[Bug 1901582]
(In reply to PGillespie from comment #43) > Forgive my ignorance, but will this fix be backported to 5.18.x? Or will the > fix only apply to 5.20.3? > Am currently on Kubuntu 20.04 with version 5.18.5. And what systemd version does Kubuntu 20.04 have? According to my testing on the upcoming openSUSE Leap 15.3 (which has Plasma 5.18 and systemd 246), the only change needed to fix the problem there is the commit referenced in bug#42, otherwise things seem to work well. But it seems Ubuntu 20.04 has systemd 245 (can you confirm?). From what I understand that might have had a "bug" that broke the deprecated GetSessionByPID function (seems to be fixed again in 246), so probably the fix from comment#10 (https://invent.kde.org/plasma/plasma- workspace/commit/bb7b1226e65f533e21145b03047bfef604232323) would be needed as well (and https://invent.kde.org/plasma/plasma- workspace/commit/f6269cadde64ac535092a74cb4fc493cc25014fe to fix it again for older versions). Maybe you should also contact the distribution about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901582 Title: 'Switch user' not available in application launcher after upgrade to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-desktop/+bug/1901582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869280]
Well, the crash apparently only occured with Qt 5.13 or lower, as mentioned in bug#404518#c20 . But Plasma 5.19 requires Qt 5.14 as minimum anyway, so it's no wonder why it's not reproducible with that version anymore. Although I don't know about Qt 5.12.9, the last one I tried was 5.12.7 (as shipped in openSUSE Leap 15.2) where it did still crash. (until the kirigami change was reverted in the distribution package to avoid this crash) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869280 Title: Plasma system settings app crashes when selecting Virtual Desktops menu item To manage notifications about this bug go to: https://bugs.launchpad.net/kirigami2/+bug/1869280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869280]
*** Bug 421551 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to systemsettings in Ubuntu. https://bugs.launchpad.net/bugs/1869280 Title: Plasma system settings app crashes when selecting Virtual Desktops menu item To manage notifications about this bug go to: https://bugs.launchpad.net/kirigami2/+bug/1869280/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1869280]
*** Bug 423220 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869280 Title: Plasma system settings app crashes when selecting Virtual Desktops menu item To manage notifications about this bug go to: https://bugs.launchpad.net/kirigami2/+bug/1869280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982210]
*** Bug 410396 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982210 Title: Akregator shows 07.02.2106 07:28 in the date section To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/982210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
*** Bug 363876 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437260]
*** Bug 357001 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437260 Title: Plasma5 Font Preview is not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437260]
*** Bug 356444 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437260 Title: Plasma5 Font Preview is not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437260]
*** Bug 358728 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1437260 Title: Plasma5 Font Preview is not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
*** Bug 357641 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
*** Bug 343518 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
*** Bug 349432 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
*** Bug 357942 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
*** Bug 355707 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
*** Bug 354800 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422469]
(In reply to Hermann from comment #65) Yes, it's fully up to date. Ok. What I tried now is totally removed ~/.kde4/share/apps/kfileplaces/ and removed also ~/.local/share/user-places* files. BUT after logout and back in there was now functional plasma-desktop there!?! No kicker, no taskbar/systemtray icons, no plasma widgets, no desktop background picture... Also 'killall plasma-desktop plasma-desktop ' didn't bring back a working desktop in this stage :( Strange, that should have absolutely no impact on plasma-desktop. I added then a new user in a console and logged me in with this new user and voila, there I have a perfectly working kde/dolphin (incl. places entries working here). So I copied the working ~/.local/share/user-places.xbel file from this new user to my old user (chowned to old user, home folder name to old user) and logged in again with the old user. Now I had a working desktop again! The situation now is... I CAN add a new place in dolphin (this new entry still gets deleted automatically after 1 sec) BUT after this addition of a new places entry plasma-desktop crashes again :(! That it works with a new user account shows that the bug is fixed. But again, check that the file is writeable for your user. Depending on how you copied it, that might not be the case. Really strange :( Yes, and especially your Plasma crashes are totally unrelated to this fixed bug report. And I still don't see any relation to Plasma, Plasma should not care at all whether user-places.xbel exists. Probably you added some Plasmoid that makes use of it? In this case that might also be the reason why places get removed again automatically. Try to delete (or at least temporary rename) Plasma's config as well: ~/.kde4/share/config/plasma* And if Plasma crashes, you should file a bug report against Plasma. But it would be good to find out first which Plasmoid causes this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422469 Title: Dolphin won't keep the folder shortcuts on Kubuntu 15.04 with Plasma 5. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422469]
(In reply to Hermann from comment #68) Wolfgang, thank you for your patience I found it! Great! The plasma-widget Homerun-Kicker (https://blogs.kde.org/2014/01/29/homerun-120) causing this plasma-desktop crash And I suppose it also overwrote your changes to the places. From a quick look at the source code it seems that this still uses both files, and probably tries to synchronize them as well. That's what mainly caused problems in the past, and got removed in kdelibs and dolphin to fix this (and other) bugs. They only use user-places.xbel now. Maybe there would be an option to turn the places off in Homerun? This might be a workaround. (In reply to Hermann from comment #69) sumbitted also a new bug in homerun project, https://bugs.kde.org/show_bug.cgi?id=349850 Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422469 Title: Dolphin won't keep the folder shortcuts on Kubuntu 15.04 with Plasma 5. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422469]
(In reply to Hermann from comment #63) So by above mentioned solution to add the KDE:Applications repo doesn't work here. I've upgrade my kde packages to the Applications repo versions but the dolphin problem still exists. It works fine here. But adding this repo and installing dolphin from there is not necessary any more anyway. Dolphin 15.04.1 and kdelibs 4.14.9 are available as official update for openSUSE 13.2. What I'm wondering is also the fact that my ~/.kde4/share/apps/kfileplaces/bookmarks.xml file is really (!) huge and becomming bigger and bigger (3,5MB now). ~ ll ~/.kde4/share/apps/kfileplaces/bookmarks.xml -rw-r--r-- 1 heart users 3,5M 1. Jul 13:30 /home/heart/.kde4/share/apps/kfileplaces/bookmarks.xml There are ~15000 lines of code in there which looks like again and again like shown here https://paste.kde.org/pabbfnjtc Wow, a lot of garbage has accumulated in there. Just delete the whole folder /home/heart/.kde4/share/apps/kfileplaces/, the places are not stored there any more to fix this bug (and others). Strange that it is still growing though. It shouldn't be used at all any more. Is your system fully up to date? All kdelibs* and libkde* packages in particular? (.local/share/user-places.xbel file looking good with 2,9K) Looks ok, yes. But verify that the file is writable. If you still have problems with the latest versions, you might try to delete that one as well and start fresh. Maybe it's gotten corrupted somehow by the earlier problems... And I don't see how your plasma crashes would be related to this bug at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422469 Title: Dolphin won't keep the folder shortcuts on Kubuntu 15.04 with Plasma 5. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422469]
(In reply to André Verwijs from comment #59) - Linux 3.16.7-21-desktop - openSUSE 13.2 (Harlequin) (x86_64) - KDE: 4.14.6 - Dolphin 14.12.3-16.5 Same problem here, /local/share/user-places.xbel is not being updated.. (witch saves places i think) So once again: Yes, this is a problem in Dolphin 14.12.3, that's the version it has been reported against. For openSUSE an update to the fixed 15.04.1 is on the way, but it will take a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422469 Title: Dolphin won't keep the folder shortcuts on Kubuntu 15.04 with Plasma 5. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422469]
(In reply to Peter Stolz from comment #54) Same problem here, Ubuntu 15.04 with Unity Desktop and Dolphin 14.12.3. Again, this will (hopefully) be fixed in KDE Applications 15.04.1, to be released tomorrow. Bug your distribution to include the fix in their packages or to update them. There's no need for more I still see this with Dolphin 14.12.3 comments here, IMHO. This bug has originally been reported against dolphin 14.12.3 anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422469 Title: Dolphin won't keep the folder shortcuts on Kubuntu 15.04 with Plasma 5. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422469]
(In reply to Alain Laporte from comment #56) FYI : seems fixed with latest packages on ArchLinux. And it's strange, I don't use yet KDE Applications 15.04.1 : Well, that's not so strange really. Arch apparently added the fixes to their 15.04.0 packages on April 30th (i.e. kdebase-dolphin 15.04.0-3 and kdelibs 4.14.7-2): https://projects.archlinux.org/svntogit/packages.git/log/trunk?h=packages/kdebase https://projects.archlinux.org/svntogit/packages.git/log/trunk?h=packages/kdelibs So you're basically confirming that the fix works... ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422469 Title: Dolphin won't keep the folder shortcuts on Kubuntu 15.04 with Plasma 5. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313874]
(In reply to comment #27) I've got to the same commmit by using 'git bisect' independently. I haven't looked into it yet, however. I guess a bug report to util-linux might be good too. No need for any further bug reports. This has been fixed already: https://lkml.org/lkml/2014/5/28/297 It has been backported to openSUSE's 3.11.10 kernel and will be part of the next kernel update there. I tried it out, and floppy disk access now works at first attempt again, be it with mdir, blkid, or the patched udisks (with or without an fstab entry for the floppy drive). And yes, the patches still work fine and fix the issue reported here, i.e. the floppy does get correctly mounted as user, no matter whether there is an fstab entry or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313874 Title: fstab-based mounts not done as calling user To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1313874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064195]
(In reply to comment #27) I've got to the same commmit by using 'git bisect' independently. I haven't looked into it yet, however. I guess a bug report to util-linux might be good too. No need for any further bug reports. This has been fixed already: https://lkml.org/lkml/2014/5/28/297 It has been backported to openSUSE's 3.11.10 kernel and will be part of the next kernel update there. I tried it out, and floppy disk access now works at first attempt again, be it with mdir, blkid, or the patched udisks (with or without an fstab entry for the floppy drive). And yes, the patches still work fine and fix the issue reported here, i.e. the floppy does get correctly mounted as user, no matter whether there is an fstab entry or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064195 Title: No permission to access files on storage device Ubuntu 12.04 does not allow me to access Floppy Drive To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1064195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064195]
(In reply to comment #24) kernel 3.12.9.1 - works normally. (In reply to comment #25) Kernel 3.13.10 - works normally. I tried some kernels as well, here are my findings: It works fine (on first attempt) with the 3.7.10 kernels from openSUSE 12.3. It still works fine with the 3.11.6 kernel shipped with openSUSE 13.1. But it fails with the 3.11.10 kernels available in the official update repo. Anyway, I guess you/we can stop trying different kernel versions now: Possibly it is regression in a kernel 3.14 This is the commit that causes it: https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git/commit/?h=for-nextid=7b7b68bba5ef23734c35ffb0d8d82079ed604d33 I built openSUSE 13.1's 3.11.10 kernel (the latest one that has this problem) _without_ that commit (it was backported by openSUSE), and it works fine now. Here is the accompanying bug report that lead to this commit: https://bugzilla.novell.com/show_bug.cgi?id=773058 Not sure how to proceed now. I think a bug report against the kernel would be in order, as this not only affects udisks. (as mentioned, mdir and blkid show the same behavior) I guess I'll start with reporting it to openSUSE, as they are responsible for that change. But this will have to wait until after the weekend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064195 Title: No permission to access files on storage device Ubuntu 12.04 does not allow me to access Floppy Drive To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1064195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064195]
(In reply to comment #21) BTW, what kind of distribution and destop environment are you two using? openSUSE 13.1 with kernel 3.11.10 and KDE 4.13.1 here. I couldn't reproduce the problem here, but I'll try with a newer kernel next week. Unfortunately I only have access to an actual floppy drive about once a week. I can reproduce the issue (both) in VirtualBox with openSUSE Factory (kernel 3.14), so a physical floppy drive is not really necessary. I will test with other kernel versions as well in the next days... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064195 Title: No permission to access files on storage device Ubuntu 12.04 does not allow me to access Floppy Drive To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1064195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313874]
(In reply to comment #24) kernel 3.12.9.1 - works normally. (In reply to comment #25) Kernel 3.13.10 - works normally. I tried some kernels as well, here are my findings: It works fine (on first attempt) with the 3.7.10 kernels from openSUSE 12.3. It still works fine with the 3.11.6 kernel shipped with openSUSE 13.1. But it fails with the 3.11.10 kernels available in the official update repo. Anyway, I guess you/we can stop trying different kernel versions now: Possibly it is regression in a kernel 3.14 This is the commit that causes it: https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git/commit/?h=for-nextid=7b7b68bba5ef23734c35ffb0d8d82079ed604d33 I built openSUSE 13.1's 3.11.10 kernel (the latest one that has this problem) _without_ that commit (it was backported by openSUSE), and it works fine now. Here is the accompanying bug report that lead to this commit: https://bugzilla.novell.com/show_bug.cgi?id=773058 Not sure how to proceed now. I think a bug report against the kernel would be in order, as this not only affects udisks. (as mentioned, mdir and blkid show the same behavior) I guess I'll start with reporting it to openSUSE, as they are responsible for that change. But this will have to wait until after the weekend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313874 Title: fstab-based mounts not done as calling user To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1313874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064195]
(In reply to comment #18) OK, with updated patch it works. But there is a problem: $ udisksctl mount -b /dev/fd0 Error mounting /dev/fd0: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Failed to open device /dev/fd0 for filesystem probing. $ udisksctl mount -b /dev/fd0 Mounted /dev/fd0 at /media/nikts/disk. The diskette is always mounted only with the second attempt. I can confirm this here: It works now, but only on second attempt when there's no fstab entry (with an entry it works immediately). But I don't think this is related to the patch or udisks2. I see the same behavior with mdir. After inserting a new disk, mdir fails with: Can't open /dev/fd0: No such device or address Cannot initialize 'A:' Running it a second time works. Also after running mdir once, udisksctl mount works and vice versa. So this rather seems to be a kernel issue I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064195 Title: No permission to access files on storage device Ubuntu 12.04 does not allow me to access Floppy Drive To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1064195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313874]
(In reply to comment #18) OK, with updated patch it works. But there is a problem: $ udisksctl mount -b /dev/fd0 Error mounting /dev/fd0: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Failed to open device /dev/fd0 for filesystem probing. $ udisksctl mount -b /dev/fd0 Mounted /dev/fd0 at /media/nikts/disk. The diskette is always mounted only with the second attempt. I can confirm this here: It works now, but only on second attempt when there's no fstab entry (with an entry it works immediately). But I don't think this is related to the patch or udisks2. I see the same behavior with mdir. After inserting a new disk, mdir fails with: Can't open /dev/fd0: No such device or address Cannot initialize 'A:' Running it a second time works. Also after running mdir once, udisksctl mount works and vice versa. So this rather seems to be a kernel issue I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313874 Title: fstab-based mounts not done as calling user To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1313874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313874]
(In reply to comment #21) BTW, what kind of distribution and destop environment are you two using? openSUSE 13.1 with kernel 3.11.10 and KDE 4.13.1 here. I couldn't reproduce the problem here, but I'll try with a newer kernel next week. Unfortunately I only have access to an actual floppy drive about once a week. I can reproduce the issue (both) in VirtualBox with openSUSE Factory (kernel 3.14), so a physical floppy drive is not really necessary. I will test with other kernel versions as well in the next days... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313874 Title: fstab-based mounts not done as calling user To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1313874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313874]
(In reply to comment #14) I applied these three patches. Without entry in fstab: When I try to get into a floppy through Thunar it says: Message did not receive a reply (timeout by message bus). And service udisksd ends. I can confirm this problem here after applying the 3 patches to the current version 2.1.3. Running udisksctl mount -b /dev/fd0 with the removed fstab entry just gives: Error mounting /dev/fd0: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) udisksd apparently crashes, it disappears from the process list temporarily, and is restarted again immediately. With the following fstab entry in place it works and indeed mounts the disk as user, not root as before: /dev/fd0 /media/floppyauto noauto,user,sync 0 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313874 Title: fstab-based mounts not done as calling user To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1313874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313874]
I installed debuginfo packages now and attached gdb to udisksd, I get the following backtrace: Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fa21700 (LWP 2865)] 0x7fa230cae849 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x7fa230cae849 in raise () from /lib64/libc.so.6 #1 0x7fa230cafcd8 in abort () from /lib64/libc.so.6 #2 0x7fa231297f0d in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa2312b52f7 in g_assertion_message () from /usr/lib64/libglib-2.0.so.0 #4 0x7fa2312b535a in g_assertion_message_expr () from /usr/lib64/libglib-2.0.so.0 #5 0x0041fc05 in probe_fs_type_prior_to_mount (error=0x7fa21fffe778, block=0x2510220) at udiskslinuxfilesystem.c:623 #6 calculate_fs_type (error=0x7fa21fffe778, given_options=0x25bb4d0, block=optimized out) at udiskslinuxfilesystem.c:746 #7 handle_mount (filesystem=0x25102b0, invocation=0x7fa2240031c0, options=0x25bb4d0) at udiskslinuxfilesystem.c:1448 ... So it seems to assert in udiskslinuxfilesystem.c:623, which is: gassert (block == NULL); -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313874 Title: fstab-based mounts not done as calling user To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1313874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064195]
I installed debuginfo packages now and attached gdb to udisksd, I get the following backtrace: Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fa21700 (LWP 2865)] 0x7fa230cae849 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x7fa230cae849 in raise () from /lib64/libc.so.6 #1 0x7fa230cafcd8 in abort () from /lib64/libc.so.6 #2 0x7fa231297f0d in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa2312b52f7 in g_assertion_message () from /usr/lib64/libglib-2.0.so.0 #4 0x7fa2312b535a in g_assertion_message_expr () from /usr/lib64/libglib-2.0.so.0 #5 0x0041fc05 in probe_fs_type_prior_to_mount (error=0x7fa21fffe778, block=0x2510220) at udiskslinuxfilesystem.c:623 #6 calculate_fs_type (error=0x7fa21fffe778, given_options=0x25bb4d0, block=optimized out) at udiskslinuxfilesystem.c:746 #7 handle_mount (filesystem=0x25102b0, invocation=0x7fa2240031c0, options=0x25bb4d0) at udiskslinuxfilesystem.c:1448 ... So it seems to assert in udiskslinuxfilesystem.c:623, which is: gassert (block == NULL); -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064195 Title: No permission to access files on storage device Ubuntu 12.04 does not allow me to access Floppy Drive To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1064195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064195]
(In reply to comment #14) I applied these three patches. Without entry in fstab: When I try to get into a floppy through Thunar it says: Message did not receive a reply (timeout by message bus). And service udisksd ends. I can confirm this problem here after applying the 3 patches to the current version 2.1.3. Running udisksctl mount -b /dev/fd0 with the removed fstab entry just gives: Error mounting /dev/fd0: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) udisksd apparently crashes, it disappears from the process list temporarily, and is restarted again immediately. With the following fstab entry in place it works and indeed mounts the disk as user, not root as before: /dev/fd0 /media/floppyauto noauto,user,sync 0 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064195 Title: No permission to access files on storage device Ubuntu 12.04 does not allow me to access Floppy Drive To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1064195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
