From: Marc <1marc1@gmail.com>
To: linux-cifs@vger.kernel.org
Subject: Follow up on: Issue with kernel 6.8.0-40-generic?
Date: Tue, 22 Jul 2025 09:38:17 +1000 [thread overview]
Message-ID: <CAMHwNVuy2+EjMNFJAvMKACwpuSQ5kry25q5y5c1j4u2=Rc29ng@mail.gmail.com> (raw)
Dear all,
This message is a follow up on a message I initially wrote about a year ago.
I have the following setup: Windows 11 machine running in VirtualBox,
hosted on Ubuntu 22.04.
The Windows machine uses MS OneDrive to connect to our corporate
OneDrive for SharePoint. Inside the OneDrive directory structure, I
have created a Windows share. Let's call it "mydata".
Whenever the Windows 11 machine is running, on my Ubuntu host, I then
run `sudo mount.cifs //192.168.56.2/mydata /mnt/mydata -o
username=marc,uid=1000,gid=1000`. This will then mount the Windows
share and I can work with the files on Ubuntu.
The reason for my message last year was that since my Ubuntu host
machine upgraded to kernel 6.8.0-40-generic, I was no longer able to
mount the "mydata" Windows share.
Thanks to the great work of the community this was addressed and in
version 6.8.0-60-generic I was able to mount the share again.
However, I noticed that any PDF file I tried to open from this share would fail.
Evince reports "Unable to open document <path to pdf file> PDF
document is damaged".
This then caused me to again revert back to kernel 6.5.0-45-generic.
Today, I found some time for some testing with a newer kernel version
to see if the issue is still present.
I used mainline-gtk to install kernel version 6.15.7-061507-generic.
This kernel portrays the same problem when trying to open a PDF file.
Opening and editing text files, spreadsheets and images via the share
is no problem.
Hopefully someone can have a look into this situation.
Thank you.
Regards, /|/|arc.
reply other threads:[~2025-07-21 23:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMHwNVuy2+EjMNFJAvMKACwpuSQ5kry25q5y5c1j4u2=Rc29ng@mail.gmail.com' \
--to=1marc1@gmail.com \
--cc=linux-cifs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).