[Desktop-packages] [Bug 2037055] Re: gnome-shell crashed with SIGABRT: ERROR:../src/shell-app.c:1644:shell_app_dispose: assertion failed: (app->state == SHELL_APP_STATE_STOPPED)
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037055 Title: gnome-shell crashed with SIGABRT: ERROR:../src/shell- app.c:1644:shell_app_dispose: assertion failed: (app->state == SHELL_APP_STATE_STOPPED) Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Running MATLAB 2023b with Matlab Connector installed suddenly crashed gnome-shell and returned to gdm. Has been running fine w/o the Connector but not sure it's related. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 10:05:51 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-18 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 ??? () at /usr/lib/gnome-shell/libshell-13.so g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libgjs.so.0 Title: gnome-shell crashed with SIGABRT in ???() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2037055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037055] Re: gnome-shell crashed with SIGABRT: ERROR:../src/shell-app.c:1644:shell_app_dispose: assertion failed: (app->state == SHELL_APP_STATE_STOPPED)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7045 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7045 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7045 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037055 Title: gnome-shell crashed with SIGABRT: ERROR:../src/shell- app.c:1644:shell_app_dispose: assertion failed: (app->state == SHELL_APP_STATE_STOPPED) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Running MATLAB 2023b with Matlab Connector installed suddenly crashed gnome-shell and returned to gdm. Has been running fine w/o the Connector but not sure it's related. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 10:05:51 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-18 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 ??? () at /usr/lib/gnome-shell/libshell-13.so g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libgjs.so.0 Title: gnome-shell crashed with SIGABRT in ???() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2037055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037210] Re: unable to add PPA by its sources.list line
** Tags added: rls-mm-incoming ** Changed in: software-properties (Ubuntu) Status: New => Confirmed ** Also affects: software-properties Importance: Undecided Status: New ** Changed in: software-properties Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2037210 Title: unable to add PPA by its sources.list line Status in Software Properties: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte Adding repository. E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main Components: ' Description: This PPA provides patched libwnck3 package to fix https://github.com/mate-desktop/mate-panel/issues/1230 and https://pad.lv/1947420 . See details at https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 . This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade WNCK packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck Adding repository. Found existing deb entry in /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo apt-get update E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-common 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback Date: Sun Sep 24 14:02:10 2023 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago) 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: 2023-09-24T13:25:34.901411 To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/2037210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2023776
Title:
Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Status in mutter package in Ubuntu:
Expired
Bug description:
Currently using Nvidia driver 525, which is the "tested" and
recommended driver according to Ubuntu's additional driver tool (as of
this writing).
- manually resizing "files" windows = low fps and a little bit of
pixelation
- moving windows around = drop in fps every now and then
- opening the Gnome overview = sometimes buttery smooth 60fps but
sometimes stuttery low fps that takes time to "catch up" to smoothness
again
- resizing Chromium or Firefox window = low fps, glitchy window
behaviour etc.
How to fix it? Well, this is what I found works thus far:
- disable both "vsync" and "allow flipping" in Nvidia-settings
- now everything is buttery smooth again; all animations, apps, games
and more
- doing this will introduce lots of tearing on the Gnome desktop and
applications though
- then force full composition pipeline to get rid of the tearing by
adding this start-up line to Ubuntu's start-up applications: nvidia-
settings --assign CurrentMetaMode="nvidia-auto-select +0+0
{ForceFullCompositionPipeline=On}"
- Use Wayland alternatively: Wayland doesn't have any of these issues
at all, it's a buttery smooth fully vsynced experience ootb, but a
bunch of new problems arise instead: Can't set global hotkeys for
recording in OBS, OBS recording performance is pretty bad, Gnome
folder windows start flickering somestimes, Gnome windows glitch out
when trying to resize them manually, Steam flickering sometimes,
browsers such as Firefox and Chromium have to be set to Wayland mode
in order to solve stuttering video playback issues, Nvidia-settings is
missing a bunch of settings and features when compared to X11... and
more
Hard- and Software:
- Ubuntu 23.04
- Nvidia driver version 525 (tested) from Ubuntu's additional drivers tool
- Core i7 7700
- 32 GB DDR4 RAM
- Lenovo Nvidia RTX A2000 workstation GPU
- TWO fullHD monitors connected via display port
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 14:58:08 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-20 (24 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.1-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037235] Re: 45.0: vsync broken in many games, with dual monitors
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2037235 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: mantic wayland-session ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037235 Title: 45.0: vsync broken in many games, with dual monitors Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Bug description: I put all the details upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 Affected version Ubuntu 23.10, Wayland session Regression between 45.rc and 45.0. Dual 4K monitors, 100% desktop scaling. Bug summary The framerate goes way over vsync even with Sync to vsync set in all games tested so far. Steps to reproduce I compiled vanilla Mutter from source and bisected it to dfd58ca8 !3259 (merged) , reverting that on top of main fixes the problem again. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037191] Re: Lockscreen sometimes doesn't render
Also please clarify: "the touchscreen just doesn't render" implies that nothing is visible. Hence no information has been exposed until after "sudo loginctl unlock-sessions"? If that's the case then there would be no security issue. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037191 Title: Lockscreen sometimes doesn't render Status in gnome-shell package in Ubuntu: Incomplete Bug description: Sometimes when I unlock my laptop by opening the lid, the touchscreen just doesn't render. This renders the system completely frozen until I go into a TTY and run "sudo loginctl unlock-sessions". But that's not the real problem. The real problem is that while the lock-screen doesn't render, *everything* else does. This means that while I wasn't logged in, Firefox and all other open applications were completely visible. This is obviously a big issue if one has sensitive information open. There does not seem to be a reliable way to reproduce this, it just happens sometimes. So far, I've experienced this twice, once on 23.04 and once on the 23.10 beta. There are however, some really suspicious error messages in the logs: Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1809 (3e69d1677920 @ 73) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1812 (3e69d1677920 @ 124) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1988 (3e69d1677fb0 @ 112) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:112 (2f81e37d600 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:289 (2f81e37dc40 @ 39) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:115 (2f81e37d600 @ 91) Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
[Desktop-packages] [Bug 2037191] Re: Lockscreen sometimes doesn't render
The "real problem" you mention is being tracked in bug 1532508. Please also review the workaround for bug 1876632 in case that's related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037191 Title: Lockscreen sometimes doesn't render Status in gnome-shell package in Ubuntu: Incomplete Bug description: Sometimes when I unlock my laptop by opening the lid, the touchscreen just doesn't render. This renders the system completely frozen until I go into a TTY and run "sudo loginctl unlock-sessions". But that's not the real problem. The real problem is that while the lock-screen doesn't render, *everything* else does. This means that while I wasn't logged in, Firefox and all other open applications were completely visible. This is obviously a big issue if one has sensitive information open. There does not seem to be a reliable way to reproduce this, it just happens sometimes. So far, I've experienced this twice, once on 23.04 and once on the 23.10 beta. There are however, some really suspicious error messages in the logs: Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1809 (3e69d1677920 @ 73) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1812 (3e69d1677920 @ 124) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1988 (3e69d1677fb0 @ 112) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:112 (2f81e37d600 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:289 (2f81e37dc40 @ 39) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:115 (2f81e37d600 @ 91) Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176) Sep 23 17:31:26
[Desktop-packages] [Bug 2037188] Re: My External Monitor Crashes
Can you explain in more detail what you mean by "monitor crashes"? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2037188 Title: My External Monitor Crashes Status in Ubuntu: Incomplete Bug description: My external monitor crashes after a while of using. This is consistent accross different monitors ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 21:53:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d1] InstallationDate: Installed on 2023-04-27 (149 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 20WNS3QV00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2022 dmi.bios.release: 1.50 dmi.bios.vendor: LENOVO dmi.bios.version: N35ET50W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20WNS3QV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.41 dmi.modalias: dmi:bvnLENOVO:bvrN35ET50W(1.50):bd09/15/2022:br1.50:efr1.41:svnLENOVO:pn20WNS3QV00:pvrThinkPadT14sGen2i:rvnLENOVO:rn20WNS3QV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20WN_BU_Think_FM_ThinkPadT14sGen2i: dmi.product.family: ThinkPad T14s Gen 2i dmi.product.name: 20WNS3QV00 dmi.product.sku: LENOVO_MT_20WN_BU_Think_FM_ThinkPad T14s Gen 2i dmi.product.version: ThinkPad T14s Gen 2i dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2037188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037141] Re: Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary
This is because the Wayland surface includes the window shadows which go out to the edge of the red rectangle. It's an understandable bug but could always be better. ** Tags added: multimonitor ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037141 Title: Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary Status in gnome-shell package in Ubuntu: Confirmed Bug description: On a dual/multi monitor setup, if the monitor adjacent uses a different scale factor, when moving an application window to the boundary the application will change its scaling just slightly before the actual apparent window starts crossing over. Taking a look at looking glass shows the transition occurs when the MetaSurfaceActorWayland region (larger than the actual window) meets the boundary. My monitor configuration is: 1920X1080 monitor using 100% scaling 2560X1600 monitor using 150% scaling ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 00:22:04 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037161] Re: drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110
** Tags added: lunar ** Package changed: gdm3 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2037161 Title: drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110 Status in linux package in Ubuntu: Incomplete Bug description: I noticed that when I choose Wayland to logon to my Ubuntu 23.04 desktop PC, the display would crash at least once within 6 hours. Crash means total dark screen. Mouse,keyboard, or replugging the HDMI cable doesn't have any effects. Once the display crashes, ssh is possible but reboot commands would time out. sudo commands take more than 10 seconds. The problem does not occur if I choose xorg to logon to the desktop. The hardware specifications are: amd-ryzen5-4600g description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 15GiB *-cpu product: AMD Ryzen 5 4600G with Radeon Graphics vendor: Advanced Micro Devices [AMD] physical id: 1 bus info: cpu@0 version: 23.96.1 size: 4291MHz capacity: 4307MHz width: 64 bits Kernel info: uname -a Linux amd-ryzen5-4600g 6.2.0-32-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 14 10:03:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux more logs in the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037115] Re: Focus is not given when a new window is launched from overview
** Tags added: focus lunar ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2690 https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Fix Released ** Also affects: mutter (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Status: New => Fix Committed ** Tags added: fixed-in-mutter-44.4 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037115 Title: Focus is not given when a new window is launched from overview Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: Ubuntu 23.04 Lunar Mutter 44.3 upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037182] Re: Restarting GNOME doesn't work
Although it may have been: https://gitlab.gnome.org/GNOME/mutter/-/issues/2977 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037182 Title: Restarting GNOME doesn't work Status in gnome-shell package in Ubuntu: Incomplete Bug description: Triggering a restart through Alt-F2 then "r" causes GNOME to hang for a few seconds before going to the "something went wrong" screen prompting the user to log out. But once you log out and back in, the system still has issues, with application now taking far longer to launch. This is ultimately resolved by a full system restart. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 14:56:37 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (53 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037182] Re: Restarting GNOME doesn't work
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2977 https://gitlab.gnome.org/GNOME/mutter/-/issues/2977 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037182 Title: Restarting GNOME doesn't work Status in gnome-shell package in Ubuntu: Incomplete Bug description: Triggering a restart through Alt-F2 then "r" causes GNOME to hang for a few seconds before going to the "something went wrong" screen prompting the user to log out. But once you log out and back in, the system still has issues, with application now taking far longer to launch. This is ultimately resolved by a full system restart. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 14:56:37 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (53 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
Unfortunately that log doesn't contain a gnome-shell crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
** Tags removed: kinetic ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2000644 Title: switching workspaces with shortcut sometimes freezes screen Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The bottom panel with dots to show which workspace you are on when switching with ctrl+alt+arrow sometimes doesn't disappear and gets stuck in a half faded or not faded state. In that state the mouse appear stuck and the screen freezes until the super key is pressed to show overview or the workspace is switched again. Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand, Nvidia driver 525.60.11 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
I recall this bug was reported around last cycle too. But I wonder; is it specific to Nvidia desktops like bug 1876632? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Confirmed Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037166] Re: Entering/Waking up from sleep kills active session
*** This bug is a duplicate of bug 2034619 *** https://bugs.launchpad.net/bugs/2034619 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2034619, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2034619 [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037166 Title: Entering/Waking up from sleep kills active session Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: I have reported this bug against gdm3 but I do not know if it is the cause of the bug. My experience is this: I work on my laptop as usual, and I may have an application loaded. This could be anything - my browser, a temrinal or even just nautilus. Why my laptop goes to sleep either manually through the top right menu or I type sleep of suspend into the application launcher, or if it's automatically by letting the laptop fall asleep automatically after a period of time or I close the laptop lid, when I next wake from sleep my active session will be terminated. All applications which were running will no longer be running. I have fully reinstalled my mantic instance, and have also ensured that my packages are all up to date, but the problem persists. Additional Drivers and Firmware Updates are reporting that there is nothing to install or update. ``` $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 12:41:07 2023 InstallationDate: Installed on 2023-09-20 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230919) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2037166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037088] Re: While using secondary display - Top right display not responsive
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2012388, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug is no longer a duplicate of bug 2037141 Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary ** This bug has been marked a duplicate of bug 2012388 X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037088 Title: While using secondary display - Top right display not responsive Status in gnome-shell package in Ubuntu: New Bug description: While I am using my laptop (main screen) and have my secondary screen plugged in I cannot click anything in the top right corner. Ether in toolbar or top right pixels of an open app. Problem occuring on Mantic Minotaur beta, working on lunar. Freshed installed Ubuntu with defauls. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
This is fixed in the 23.10 dailies. I'm not sure it's really practical to fix this for the next 22.04 point release, unfortunately. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released ** Changed in: subiquity Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Jammy: Confirmed Bug description: With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037011] Re: Can't create ovpn
Worth noting this looks to be a bug in the official GNOME 45 release? ** Also affects: network-manager-openvpn (Fedora) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/2037011 Title: Can't create ovpn Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-openvpn package in Fedora: New Bug description: Settings -> Network -> Add VPN -> Import from file to import an .ovpn file does nothing after clicking Add, it just returns to the Add VPN page and no VPN connection is added. The same .ovpn file works fine in 22.04. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager-openvpn 1.10.2-3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 22:12:58 2023 InstallationDate: Installed on 2023-09-18 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/2037011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037235] Re: 45.0: vsync broken in many games, with dual monitors
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037235 Title: 45.0: vsync broken in many games, with dual monitors Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: I put all the details upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 Affected version Ubuntu 23.10, Wayland session Regression between 45.rc and 45.0. Dual 4K monitors, 100% desktop scaling. Bug summary The framerate goes way over vsync even with Sync to vsync set in all games tested so far. Steps to reproduce I compiled vanilla Mutter from source and bisected it to dfd58ca8 !3259 (merged) , reverting that on top of main fixes the problem again. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037235] [NEW] 45.0: vsync broken in many games, with dual monitors
Public bug reported: I put all the details upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 Affected version Ubuntu 23.10, Wayland session Regression between 45.rc and 45.0. Dual 4K monitors, 100% desktop scaling. Bug summary The framerate goes way over vsync even with Sync to vsync set in all games tested so far. Steps to reproduce I compiled vanilla Mutter from source and bisected it to dfd58ca8 !3259 (merged) , reverting that on top of main fixes the problem again. ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3035 https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037235 Title: 45.0: vsync broken in many games, with dual monitors Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I put all the details upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 Affected version Ubuntu 23.10, Wayland session Regression between 45.rc and 45.0. Dual 4K monitors, 100% desktop scaling. Bug summary The framerate goes way over vsync even with Sync to vsync set in all games tested so far. Steps to reproduce I compiled vanilla Mutter from source and bisected it to dfd58ca8 !3259 (merged) , reverting that on top of main fixes the problem again. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037228] Re: Firefox doesn't work after 23.10 upgrade
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: firefox (Ubuntu) Importance: Undecided => High ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Tags added: mantic rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037143] Re: Autohide enabled Dock scaling breaks on multi monitor with different scale factors (low to high scale)
** Description changed: The dock with autohide enabled breaks scaling on multi monitor setups - when revealed from a hidden state if it is on the edge of the monitor - adjacent to the other monitor where the next monitor has a higher scale - factor. In my case the dock is on the monitor with 100% scale factor and - the monitor adjacent has 150% scaling. + when revealed from being hidden by an overlapping window by moving the + overlapping window away, if it is on the edge of the monitor adjacent to + the other monitor where the next monitor has a higher scale factor. In + my case the dock is on the monitor with 100% scale factor and the + monitor adjacent has 150% scaling. When the bug occurs a bunch of the following messages appear in the log: gnome-shell[4226]: Can't update stage views actor [:0x562389bfc9e0] is on because it needs an allocation. I suspect this could be linked to my findings in this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141 Attached a screencast demonstrating the bug. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 87ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 01:57:23 2023 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2037143 Title: Autohide enabled Dock scaling breaks on multi monitor with different scale factors (low to high scale) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The dock with autohide enabled breaks scaling on multi monitor setups when revealed from being hidden by an overlapping window by moving the overlapping window away, if it is on the edge of the monitor adjacent to the other monitor where the next monitor has a higher scale factor. In my case the dock is on the monitor with 100% scale factor and the monitor adjacent has 150% scaling. When the bug occurs a bunch of the following messages appear in the log: gnome-shell[4226]: Can't update stage views actor [:0x562389bfc9e0] is on because it needs an allocation. I suspect this could be linked to my findings in this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141 Attached a screencast demonstrating the bug. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 87ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 01:57:23 2023 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2037143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()
Confirmed on bare metal, running 23.10, on a MSI GE 76 Raider 11UE.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2016217
Title:
gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
from GjsAutoPointer()
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
44.0-2ubuntu3, the problem page at
https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
#0 0x7f3aa429dd82 in clutter_actor_remove_effect
(self=self@entry=0x55d60fa59e90, effect=0x55d6101c48a0) at
../clutter/clutter/clutter-actor.c:14830
__inst = 0x55d6101c48a0
__t = 94377826055744
__r =
_g_boolean_var_274 =
__func__ = "clutter_actor_remove_effect"
#1 0x7f3aa3f9d27f in st_scroll_view_dispose (object=0x55d60fa59e90) at
../src/st/st-scroll-view.c:246
priv = 0x55d60fa59a00
#2 0x7f3aa4aeada0 in g_object_unref (_object=0x55d60fa59e90) at
../../../gobject/gobject.c:3891
_pp =
gaig_temp =
gaig_temp =
weak_locations =
nqueue = 0x55d60fa6da60
_ptr =
object = 0x55d60fa59e90
old_ref =
retry_atomic_decrement1 =
__func__ = "g_object_unref"
#3 0x7f3aa43b4b2c in GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::reset (ptr=0x0, this=) at ../gjs/jsapi-util.h:229
old_ptr =
#4 GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::~GjsAutoPointer (this=, this=) at
../gjs/jsapi-util.h:172
No locals.
#5 GjsSmartPointer<_GObject>::~GjsSmartPointer (this=,
this=) at ../gjs/jsapi-util.h:349
No locals.
#6 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1524
No locals.
#7 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1500
No locals.
#8 0x7f3aa43c9ec0 in ObjectInstance::~ObjectInstance (this=, this=) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1945
was_using_toggle_refs = false
had_toggle_up = false
had_toggle_down =
had_toggle_up =
had_toggle_down =
was_using_toggle_refs =
#9 GIWrapperInstance::finalize_impl (this=0x55d60fa0ce80) at ../gi/wrapperutils.h:1113
No locals.
#10 ObjectInstance::finalize_impl (gcx=, obj=0x35b1abd24820,
this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1912
query = {type = 94377830362416, type_name = 0x7f3aa3fdcda6
"StScrollView", class_size = 664, instance_size = 48}
query =
_g_boolean_var_74 =
#11 GIWrapperBase::finalize
(gcx=, obj=0x35b1abd24820) at ../gi/wrapperutils.h:411
priv = 0x55d60fa0ce80
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2016217/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035027] Re: GNOME crashes after resume when using Wayland
*** This bug is a duplicate of bug 2016217 *** https://bugs.launchpad.net/bugs/2016217 Confirmed on bare metal (MSI GE76 Raider 11UE - Nvidia RTX 3060 6GB). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035027 Title: GNOME crashes after resume when using Wayland Status in gnome-shell package in Ubuntu: Confirmed Bug description: Sometimes, not always, when I'm back to my computer after entered in stand-by mode (display turned off, sometimes screen locked), the session crashes and comes back to GDM. It just happens with Wayland, never with Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 10 10:59:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-30 (11 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035027] Re: GNOME crashes after resume when using Wayland
*** This bug is a duplicate of bug 2016217 *** https://bugs.launchpad.net/bugs/2016217 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035027 Title: GNOME crashes after resume when using Wayland Status in gnome-shell package in Ubuntu: Confirmed Bug description: Sometimes, not always, when I'm back to my computer after entered in stand-by mode (display turned off, sometimes screen locked), the session crashes and comes back to GDM. It just happens with Wayland, never with Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 10 10:59:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-30 (11 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2034664 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037221] [NEW] Gtk very broken, ubuntu control center crashes 'playbin' element not found
Public bug reported: Right click on desktop "display settings" does nothing, using gnome- control-center display or gnome-control-center throws the following error: 16:20:10.6842 GStreamer-Play[41314]: ERROR: GtkGstPlay: 'playbin' element not found, please check your setup Trace/breakpoint trap (core dumped) I am using 23.04 but it did work at the beginning. I assume it might have broken when I hastily reversed a pipewire->pule audio mod (had to disable pipewire in 22.10 since RDP would give no sound) since my microphone didn't work at first. Now everything works but the gnome control center (and my webcam which I newly installed but not sure it's connected). Similar to: Bug #2017498 1) Description:Ubuntu 23.04 Release:23.04 2) gnome-control-center: Installed: 1:44.0-1ubuntu6 Candidate: 1:44.0-1ubuntu6 Version table: *** 1:44.0-1ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:44.0-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 3) I would expect the command center to just open. 4) nothing happens (right click on desktop and "display settings") or using gnome-control-center display throws the above mentioned error message. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu6 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Sep 24 16:31:26 2023 InstallationDate: Installed on 2023-06-24 (92 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-09-18 (6 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037221 Title: Gtk very broken, ubuntu control center crashes 'playbin' element not found Status in gnome-control-center package in Ubuntu: New Bug description: Right click on desktop "display settings" does nothing, using gnome- control-center display or gnome-control-center throws the following error: 16:20:10.6842 GStreamer-Play[41314]: ERROR: GtkGstPlay: 'playbin' element not found, please check your setup Trace/breakpoint trap (core dumped) I am using 23.04 but it did work at the beginning. I assume it might have broken when I hastily reversed a pipewire->pule audio mod (had to disable pipewire in 22.10 since RDP would give no sound) since my microphone didn't work at first. Now everything works but the gnome control center (and my webcam which I newly installed but not sure it's connected). Similar to: Bug #2017498 1) Description: Ubuntu 23.04 Release: 23.04 2) gnome-control-center: Installed: 1:44.0-1ubuntu6 Candidate: 1:44.0-1ubuntu6 Version table: *** 1:44.0-1ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:44.0-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 3) I would expect the command center to just open. 4) nothing happens (right click on desktop and "display settings") or using gnome-control-center display throws the above mentioned error message. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu6 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Sep 24 16:31:26 2023 InstallationDate: Installed on 2023-06-24 (92 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-09-18 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037217] Re: loop ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
*** This bug is a duplicate of bug 2034664 *** https://bugs.launchpad.net/bugs/2034664 I believe this is caused by the Tiling Assistant extension that is enabled by default in Ubuntu. Therefore, I'm marking this a duplicate of the bug tracking that issue. ** This bug has been marked a duplicate of bug 2034664 Meta.Rectangle is deprecated, use Mtk.Rectangle instead -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037217 Title: loop ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell package in Ubuntu: New Bug description: loop: 1 cpu 100% Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.482 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Sep 24 13:36:35 2023 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230923) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus: Unknown Status in ardour package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Status in ardour package in Debian: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ardour (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus: Unknown Status in ardour package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Status in ardour package in Debian: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Attachment added: "Capture d’écran du 2023-09-24 15-44-45.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704098/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-44-45.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Attachment added: "Capture d’écran du 2023-09-24 15-44-18.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704097/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-44-18.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
I got it working on a 2015 MacBook Air 7.2 From a 23.04 fresh installation it didin't work neither with a 22.04 fresh installation. I tried all the tricks I found over internet and nothing worked. I then had first to install an old Ubuntu 20.04 and block the version of the following packages bcmwl-kernel-source linux-headers-5-10.0.84 linux-headers-5-10.0.84-generic linux-modules-5-10.0.84-generic. Now I have a fresh 23.04 version with Wifi on a Broadcom BCM 4360 14e4:43a0. It seems defintely to be a bug since it worked perfectly out-of-the-box with other distros such as Fedora or Arch. ** Attachment added: "Capture d’écran du 2023-09-24 15-43-57.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704096/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-43-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037217] [NEW] loop ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Public bug reported: loop: 1 cpu 100% Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.482 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Sep 24 13:36:35 2023 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230923) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037217 Title: loop ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell package in Ubuntu: New Bug description: loop: 1 cpu 100% Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 24 13:32:04 ubuntu gnome-shell[3161]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.482 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Sep 24 13:36:35 2023 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230923) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037212] [NEW] ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Public bug reported:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Affects: bluez (Debian)
Importance: Unknown
Status: Unknown
** Tags: amd64 apport-bug mantic
** Bug watch added: Debian Bug tracker #1017988
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988
** Also affects: bluez (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037212
Title:
ConfigurationDirectory 'bluetooth' already exists but the mode is
different. (File system: 755 ConfigurationDirectoryMode: 555)
Status in bluez package in Ubuntu:
New
Status in bluez package in Debian:
Unknown
Bug description:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
To manage notifications about this bug go to:
[Desktop-packages] [Bug 2037210] [NEW] unable to add PPA by its sources.list line
Public bug reported: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte Adding repository. E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main Components: ' Description: This PPA provides patched libwnck3 package to fix https://github.com/mate-desktop/mate-panel/issues/1230 and https://pad.lv/1947420 . See details at https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 . This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade WNCK packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck Adding repository. Found existing deb entry in /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo apt-get update E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-common 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback Date: Sun Sep 24 14:02:10 2023 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago) 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: 2023-09-24T13:25:34.901411 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2037210 Title: unable to add PPA by its sources.list line Status in software-properties package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using
[Desktop-packages] [Bug 1629633] Re: evince displays blank thumbnails for some pages
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1629633 Title: evince displays blank thumbnails for some pages Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: Hi, To reproduce this bug: - load the attached PS file into evince - if thumbnails are not displayed then press F9 and choose to display thumbnails - evince displayd a blank thumbnail for pages 6 and 7 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 10:10:28 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1629633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748895]
*** Bug 138158 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803604]
*** Bug 138158 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762133] Re: gvfsd-smb-browse crashed with SIGABRT
I am closing this bug since I have not seen it again since my report. Thanks! ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1762133 Title: gvfsd-smb-browse crashed with SIGABRT Status in gvfs package in Ubuntu: Fix Released Bug description: I was not even using a SMB share when gvfsd-smb-browse crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.36.0-1ubuntu1 Uname: Linux 4.15.15-041515-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 7 22:06:05 2018 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.64 /org/gtk/gvfs/exec_spaw/10 Signal: 6 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2 _talloc_free () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2 () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 gencache_parse () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 gencache_get_data_blob () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 Title: gvfsd-smb-browse crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1762133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799675] Re: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
In recent versions, gnome-control-center refuses to run under another desktop environment: $ gnome-control-center Running gnome-control-center is only supported under GNOME and Unity, exiting -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1799675 Title: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell- model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8de5ebcde9e4492a3bc570a4caa376cefbdfcbec contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1799675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877725] Re: Displays aberrant percentages for disks belonging to btrfs RAID volume
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in GNOME Disks: New Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1877725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid ** Changed in: lightdm Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: Invalid Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Invalid Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945907] Re: tracker-miner-fs-3 crashed with SIGSEGV
I am closing this bug since I have not seen a tracker crash since then. Thanks! ** Changed in: tracker-miners (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1945907 Title: tracker-miner-fs-3 crashed with SIGSEGV Status in tracker-miners package in Ubuntu: Fix Released Bug description: I found a file in /var/crash after upgrading my system to Ubuntu 21.10 ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: tracker-miner-fs 3.1.3-1 Uname: Linux 5.14.9-051409-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 3 17:26:55 2021 ExecutablePath: /usr/libexec/tracker-miner-fs-3 ProcCmdline: /usr/libexec/tracker-miner-fs-3 SegvAnalysis: Segfault happened at: 0x7fb88ead6b97:mov0x8(%rax),%rcx PC (0x7fb88ead6b97) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker-miners StacktraceTop: () at /lib/x86_64-linux-gnu/libtracker-sparql-3.0.so.0 g_task_return_now (task=0x5585cc574d80) at ../../../gio/gtask.c:1219 complete_in_idle_cb (task=0x5585cc574d80) at ../../../gio/gtask.c:1233 g_main_dispatch (context=0x5585cc569180) at ../../../glib/gmain.c:3337 g_main_context_dispatch (context=0x5585cc569180) at ../../../glib/gmain.c:4055 Title: tracker-miner-fs-3 crashed with SIGSEGV UpgradeStatus: Upgraded to impish on 2021-10-03 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1945907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968901] Re: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968901 Title: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file Status in mutter package in Ubuntu: Confirmed Bug description: Hi, when I boot my system, the following warning message is logged: # journalctl | grep /var/lib/gdm3 Apr 13 18:22:56 vougeot org.gnome.Shell.desktop[3472]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10f526ebe1d06fb2ad1649866974815191003453.ms”: No such file or directory Note that the missing file depends on the system. For instance, on another system: # journalctl | grep /var/lib/gdm3 Apr 13 14:34:45 jophur org.gnome.Shell.desktop[791]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10a247c4d323226d33164985328443594000779.ms”: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 18:15:28 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969015] Re: Recursion depth exceeded calculating colors
The bug has been fixed in mantic. Thanks! ** Changed in: yelp (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1969015 Title: Recursion depth exceeded calculating colors Status in yelp package in Ubuntu: Fix Released Bug description: Hi, here is the problem: $ yelp Recursion depth exceeded calculating green bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark fg color. Using rgb(80,82,81) Recursion depth exceeded calculating red bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark bg color. Using rgb(250,250,250) Recursion depth exceeded calculating yellow bg color. Using rgb(250,250,250) Recursion depth exceeded calculating orange bg color. Using rgb(254,250,250) Recursion depth exceeded calculating gray bg color. Using rgb(250,250,250) Recursion depth exceeded calculating purple bg color. Using rgb(250,250,250) Recursion depth exceeded calculating blue bg color. Using rgb(250,250,250) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 42.1-1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 10:10:44 2022 SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1969015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968910 Title: Extension NAME already installed in /usr/share/gnome- shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I see the following error messages in the system logs about gnome- shell extensions: # journalctl | grep Extension [...] Apr 13 18:30:51 jophur gnome-shell[831]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 19:57:37 2022 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
The bug was in cups.
** Changed in: okular (Ubuntu)
Status: Confirmed => Invalid
** Changed in: atril (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Invalid
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Invalid
Status in cups source package in Jammy:
Fix Released
Status in cups source package in Lunar:
Fix Released
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013324] Re: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed-tests/gtk+/scrolledwindow
I am closing this bug since it has been fixed in mantic. Thanks! ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2013324 Title: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed- tests/gtk+/scrolledwindow Status in Ubuntu: Fix Released Bug description: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 30 12:05:24 2023 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2013324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013544] Re: font names displayed in an unreadable way
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2013544 Title: font names displayed in an unreadable way Status in gnome-font-viewer package in Ubuntu: New Bug description: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
Hi, the bug is still there on an Ubuntu 23.10/mantic system: # journalctl | grep has_option Sep 22 13:46:02 xeelee /usr/libexec/gdm-x-session[2101]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found Sep 22 13:46:03 xeelee /usr/libexec/gdm-x-session[2123]: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Sep 22 13:46:03 xeelee /usr/libexec/gdm-x-session[2150]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ** Tags added: lunar mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
