[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Tested again from focal-proposed (mutter 3.36.6-1ubuntu0.20.04.2). Can confirm it still fixes the problem! (Intel HD Graphics). -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1893719] Re: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF
** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1893719 Title: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893719/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896861] [NEW] Update to 1.90.3
Public bug reported: Fixes various bugs in AuthenTec chip, synapitcs and add goodix reader support ** Affects: libfprint (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1896861 Title: Update to 1.90.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1896861/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
As per comment https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/comments/27 We can mark this as verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from c
As per comment https://bugs.launchpad.net/mutter/+bug/1857947/comments/11 We can mark this as verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1857947 Title: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from call_later_func() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1857947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1887998] Re: Update to 3.36.4 and SRU it
As per comment https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/comments/13 We can mark this as verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1887998 Title: Update to 3.36.4 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879968] Re: Copy/paste still sometimes fails in LibreOffice and Wine apps
I forgot to mention this i changelogs, so this will be closed once bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332 will be ** Changed in: mutter (Ubuntu Focal) Status: Triaged => Fix Committed -- 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/1879968 Title: Copy/paste still sometimes fails in LibreOffice and Wine apps To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896332] Re: SRU 3.36.6
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1896332 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896416] Re: screen locking no longer works
yep, there we go, works fine now. I wonder what component malfunctioned when setting that, could have been wine or vlc or any number of things that prevent sleep while playing media, I suppose. It's too bad that there's no indicator or overrider to let a user know what's going on in this scenario. -- 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/1896416 Title: screen locking no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896332] Re: SRU 3.36.6
No issues here either on AMD and Intel. Thankfully this also finally fixes https://bugs.launchpad.net/bugs/1879968 -- 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/1896332 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896332] Re: SRU 3.36.6
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1896332 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750146]
Dear sender! Thank you for your message! Unfortunately, I am out of office until 27.9.2020 and hence will not be able to reply immediately. Your email will not be forwarded, but I will answer your email as soon as possible on my return. In very urgent cases, however, please contact our service center via email mailto:serv...@escrypt.com>> or phone +49 234 43870-200. Yours sincerely, Matthias Pritschet Sehr geehrte Damen und Herren, Vielen Dank für Ihre E-Mail! Ich bin leider bis zum 27.9.2020 nicht erreichbar und kann daher nicht unmittelbar antworten. Ihre Nachricht wird nicht weitergeleitet. In dringenden Fällen können Sie sich jedoch gern an unser Service-Center (mailto:serv...@escrypt.com>> oder +49 234 43870-200) wenden. Mit freundlichen Grüßen Matthias Pritschet -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1750146 Title: Xbox (One) Wireless Controller won't connect To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750146]
Yeah, it seems to get worse with every 5.4 LTS update. Worked almost flawless about some months ago (despite taking something from 30-60s to successfully connect). But I don't see a correlation to any commits. But now, it's almost impossible to connect successfully, it usually disconnects after a 1-2 minutes (coincidentally just when entering a game). I usually also see messages like this: During use of the controller (probably around disconnect time): [ 5304.480502] Bluetooth: Unexpected continuation frame (len 52) When plugging the BT dongle: [ 5241.926752] Bluetooth: hci0: unexpected event for opcode 0x While it's in a loop of constantly connecting and disconnecting: [ 1120.736530] Bluetooth: hci0: hardware error 0x58 [ 1120.923550] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 1120.923555] debugfs: File 'le_max_key_size' in directory 'hci0' already present! [ 1120.923557] debugfs: File 'force_bredr_smp' in directory 'hci0' already present! Other BT devices seem to just work fine tho I don't use a lot of them and only occasionally. It seems that the Xbox One S firmware does something strange in the BT protocol. It also needs either ERTM disabled to connect. Alternatively, one can apply this patch to be able to use ERTM: https://github.com/kakra/linux/commit/c8b24d83f227a7fecfa9420d6756074e8f9b542c I'm also feeling there's some internal state getting messed up within the controller on each BT pairing: Results are not really reproducible. I managed to get it to work flawlessly one time (stable connection despite 20-30s connect handshake time), then purged my Bluetooth config from /var/lib, re-paired the controller and now it's a mess - still with the same kernel version. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1750146 Title: Xbox (One) Wireless Controller won't connect To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896847] [NEW] Most executables crash when running in GUI but not in terminal
Public bug reported: Most of the executable ELF files in /usr/bin/ will not run from any GUI interface and most do not show up anywhere including in the files list. When I try to execute one from GUI I get the popup box that I have attached to this report. However, when I run the same file from a terminal it will open and run as it should. It would seem the error is either in the GUI or every single ELF file is missing a : in the uri. Many of those are supposed to run in the background. They don't. I will be very happy to see this fixed and everything running as it is supposed to run. Just in case my attachment has something wrong with it too, I will type out what is in the popup box: Invalid url:'/usr/bin/gnome-system-monitor' given, exiting No ':' in the uri ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 17:33:43 2020 InstallationDate: Installed on 2020-09-08 (15 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Popup error code" https://bugs.launchpad.net/bugs/1896847/+attachment/5413649/+files/system-monitor-terminal.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1896847 Title: Most executables crash when running in GUI but not in terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1896847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1896416] Re: screen locking no longer works
On Wed, Sep 23, 2020 at 10:14:57PM -, Tessa wrote: > Sep 23 15:07:58 boxxy gnome-shell[209336]: Screen lock is locked down, > not locking > > so it appears as if it thinks the screen is already locked, even though > I'm interacting with my session. and the dbus call doesn't have any way This message indicates that the screen lock has been disabled: https://sources.debian.org/src/gnome- shell/3.36.6-1/js/ui/screenShield.js/?hl=595#L595 I'm guessing that the setting may be named 'disable-lock-screen' in the 'org.gnome.desktop.lockdown' schema: https://sources.debian.org/src/gnome- shell/3.36.6-1/js/ui/screenShield.js/?hl=24#L24 try this to see the current value of the setting: gsettings get org.gnome.desktop.lockdown disable-lock-screen try this to change it: gsettings set org.gnome.desktop.lockdown disable-lock-screen false # or true, as needed I hope this helps. Thanks -- 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/1896416 Title: screen locking no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1558886] Please test proposed package
Hello Anthony, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1887998] Re: Update to 3.36.4 and SRU it
Hello Marco, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1887998 Title: Update to 3.36.4 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896416] Re: screen locking no longer works
why am I not surprised that sending a cryptic dbus command is the "correct" way to lock the screen from the cli these days. in any case, I can run that command as often as you like, and it always returns success to the shell, but it never locks the screen: tessa@boxxy:~/Downloads$ dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock tessa@boxxy:~/Downloads$ echo $? 0 tessa@boxxy:~/Downloads$ dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock tessa@boxxy:~/Downloads$ echo $? 0 looking at the journalctl output right after running, I see the following, which is clearly incorrect: Sep 23 15:07:58 boxxy gnome-shell[209336]: Screen lock is locked down, not locking so it appears as if it thinks the screen is already locked, even though I'm interacting with my session. and the dbus call doesn't have any way of returning an error state to the cli if the operation fails, which is honestly such a bad design, as it leaves things that rely on it silently failing all over the interface but claiming they're working correctly. -- 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/1896416 Title: screen locking no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Hello Cristiano, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896332] Please test proposed package
Hello Marco, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1896332 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
Hello Ivan, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from c
Hello errors.ubuntu.com, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1857947 Title: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from call_later_func() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1857947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Hello Cristiano, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
For ABNT2 keyboards, I've removed the "Scroll Lock" key, see: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard- config/-/merge_requests/112 It is not the right solution (I even regretted it), but it works... -- 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/1895486 Title: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1895486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
I've tested the mutter 3.36.6-1ubuntu0.20.04.2~wip1 (in the PPA). Now, all works fine! Thanks for your attention and work. -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Thanks, Trevinho! ;) -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Thanks for making the bug SRU compliant, I've uploaded a new version. In the mean time you can probably test it using the ppa at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4267 ** Description changed: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] - This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. + This very fix was already handled as part of bug #1889090 and we had no regression report,. + + However, one possible is that the screen size is not set properly for + the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) - InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) - SourcePackage: mutter + InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released ** Changed in: mutter (Ubuntu Focal) Importance: Undecided => High ** Changed in: mutter (Ubuntu Focal) Status: New => In Progress ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
I mean, this looks like bug #1889090 is back.. -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Oh, crazy... This was supposed to be fixed already, looks like something broke when adapting the patch?! -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
And a new upload now in the queue: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1838152/comments/11 -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
I've tested in a fresh install also. -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413602/+files/dmesg.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
See also: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440 ** Description changed: + In Ubuntu 20.04.1 (focal): + [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: - # set this to 0 to disable apport, or to 1 to enable it - # you can temporarily override this with - # sudo service apport start force_start=1 - enabled=0 + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413601/+files/lspci-vnvn.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413600/+files/uname-a.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "lsusb-v.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413598/+files/lsusb-v.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413599/+files/version.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413597/+files/syslog -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
In my syslog: gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor- manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) gnome-shell[3407]: Bail out! mutter:ERROR:../src/backends/x11/meta- monitor-manager- xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) ** Description changed: In Ubuntu 20.04.1 (focal): [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] - This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. + This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Description changed: - In Ubuntu 20.04.1 (focal): + In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Summary changed: - Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia) + Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) ** Description changed: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] - This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. + This bug was introduced by Marco Trevisan (Treviño) in the LP 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago)
[Bug 1896825] [NEW] Mutter 3.28 doesn't compile with mesa 20
Public bug reported: [ Impact ] Mesa 20 update broke mutter builds, as visible in https://launchpad.net/ubuntu/+source/mutter/3.28.4+git20200505-0ubuntu18.04.1 [ Test case ] Mutter should build cleanly in a bionic chroot [ Regression potential ] Wayland components aren't included in the final mutter build ** Affects: mutter (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: mutter (Ubuntu Bionic) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Bionic) Importance: Undecided => High ** Changed in: mutter (Ubuntu Bionic) Status: New => In Progress ** Changed in: mutter (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1896825 Title: Mutter 3.28 doesn't compile with mesa 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896332] Re: SRU 3.36.6
There is a problem: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818 -- 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/1896332 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I've fill another bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818 -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892747] Re: [Dell Vostro 3446] Ubuntu hangs while changing display brightness from keyboard shortcut
Daniel, I'm not sure if this bug is related but, the system also hangs for a few seconds whenever the Wi-Fi gets disconnected. -- 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/1892747 Title: [Dell Vostro 3446] Ubuntu hangs while changing display brightness from keyboard shortcut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896818] [NEW] Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
Public bug reported: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896756] Re: tracker* startup is defined multiple times
** Package changed: systemd (Ubuntu) => tracker (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896756 Title: tracker* startup is defined multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896756] [NEW] tracker* startup is defined multiple times
You have been subscribed to a public bug:
This is about
- tracker-miner-fs
- tracker-extract
- tracker-store
Actual Behavior
=
Their startup is defined in
- ${XDG_CONFIG_HOME}/autostart ( more info:
https://wiki.archlinux.org/index.php/XDG_Autostart )
- /usr/lib/systemd/user/tracker*.service
Expected Behavior
===
Startup is only defined in one place.
Reason:
- Managing the software does not get confusing
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Sep 23 20:39:33 2020
MachineType: FUJITSU FMVWB3U27
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows
2015" pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service →
/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: Upgraded to focal on 2020-07-24 (61 days ago)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB2BB
dmi.board.vendor: FUJITSU
dmi.board.version: A2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:
dmi.product.family: LIFEBOOK-JR
dmi.product.name: FMVWB3U27
dmi.sys.vendor: FUJITSU
** Affects: tracker (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
tracker* startup is defined multiple times
https://bugs.launchpad.net/bugs/1896756
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is subscribed to tracker in Ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896654] Re: Windows flicker when resizing with mouse
Should note - testing mutter package 3.38.0-1ubuntu1 ** Summary changed: - Windows flicker when resizing with mouse + Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie ** Summary changed: - Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie + Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) -- 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/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896654] Re: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)
I do not see any window flickering with QEMU hosting 20.10 guest. So specific to intel i915? Sorry - I cannot test radeon or Nvidia. -- 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/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@ Marco Trevisan, After I power down my display and power up again (in the lock screen), the problem is: gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor- manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) gnome-shell[3407]: Bail out! mutter:ERROR:../src/backends/x11/meta- monitor-manager- xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+attachment/5413576/+files/syslog -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896654] Re: Windows flicker when resizing with mouse
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896654] Re: Windows flicker when resizing with mouse
Note - this affects GNOME-Shell on Xorg as well. Confirmed with intel i915 driver. GNOME-Shell on Wayland there are no window flicker So most probably a regression in mutter (since budgie and GNOME-Shell share the same window manager) in the X11 handling. -- 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/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
I've prepared a new package with the whole set of fixes: https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text =gnome-shell -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896812] [NEW] Failed to start GNOME Shell on X11
Public bug reported: Ubuntu 20.04.1 Package mutter-3.36.6-1ubuntu0.20.04.1 Sep 23 12:30:03 razorback systemd[2389]: Starting GNOME Shell on X11... Sep 23 12:30:03 razorback gnome-shell[26684]: ** Sep 23 12:30:03 razorback gnome-shell[26684]: mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Sep 23 12:30:03 razorback gnome-shell[26684]: Bail out! mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Sep 23 12:30:03 razorback systemd[2389]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT Sep 23 12:30:03 razorback systemd[2389]: gnome-shell-x11.service: Failed with result 'core-dump'. Sep 23 12:30:03 razorback systemd[2389]: Failed to start GNOME Shell on X11. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1896812 Title: Failed to start GNOME Shell on X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@ Marco Trevisan, I'll do that. Anyway, thanks for the fix. ;) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@ Cristiano, please fill another bug for that :) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
The bug is fixed when I updated mutter to 3.36.1-1ubuntu0.20.04.1. BUT After an "Automatic Screen Lock", the display turned off, the Gnome Shell crash and show us a blank screen with the message "Oh no! Something has gone wrong." This bug did not appears before the update. I have a NVIDIA card. I think that this problem occurs only with NVIDIA users. I have other PC (without a NVIDIA card) and the problem not occurs. -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896804] [NEW] CD/DVD drive detected as read only, command line and GUI programs
Public bug reported: Disks utility program and command line only seeing the drive as read only. unable to write data to the disk. all works OK in Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: brasero 3.12.2-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_31_35_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 17:47:26 2020 InstallationDate: Installed on 2020-02-04 (232 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: Upgraded to focal on 2020-05-07 (138 days ago) ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1896804 Title: CD/DVD drive detected as read only, command line and GUI programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1896804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1891338] Re: apparmor misconfigured for evince
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6 --- apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium * Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not 3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the wrong directory in is_container_with_internal_policy(), which causes policy to always fail to load in containers. Thanks to Christian Ehrhardt for the analysis. (LP: #1895967) apparmor (3.0.0~beta1-0ubuntu5) groovy; urgency=medium [ John Johansen ] * d/p/fix-parser-to-emit-proc-attr-access-for-all-situations.patch: fix-automatic-adding-of-rule-for-change-hat-iface.patch fixed the parser to emit rules needed for change_hat in the hat profiles but broke the rule being emitted for the parent profile, this fixes it for both so that it is emitted for any profile that is a hat or that contains a hat. * d/p/fix-change-profile-stack-abstraction.patch: fix the change_profile abstraction so that it allows access to the apparmor attribute paths under LSM stacking. apparmor (3.0.0~beta1-0ubuntu2) groovy; urgency=medium [ John Johansen ] * d/p/fix-automatic-adding-of-rule-for-change-hat-iface.patch: fix parser not adding a rule to profiles if they are a hat or contain hats granting write access to the kernel interfaces. apparmor (3.0.0~beta1-0ubuntu1) groovy; urgency=medium [ John Johansen ] * New upstream release (LP: #1895060, LP: #1887577, LP: #1880841) * Drop all patches backported from upstream: applied in 3.0 * d/p/policy-provide-example-and-base-abi-to-pin-pre-3.0-p.patch: provide example and base abi to pin pre 3.0 policy * d/p/ubuntu/enable-pinning-of-pre-AppArmor-3.x-poli.patch: enable pinning of pre AppArmor 3.x policy * drop d/p/debian/dont-include-site-local-with-dovecot.patch: no longer needed with upstream 'include if exists' [ Steve Beattie ] * d/p/parser-fix_cap_match.patch: fix cap match to work correctly, important now that groovy has a 5.8 kernel. * d/apparmor-profiles.install: + adjust for renamed postfix profiles + add usr.bin.dumpcap and usr.bin.mlmmj-receive to extra-profiles + remove usr.sbin.nmbd and usr.sbin.smbd from extra-profiles (already in apparmor-profiles) * d/apparmor.install: include abi/ directory and tunables/etc. * d/apparmor.manpages: add apparmor_xattrs.7 manpage * d/control: + apparmor-utils: no more shipped perl tools, drop perl dependency + apparmor-notify: aa-notify was converted to python3 from perl; adjust -notify dependencies to compensate * d/p/fix-tests-regression-apparmor-prologue-inc-settest.patch: fix sed expression in settest() [ Emilia Torino ] * Removing Ubuntu specific chromium-browser profile. This is safe to do since groovy's chromium-browser deb installs the snap. If apparmor3 is backported to 18.04 or earlier, the profile will need to be taken into consideration - d/profiles/chromium-browser: remove chromium-browser profile - d/apparmor-profiles.postinst: remove postinst script as it only contains chromium-browser related functionallity. - d/apparmor-profiles.postrm: remove postrm script as it only contains chromium-browser related functionallity. - d/apparmor-profiles.install: remove ubuntu-specific chromium-browser abstraction and profile - d/apparmor-profiles.lintian-overrides: remove chromium-browser profile lintian overrides - d/p/ubuntu/add-chromium-browser.patch: remove patch which added chrome-browser [ Alex Murray ] * d/p/policy-provide-example-and-base-abi-to-pin-pre-3.0-p.patch: refresh this patch with the official upstream version * d/p/ubuntu/enable-pinning-of-pre-AppArmor-3.x-poli.patch: refresh this patch to match the above * d/p/parser-add-abi-warning-flags.patch: enable parser warnings to be silenced or to be treated as errors [ Jamie Strandboge ] * d/p/adjust-for-ibus-1.5.22.patch: update ibus abstract path for ibus 1.5.22. This can be dropped with AppArmor 3.0 final. * d/p/parser-add-abi-warning-flags.patch: refresh to avoid lintian warnings * d/p/ubuntu/lp1891338.patch: adjust ubuntu-integration to use abstractions/exo-open (LP: #1891338) * d/p/ubuntu/lp1889699.patch: adjust to support brave in ubuntu abstractions. Patch thanks to François Marier (LP: #1889699) * d/p/ubuntu/lp1881357.patch: adjust for new ICEauthority path in /run (LP: #1881357) -- Jamie Strandboge Tue, 22 Sep 2020 15:10:33 + ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1891338 Title: apparmor misconfigured for evince To manage notifications about this bug go to:
[Bug 1896334] Re: SRU 3.36.6
Ah about this: > If this isn't used for generating the final packages at all, why do you propose to make users download an update? Those files aren't included at all into the package, the README.sources there was included to explain why we have such files, even though they are not built. It's just inside an orig file for diff purposes, nothing more. -- 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/1896334 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1896334] Re: SRU 3.36.6
> I don't understand why yaru-theme needs to be updated, either. I see > that this has been done for yaru-theme once before, but I've found no > explanation as to why. I will make it clearer in the top post, but it should be quite easy to spot looking at the shell's (data subdir) and yaru diffs: - Ubuntu's GNOME shell uses a Yaru theme based on upstream gnome-shell This theme basically takes the shell's data/ directory, applies some diffs and generates a gresource file out of it, that it's then loaded on startup (in place of the upstream one). - GNOME Shell applied some fixes to the theme (se its data/ directory diffs) - In order to get those fixes in Ubuntu main session we have to sync the upstream changes applied to such dir to yaru's src/gnome-shell path - You can easily compare the diffs applied there to match the ones happening in its upstream counterpart. ** Description changed: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6 Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU. - The changes involving yaru here are ONLY gnome-shell upstream changes - applied to the Yaru sources, as per this we can consider them also part - of the GNOME release. + The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release. + In fact: + - Ubuntu's GNOME shell uses a Yaru theme based on upstream + gnome-shell This theme basically takes the shell's data/ directory, + applies some diffs and generates a gresource file out of it, that it's + then loaded on startup (in place of the upstream one). + - GNOME Shell applied some fixes to the theme (se its data/ + directory diffs) + - In order to get those fixes in Ubuntu main session we have to sync + the upstream changes applied to such dir to yaru's src/gnome-shell + path + - You can easily compare the diffs applied there to match the ones + happening in its upstream counterpart. The yaru-theme's `gnome-shell/upstream` directory is just for documentation and to allow three way merges when updating to new versions of gnome-shell, and it is not used for generating the final packages at all [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates -- 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/1896334 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
@ David I think pop-os disabled fractional scaling patch, so get in contact with them please: https://github.com/pop-os/mutter/commit/bc7c2658e4c873a28afeaf621fb24a1341c6d74c -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838152] Proposed package upload rejected
An upload of gnome-shell to bionic-proposed has been rejected from the upload queue for the following reason: "Fix appears incomplete, and no progress in a month. Please see https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1838152/comments/5 and subsequent discussion.". -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890875] Proposed package upload rejected
An upload of gnome-shell to bionic-proposed has been rejected from the upload queue for the following reason: "Fix appears incomplete, and no progress in a month. Please see https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1838152/comments/5 and subsequent discussion.". -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided => High ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: + [ Impact ] + + Using discord application, causes the shell to slowdown and trigger lots + of "unable to lookup icon ..." errors + + [ Test case ] + + Install discord app: + - snap install discord + + Run it, starting a call seems to trigger it more + + [ Regression potential ] + + Icons may not be loaded properly, there may be delays between a good + icon and an invalid one (and vice-versa). + + --- + Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884396] Re: Ubuntu freezing intermittently when the mega.nz appindicator is loaded
** Description changed: [ Impact ] Indicators using (big) pixmap icons cause the shell to use a lot of CPU computation, which interfere with user experience - [ Test case ] - Install mega client from https://mega.nz/sync - Run it in ubuntu and ensure it doesn't block the UI while syncing - (but even opening/closing the app should be enough to trigger + (but even opening/closing the app should be enough to trigger Alternatively use this test tool: - https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js + https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js Launch it with `gjs` and select the 'Crazy icons updates' menu item: - - The shell should not hang + - The shell should not hang [ Regression potential ] Icon updates may be late or not apply immediately (or at all). + In general there has been a refactor of the iconCache, so internally it + may happen that we load an icon more times, or that there could be an + increase in RAM usage as per missing garbage collecting of it. + - - I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. + I had similar issues when 20.04 was released, then it disappeared with + an upgrade - but sadly it's back. I have short intermittent freezings of + the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg + when writing this description, the OS freezes every second word. When + the freeze goes away the OS is snappy. I have tried switching between + Wayland and Xorg - but the problem persists. If I write something when + it freezes up the last character will be + replicated many times - like what happened + jut now. This problem did not show up in + ubuntu 18.04 through 19.10. Hope U can + fix this soon - using my laptop in unbearable. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] InstallationDate: Installed on 2020-05-12 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M13 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M13 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M13 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
Could you please stop that reassigning game? You are right, it's either on shared-mime-info or the qt integration, now the result of the testcase provided is correct on GNOME (see comment 5), it's also correct on a cloud instance (e.g no desktop integration) so it's only buggy on KDE, you should rather reassign to the Qt integration, unsure what the right component for that is though ** Package changed: shared-mime-info (Ubuntu) => kde-cli-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1857824 Title: kmimetypefinder5 misidentifies mimetype of python files containing certain strings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
testing with xdgmime [1] (reference implementation of the spec [2] and also used tests on shared-mine-type): > ../xdgmime/src/print-mime-data . test.py: name: text/x-python data: application/xhtml+xml file: application/xhtml+xml > ../xdgmime/src/test-mime test.py File "test.py" has a mime-type of application/xhtml+xml [1] https://gitlab.freedesktop.org/xdg/xdgmime [2] https://freedesktop.org/wiki/Specifications/shared-mime-info-spec/ -- kmimetypefinder5 is just a tiny wrapper over QMimeDatabase [3][4]. So bug is likely on shared-mime-info or Qt implementation. [3] https://github.com/KDE/kde-cli-tools/blob/master/kmimetypefinder/kmimetypefinder.cpp [4] https://bugs.freedesktop.org/show_bug.cgi?id=99672 ** Bug watch added: freedesktop.org Bugzilla #99672 https://bugs.freedesktop.org/show_bug.cgi?id=99672 ** Package changed: kde-cli-tools (Ubuntu) => shared-mime-info (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1857824 Title: kmimetypefinder5 misidentifies mimetype of python files containing certain strings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857824] [NEW] kmimetypefinder5 misidentifies mimetype of python files containing certain strings
You have been subscribed to a public bug:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: shared-mime-info (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
kmimetypefinder5 misidentifies mimetype of python files containing certain
strings
https://bugs.launchpad.net/bugs/1857824
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is subscribed to shared-mime-info in Ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
> > dpkg -S /usr/bin/mimetype > libfile-mimeinfo-perl: /usr/bin/mimetype how is that supposed to prove it's a shared-mime-info bug? ** Changed in: shared-mime-info (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884396] Re: Ubuntu freezing intermittently when the mega.nz appindicator is loaded
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: - I had similar issues when 20.04 was released, then it disappeared with - an upgrade - but sadly it's back. I have short intermittent freezings of - the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg - when writing this description, the OS freezes every second word. When - the freeze goes away the OS is snappy. I have tried switching between - Wayland and Xorg - but the problem persists. If I write something when - it freezes up the last character will be - replicated many times - like what happened - jut now. This problem did not show up in - ubuntu 18.04 through 19.10. Hope U can - fix this soon - using my laptop in unbearable. + [ Impact ] - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + Indicators using (big) pixmap icons cause the shell to use a lot of CPU + computation, which interfere with user experience + + + [ Test case ] + + - Install mega client from https://mega.nz/sync + - Run it in ubuntu and ensure it doesn't block the UI while syncing + (but even opening/closing the app should be enough to trigger + + Alternatively use this test tool: + https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js + + Launch it with `gjs` and select the 'Crazy icons updates' menu item: + - The shell should not hang + + [ Regression potential ] + + Icon updates may be late or not apply immediately (or at all). + + + + + I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. + + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] InstallationDate: Installed on 2020-05-12 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera - Bus 001 Device 002: ID 8087:0a2b Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=sv_SE.UTF-8 - SHELL=/bin/bash - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7 - SourcePackage: xorg + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=sv_SE.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019
[Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
@Kai, so you use a 'command is provided by a perl utility' as a reason to reasing to shared-mime-info, what's the logic? also xdg-mime works fine under GNOME or when using gio that uses shared-mime-info... ** Package changed: shared-mime-info (Ubuntu) => kde-cli-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1857824 Title: kmimetypefinder5 misidentifies mimetype of python files containing certain strings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896785] Re: Exported DBus interface is missing info or using wrong names
** Description changed:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods and
properties are missing or invalid
-
[ Test case ]
-
Run:
- gdbus call --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher \
- --method org.freedesktop.DBus.Properties.Get "org.kde.StatusNotifierWatcher"
ProtocolVersion
+ gdbus call --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher \
+ --method org.freedesktop.DBus.Properties.Get "org.kde.StatusNotifierWatcher"
ProtocolVersion
-> Should return (<0>,)
In particular, the API should contain
- gdbus introspect --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher
+ gdbus introspect --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher
node /StatusNotifierWatcher {
-
- Default fdo properties stuff
- interface org.kde.StatusNotifierWatcher {
- interface org.kde.StatusNotifierWatcher {
- methods:
- RegisterStatusNotifierItem(in s service);
- RegisterStatusNotifierHost(in s service);
- signals:
- StatusNotifierItemRegistered(s arg_0);
- StatusNotifierItemUnregistered(s arg_0);
- StatusNotifierHostRegistered();
- StatusNotifierHostUnregistered();
- properties:
- @org.qtproject.QtDBus.QtTypeName.Out0("QStringList")
- readonly as RegisteredStatusNotifierItems = [ ... list of indicators
path/obj-names ... ];
- readonly b IsStatusNotifierHostRegistered = true;
- readonly i ProtocolVersion = 0;
- };
+ Default fdo properties stuff
+
+ interface org.kde.StatusNotifierWatcher {
+ interface org.kde.StatusNotifierWatcher {
+ methods:
+ RegisterStatusNotifierItem(in s service);
+ RegisterStatusNotifierHost(in s service);
+ signals:
+ StatusNotifierItemRegistered(s arg_0);
+ StatusNotifierItemUnregistered(s arg_0);
+ StatusNotifierHostRegistered();
+ StatusNotifierHostUnregistered();
+ properties:
+ @org.qtproject.QtDBus.QtTypeName.Out0("QStringList")
+ readonly as RegisteredStatusNotifierItems = [ ... list of indicators
path/obj-names ... ];
+ readonly b IsStatusNotifierHostRegistered = true;
+ readonly i ProtocolVersion = 0;
+ };
};
-
In the old version we had an invalid "RegisterNotificationHost" method (not
specified by specs nor used)
We didn't expose the ProtocolVersion
+
+ ---
+
+ [ Regression potential ]
+
+ We won't expose anymore some NON-STANDARD and NEVER USED dbus methods such as:
+ - RegisterNotificationHost (was un-implemlented anyways)
+ - ProtocolVersion (this was supposed to be a property, not a method)
+
+ There are some changes to the interfaces xml files to follow the
+ standard ones, but they don't involve any change, could happen though
+ that we don't list a property that an indicator exposes lazily (don't
+ think there are in real world).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1896785
Title:
Exported DBus interface is missing info or using wrong names
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896785/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896785] Re: Exported DBus interface is missing info or using wrong names
This has been fixed in 34-1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1896785 Title: Exported DBus interface is missing info or using wrong names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I can confirm this bug is fixed when I updated mutter to 3.36.1-1ubuntu0.20.04.1. Using NVIDIA Graphics card. -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896785] [NEW] Exported DBus interface is missing info or using wrong names
Public bug reported:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods and
properties are missing or invalid
[ Test case ]
Run:
gdbus call --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher \
--method org.freedesktop.DBus.Properties.Get "org.kde.StatusNotifierWatcher"
ProtocolVersion
-> Should return (<0>,)
In particular, the API should contain
gdbus introspect --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher
node /StatusNotifierWatcher {
Default fdo properties stuff
interface org.kde.StatusNotifierWatcher {
interface org.kde.StatusNotifierWatcher {
methods:
RegisterStatusNotifierItem(in s service);
RegisterStatusNotifierHost(in s service);
signals:
StatusNotifierItemRegistered(s arg_0);
StatusNotifierItemUnregistered(s arg_0);
StatusNotifierHostRegistered();
StatusNotifierHostUnregistered();
properties:
@org.qtproject.QtDBus.QtTypeName.Out0("QStringList")
readonly as RegisteredStatusNotifierItems = [ ... list of indicators
path/obj-names ... ];
readonly b IsStatusNotifierHostRegistered = true;
readonly i ProtocolVersion = 0;
};
};
In the old version we had an invalid "RegisterNotificationHost" method (not
specified by specs nor used)
We didn't expose the ProtocolVersion
** Affects: gnome-shell-extension-appindicator (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1896785
Title:
Exported DBus interface is missing info or using wrong names
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896785/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896073] Re: SRU the current 2.3.6 stable update
** Also affects: tracker (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896073 Title: SRU the current 2.3.6 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896073/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881669] Re: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: + [ Impact ] + + Destroying an appindicator dbusmenu we fail with some (non-fatal) errors + + [ Test case ] + + Open/Close an application with appindicator + Ensure that gnome-shell journal (journalctl -b0 /usr/bin/gnome-shell) doesn't show any error related to + + Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While reading menu layout: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1. + Jun 01 17:24:15 cerberus gnome-shell[3318]: JS ERROR: TypeError: this._proxy is null + DBusClient<._beginRequestProperties@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:247:9 + wrapper@resource:///org/gnome/gjs/modules + + [ Regression potential ] + + Indicator may not show at all, but that was what we expect on + destruction. + + --- + jlquinn@cerberus:~$ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 jlquinn@cerberus:~/Videos$ apt-cache policy gnome-shell-extension-appindicator gnome-shell-extension-appindicator: - Installed: 18.04.1 - Candidate: 18.04.1 - Version table: - *** 18.04.1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 18.04.1 + Candidate: 18.04.1 + Version table: + *** 18.04.1 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages + 100 /var/lib/dpkg/status - - This may be related to bug 1879016, but my stack trace is smaller and different. I enabled the appindicator extension, and see the following my logs: + This may be related to bug 1879016, but my stack trace is smaller and + different. I enabled the appindicator extension, and see the following + my logs: Jun 01 17:24:15 cerberus gnome-shell[3318]: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it. Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: == Stack trace for context 0x5582a28894b0 == Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #0 0x7ffc718eda00 b resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f70f00b5de0 @ 87) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #1 0x5582a2c5a930 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93 (0x7f6ee00 Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #2 0x7ffc718ee5e0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #3 0x7ffc718eed80 b self-hosted:916 (0x7f70f00f12b8 @ 367) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #4 0x7ffc718eee70 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f70f00d2230 @ 386) - Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #5 0x5582a2c5a8a8 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190 (0x7f6ee00adf78 + Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #5 0x5582a2c5a8a8 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190 (0x7f6ee00adf78 Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #6 0x7ffc718efac0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #7 0x5582a2c5a800 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:176 (0x7f6e Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #8 0x7ffc718f06a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #9 0x5582a2c5a760 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:170 (0x7f6e Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #10 0x7ffc718f1290 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #11 0x7ffc718f1a50 b self-hosted:918 (0x7f70f00f12b8 @ 394) Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While reading menu layout: Gio.DBusError:
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Update to mutter 3.36.1-1ubuntu0.20.04.1 in focal/proposed also fixed the bug for AMD. Good work, thanks and cheers! :-) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870795] Re: Appindicator not showing under wayland
This was fixed by version 34-1 ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #235 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/235 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870795] Re: Appindicator not showing under wayland
Upstream issue: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/235 Upstream fix: https://github.com/ubuntu/gnome-shell-extension-appindicator/pull/231 ** Description changed: + [ Impact ] + + An app-indicator icon does not show when I login using the default gnome + session (wayland). If I choose the xorg session, the icon shows as + normal. Under wayland, the icon does appear if I lock my session then + log back in. + + [ Test case ] + + Run a desktop session (better if Ubuntu wayland), ensure that all the + startup-launched appindicators are showing in the status area. + + One affected indicator seems to be + https://github.com/juliagoda/antimicroX/ + + [ Regression potential ] + + Indicators may not load at all, wrong icons are shown instead. + + --- + + Upstream change: https://github.com/ubuntu/gnome-shell-extension- + appindicator/pull/231 + + $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gnome-session-wayland gnome-session-wayland: - Installed: (none) - Candidate: 3.36.0-2ubuntu1 - Version table: - 3.36.0-2ubuntu1 500 - 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages - 500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages + Installed: (none) + Candidate: 3.36.0-2ubuntu1 + Version table: + 3.36.0-2ubuntu1 500 + 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages + 500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages - An app-indicator icon does not show when I login using the default gnome - session (wayland). If I choose the xorg session, the icon shows as - normal. Under wayland, the icon does appear if I lock my session then - log back in. - - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 15:30:40 2020 InstallationDate: Installed on 2019-12-15 (111 days ago) - InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) - SourcePackage: gnome-session + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-03-10 (24 days ago) ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720334] Re: Indicator applet not launched at all. Shows error at extensions page.
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1720334 Title: Indicator applet not launched at all. Shows error at extensions page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1720334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1894666] Re: Gnome high CPU preventing login after screen lock
Daniel, after further extensive testing and trialling. I can confirm that the high CPU problem does not occur when I disable all GNOME extensions. When no gnome-extensions were enabled the problem did not occur. However, I was able to make the high CPU problem appear by running the dock gnome-extension. I have noted a reduction in the frequency of this problem after the recent set of patches. As you are already tracking a similar issue caused by gnome-extensions I am happy for you to close this ticket. However I am also willing to send you any further information if you want more data. Regards, Fausto. -- 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/1894666 Title: Gnome high CPU preventing login after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896779] [NEW] Appindicators use too much padding
Public bug reported: [ Impact ] Padding on indicators is too wide, as per double-multiplication of the same, leading to very spread icons: https://user- images.githubusercontent.com/16012374/77627511-505f3780-6f47-11ea- 9d65-ec9053290b2f.png [ Test case ] - Open various indicator, padding should be reduced to be consistent with other icons, for example: https://user-images.githubusercontent.com/16012374/77627515-52c19180-6f47-11ea-8edb-9861ad518f8e.png [ Regression potential ] Very low, there's just a style change to ensure we don't apply the very same padding two times. -- Upstream fix: https://github.com/ubuntu/gnome-shell-extension- appindicator/pull/219 ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: New => In Progress ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #246 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/246 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1896779 Title: Appindicators use too much padding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896779] Re: Appindicators use too much padding
Upstream issue https://github.com/ubuntu/gnome-shell-extension- appindicator/issues/246 ** Description changed: [ Impact ] Padding on indicators is too wide, as per double-multiplication of the same, leading to very spread icons: https://user- images.githubusercontent.com/16012374/77627511-505f3780-6f47-11ea- 9d65-ec9053290b2f.png - [ Test case ] - Open various indicator, padding should be reduced to be consistent with other icons, for example: - https://user-images.githubusercontent.com/16012374/77627515-52c19180-6f47-11ea-8edb-9861ad518f8e.png - + https://user-images.githubusercontent.com/16012374/77627515-52c19180-6f47-11ea-8edb-9861ad518f8e.png [ Regression potential ] Very low, there's just a style change to ensure we don't apply the very same padding two times. + + -- + + Upstream fix: https://github.com/ubuntu/gnome-shell-extension- + appindicator/pull/219 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1896779 Title: Appindicators use too much padding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1654839] Re: shared-mime-info detects all binary files as shared libraries
** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #11 https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/11 ** Also affects: shared-mime-info via https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/11 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1654839 Title: shared-mime-info detects all binary files as shared libraries To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1654839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881669] Re: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it
This was fixed by gnome-shell-extension-appindicator 34-1 ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Fix Released ** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1881669 Title: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1881669/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896334] Re: SRU 3.36.6
On gnome-shell, we now understand there are complications with API breakage in microreleases, so we need a plan for reverse dependency shell extensions to mitigate potential regressions. Discussion at https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041. I don't think we can proceed with the gnome-shell microrelease update until we have a plan for this. I don't think it makes sense to proceed with yaru-theme either until this is resolved, since I understand that's based on the gnome-shell update that is not concluded yet. I don't understand why yaru-theme needs to be updated, either. I see that this has been done for yaru-theme once before, but I've found no explanation as to why. The current queue diff has: diff --git a/debian/README.source b/debian/README.source new file mode 100644 index 000..84c9d3c --- /dev/null +++ b/debian/README.source @@ -0,0 +1,3 @@ +The `gnome-shell/upstream` directory is just for documentation and +to allow three way merges when updating to new versions of gnome-shell, +and it is not used for generating the final packages at all If this isn't used for generating the final packages at all, why do you propose to make users download an update? ** Changed in: yaru-theme (Ubuntu Focal) Status: In Progress => Incomplete ** Changed in: gnome-shell (Ubuntu Focal) Status: In Progress => Incomplete -- 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/1896334 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I tried the PPA suggested in post 122 (https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1870736/comments/122) last night. No luck I'm running Pop OS 20.04 and the displays control panel does not even have fractional scaling buttons to try. I just have choices for "100% 200% 300% 400%" So it is possible the fix from 122 might work if I had the GUI options to try. Apparently out of sheer coincidence, my updates showed a new "Nvidia 450" driver available. Applied the update and rebooted but I still do not see a settings option for fractional scaling. I know this is not a Pop OS support ticket but is anyone aware of another mechanism to attempt fractional scaling? I am going to ask the same on Pop OS support. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
probably fixed on shared-mime-info 2.0: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896637] Re: system booting is too slow. Application like chrome, spotify, Libre Office, etc open too slow.
adding 'journalctl -b 0' from a session having the issue. ** Attachment added: "Adding 'journalctl -b 0' as file journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896637/+attachment/5413471/+files/journalctl.txt -- 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/1896637 Title: system booting is too slow. Application like chrome, spotify, Libre Office, etc open too slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
> dpkg -S /usr/bin/mimetype libfile-mimeinfo-perl: /usr/bin/mimetype > /usr/bin/mimetype --magic-only foo.py foo.py: application/xhtml+xml ** Package changed: kde-cli-tools (Ubuntu) => shared-mime-info (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1857824 Title: kmimetypefinder5 misidentifies mimetype of python files containing certain strings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1857824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1893555] Re: gnome-terminal wrapper doesn't wait for the process to exit
This bug was fixed in the package gnome-terminal - 3.38.0-1ubuntu1 --- gnome-terminal (3.38.0-1ubuntu1) groovy; urgency=medium * Merge with debian, remaining changes: - gnome-terminal.wrap, debian/rules: - Add a wrapper script to restore command line compatibility. + debian/control.in: - gnome-terminal depends on python3, python3-gi and gir1.2-glib-2.0 for the wrapper script. - add a build dependency on gettext to match the configure requirement + Add 0001-Restore-transparency.patch: - Restore transparency support + Add 0001-Add-style-classes-and-CSS-names-to-some-of-our-widge.patch: - Add CSS names and style classes so we can theme things more easily. + Add 0001-screen-window-Extra-padding-around-transparent-termi.patch: - Fix transparency on Wayland. Patch by Owen Taylor, via Debarshi Ray @ Fedora + Add 52_support_apturl.patch: - Support apt: urls. + Add 60_add_lp_handler.patch: - Add a handler for launchpad bug URLs. + Add scrollbar-background-theming.patch: - Draw background under the scrollbar that matches the actual terminal background color. This allows proper theming. -- Marco Trevisan (Treviño) Tue, 22 Sep 2020 21:03:04 +0200 ** Changed in: gnome-terminal (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1893555 Title: gnome-terminal wrapper doesn't wait for the process to exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
> dpkg -S /usr/bin/mimetype libfile-mimeinfo-perl: /usr/bin/mimetype > /usr/bin/mimetype --magic-only foo.html foo.html: application/x-perl ** Changed in: shared-mime-info (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857824] [NEW] kmimetypefinder5 misidentifies mimetype of python files containing certain strings
You have been subscribed to a public bug:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: shared-mime-info (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
kmimetypefinder5 misidentifies mimetype of python files containing certain
strings
https://bugs.launchpad.net/bugs/1857824
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is subscribed to shared-mime-info in Ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896416] Re: screen locking no longer works
Thank you for your bug report. Could you add your 'journalctl -b 0' log after getting the issue? gnome-screensaver is an old legacy component that isn't needed nor installed nowadays so it's not what you need to lock the screen, you should be able to test with that command though $ dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- 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/1896416 Title: screen locking no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
