[Bug 1021375] Re: Nautilus says the USB stick is read only when it is not
I know I'm not running the latest LTS, but 16.04, yet I tried Etienne's advice (because it seems to make perfect sense), but fsck wasn't allowed to fix a FAT-mismatch: sudo fsck.vfat /dev/sdf1 fsck.fat 3.0.28 (2015-05-16) FATs differ but appear to be intact. Use which FAT ? 1) Use first FAT 2) Use second FAT ? 1 Perform changes ? (y/n) y /dev/sdf1: 25 files, 445911/487648 clusters Writing 1950600 bytes at 2243584 failed: Operation not permitted Seems like the readonly even applies to "sudo fsck". Permissions of the block device are: brw-rw 1 root disk 8, 81 Sep 28 23:04 /dev/sdf1 As it seems that this issue is still open, I hope that maybe someone might find this information useful for debugging. Thanks for any hints! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1021375 Title: Nautilus says the USB stick is read only when it is not To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1021375/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792167] Re: Display size detected incorrectly
Bug still present. In my multi-display setup a 40" display is reported as a 7" in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845792] Re: gnome-shell crashed with SIGSEGV in meta_get_window_actors()
*** This bug is a duplicate of bug 1845136 *** https://bugs.launchpad.net/bugs/1845136 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1845136, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1845792/+attachment/5292259/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292261/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292266/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292267/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292268/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292271/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292272/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1845136 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845792 Title: gnome-shell crashed with SIGSEGV in meta_get_window_actors() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
Why the f*** has nothing been done on this for over a year? > Could someone having the issue record a screencast showing the bug? Do you need a screencast because you are too lazy to read my description of the issue which is in my original report and perfectly describes what happens, or because you genuinely doubt that I might be making this up? Or is my english really so bad that my description of the issue isn't clear enough? I think you can literally picture it in your head by reading it, but of course I'm biased because I wrote it myself and I've seen the issue. Yet I find it really difficult to believe that anyone familiar with Nautilus, even without having ever observed the issue, would have any difficulty in understanding what I describe. By the way, now I found out that my Trash folder (in home/.local/share/Trash) was about 140 GB. There's obviously something wrong with that. I certainly haven't deleted 100 GB (nor even anywhere near one GB) in the last few months, and I assume the trash is supposed to get emptied automatically from time to time. Now I did "empty Trash" from nautilus and during the whole time it took, it kept flickering just as described in the issue report as it usually happens when deleting folders with "many" files in them. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 438494] Re: Brasero reports blank CD's free space incorrectly.
This is still happening with version 3.12.1, under Ubuntu 18.04 LTS. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/438494 Title: Brasero reports blank CD's free space incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/438494/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845198] Re: GNOME Shell seemingly locked up at login
I had this issue in VM consistently when loggin in with Xorg. No problems with Wayland. Tried the patch from above ppa and it appears to have solved problem. Will do physical install on laptop to verify -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845198 Title: GNOME Shell seemingly locked up at login To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834495] Re: Calendar name is not persistent after log out (it changes back to default name)
** Description changed: Steps to reproduce the bug: - 1. Add a Google or a Nextcloud account in gnome-calendar (or gnome-online-accounts) + 1. Add a Google or a Nextcloud account in gnome-calendar 2. Activate the calendar component in the account - 3. Open gnome-calendar and go to Calendar Settings (either from the "Manage your calendars" button in the app or from the app menu in the top bar of gnome-shell) - 4. Choose a Google or a Nextcloud calendar, which was already setup from step 1 + 3. Open gnome-calendar and go to Calendar Settings + 4. Choose a Google or a Nextcloud calendar 5. Change the calendar name 6. Go back, close the app and open it again 7. The new name is still there 8. Log out and log back in 9. Check the calendar name 10. It's back to the default name The new calendar name should always be persistent and does not change to the default name. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 27 16:45:18 2019 InstallationDate: Installed on 2018-11-29 (209 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1834495 Title: Calendar name is not persistent after log out (it changes back to default name) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1834495/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1837321] Re: Update to 2.7
** Changed in: iio-sensor-proxy (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1837321 Title: Update to 2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1837321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() when using the GPaste extension
Bug #1775971 is for updating gpaste to 3.28.3 in Bionic, which fixes two crashes, one with emptying history and one with image support. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1813173 Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() when using the GPaste extension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
