[Desktop-packages] [Bug 1841929] Re: Volume up/down repeat keys don't work on Xorg
This is a regression for our vast majority of users using the normal ubuntu product and quite visible one, I wouldn't put it as low. ** Changed in: gnome-shell (Ubuntu) Importance: Low => High ** Changed in: mutter (Ubuntu) Importance: Low => High -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+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 1834794] Re: Uses too much memory (6Gbyte process)
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834794 Title: Uses too much memory (6Gbyte process) Status in pulseaudio package in Ubuntu: Expired Bug description: So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in memory. version: 1:11.1-1ubuntu7.2 OS: Ubuntu 18.04.2 LTS System uptime: 11 days Desktop: GNOME pmap output: $ pmap 25499 25499: /usr/bin/pulseaudio --start --log-target=syslog 55e3bb805000 84K r-x-- pulseaudio 55e3bba1a000 4K r pulseaudio 55e3bba1b000 4K rw--- pulseaudio 55e3bd1b9000132K rw--- [ anon ] 55e3bd1da000 3671036K rw--- [ anon ] 7f705c00 65536K rw-s- memfd:pulseaudio (deleted) 7f706000 65536K rw-s- memfd:pulseaudio (deleted) 7f706400 65536K rw-s- memfd:pulseaudio (deleted) 7f706800 65536K rw-s- memfd:pulseaudio (deleted) 7f706c00 65536K rw-s- memfd:pulseaudio (deleted) 7f707000 65536K rw-s- memfd:pulseaudio (deleted) 7f707400 65536K rw-s- memfd:pulseaudio (deleted) 7f707800 65536K rw-s- memfd:pulseaudio (deleted) 7f707c00 65536K rw-s- memfd:pulseaudio (deleted) 7f708000 65536K rw-s- memfd:pulseaudio (deleted) 7f708400 65536K rw-s- memfd:pulseaudio (deleted) 7f708800 65536K rw-s- memfd:pulseaudio (deleted) 7f70bc00 65536K rw-s- memfd:pulseaudio (deleted) 7f70c000 65536K rw-s- memfd:pulseaudio (deleted) 7f70c400 65536K rw-s- memfd:pulseaudio (deleted) 7f70c800 65536K rw-s- memfd:pulseaudio (deleted) 7f70ec00 65536K rw-s- memfd:pulseaudio (deleted) 7f70f000 65536K rw-s- memfd:pulseaudio (deleted) 7f70f400 65536K rw-s- memfd:pulseaudio (deleted) 7f70f800 65536K rw-s- memfd:pulseaudio (deleted) 7f70fc00 65536K rw-s- memfd:pulseaudio (deleted) 7f71 65536K rw-s- memfd:pulseaudio (deleted) 7f710400 65536K rw-s- memfd:pulseaudio (deleted) 7f710800 65536K rw-s- memfd:pulseaudio (deleted) 7f710c00 65536K rw-s- memfd:pulseaudio (deleted) 7f711000 65536K rw-s- memfd:pulseaudio (deleted) 7f711400 65536K rw-s- memfd:pulseaudio (deleted) 7f711800 65536K rw-s- memfd:pulseaudio (deleted) 7f711c00172K rw--- [ anon ] 7f711c02b000 65364K - [ anon ] 7f7120957000 24K r-x-- libuuid.so.1.3.0 7f712095d000 2044K - libuuid.so.1.3.0 7f7120b5c000 4K r libuuid.so.1.3.0 7f7120b5d000 4K rw--- libuuid.so.1.3.0 7f7120b5e000 28K r-x-- libSM.so.6.0.1 7f7120b65000 2044K - libSM.so.6.0.1 7f7120d64000 4K r libSM.so.6.0.1 7f7120d65000 4K rw--- libSM.so.6.0.1 7f7120d66000 92K r-x-- libICE.so.6.3.0 7f7120d7d000 2044K - libICE.so.6.3.0 7f7120f7c000 4K r libICE.so.6.3.0 7f7120f7d000 4K rw--- libICE.so.6.3.0 7f7120f7e000 12K rw--- [ anon ] 7f7120f81000 8K r-x-- module-x11-xsmp.so 7f7120f83000 2048K - module-x11-xsmp.so 7f7121183000 4K r module-x11-xsmp.so 7f7121184000 4K rw--- module-x11-xsmp.so 7f7121185000 68K r-x-- libXext.so.6.4.0 7f7121196000 2044K - libXext.so.6.4.0 7f7121395000 4K r libXext.so.6.4.0 7f7121396000 4K rw--- libXext.so.6.4.0 7f7121397000 20K r-x-- libXtst.so.6.1.0 7f712139c000 2044K - libXtst.so.6.1.0 7f712159b000 4K r libXtst.so.6.1.0 7f712159c000 4K rw--- libXtst.so.6.1.0 7f712159d000 8K r-x-- module-x11-cork-request.so 7f712159f000 2044K - module-x11-cork-request.so 7f712179e000 4K r module-x11-cork-request.so 7f712179f000 4K rw--- module-x11-cork-request.so 7f71217a 8K r-x-- module-x11-bell.so 7f71217a2000 2044K - module-x11-bell.so 7f71219a1000 4K r module-x11-bell.so 7f71219a2000 4K rw--- module-x11-bell.so 7f71219a3000 12K r-x-- module-x11-publish.so 7f71219a6000 2044K - module-x11-publish.so 7f7121ba5000 4K r module-x11-publish.so 7f7121ba6000 4K rw--- module-x11-publish.so 7f7121ba7000 8K r-x-- libcli.so 7f7121ba9000 2044K - libcli.so 7f7121da8000 4K r libcli.so 7f7121da9000 4K rw--- libcli.so 7f7121daa000 8K r-x-- libprotocol-cli.so 7f7121dac000 2044K - libprotocol-cli.so 7f7121fab000 4K r libprotocol-cli.so 7f7121fac000 4K rw--- libprotocol-cli.so
[Desktop-packages] [Bug 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
A black frame can also mean a zero FB ID, IIRC... Can you tell if the backlight is going off? -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. Because the GPU powers down quite aggressively (I think it's about 5sec without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-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/1842009/+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 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
Regardless, please also create an upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. Because the GPU powers down quite aggressively (I think it's about 5sec without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-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/1842009/+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
Re: [Desktop-packages] [Bug 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
It looks like modesetting, or at least a destructive probe of the attached displays. There's nothing KMS related in dmesg corresponding to the blanking, so I don't think it's an invalid FB (I'd expect i915 to spit something in dmesg in that case) -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. Because the GPU powers down quite aggressively (I think it's about 5sec without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-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/1842009/+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 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
dmesg output attached ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+attachment/5285718/+files/dmesg.txt -- 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/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: 2015 15" Macbook Pro, Integrated graphics. Description: Ubuntu 19.04 Release: 19.04 On occasion when I right-click on an item or two on the desktop to move to trash the Gnome Wayland session will lockup forcing me to hard reboot. Upon reboot, the items will be deleted as expected however. This has happened multiple times since I did a fresh install of 19.04, the most recent was just after booting. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-09 (79 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell-extension-desktop-icons PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Tags: wayland-session disco Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+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 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
Journal output attached ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+attachment/5285717/+files/journal.txt -- 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/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: 2015 15" Macbook Pro, Integrated graphics. Description: Ubuntu 19.04 Release: 19.04 On occasion when I right-click on an item or two on the desktop to move to trash the Gnome Wayland session will lockup forcing me to hard reboot. Upon reboot, the items will be deleted as expected however. This has happened multiple times since I did a fresh install of 19.04, the most recent was just after booting. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-09 (79 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell-extension-desktop-icons PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Tags: wayland-session disco Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+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 1841929] Re: Volume up/down repeat keys don't work on Xorg
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Importance: Undecided => Low -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+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 1841929] Re: Volume up/down repeat keys don't work on Xorg
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/1841929 Title: Volume up/down repeat keys don't work on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+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 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
Can you tell if the "blanking" is either: * The output entering sleep mode; or * A black frame being accidentally flipped. I guess checking if the backlight is still on would answer that. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags added: wayland ** Tags added: hybrid -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. Because the GPU powers down quite aggressively (I think it's about 5sec without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-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/1842009/+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 1841929] Re: Volume up/down repeat keys don't work on Xorg
** 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/1841929 Title: Volume up/down repeat keys don't work on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+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 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
or * An invalid framebuffer being accidentally flipped. -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. Because the GPU powers down quite aggressively (I think it's about 5sec without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-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/1842009/+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 1841679] Re: [nvidia] Login screen never wakes after sleeping and there is no way to recover
Please do it again and instead of saving the apport just copy the link and open it on another machine. You can then complete the new bug creation in the browser of that other machine. -- 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/1841679 Title: [nvidia] Login screen never wakes after sleeping and there is no way to recover Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This was recreated on a System76 Serval WS (serw11) on Ubuntu 18.04 with the following versions of packages: ```cat /etc/os-release NAME="Ubuntu" VERSION="18.04.3 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.3 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic apt policy gdm3 gdm3: Installed: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 Candidate: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev Version table: *** 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 100 100 /var/lib/dpkg/status 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev 1001 1001 http://ppa.launchpad.net/system76-dev/stable/ubuntu bionic/main amd64 Packages 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages apt policy gnome-shell gnome-shell: Installed: 3.28.4-0ubuntu18.04.1 Candidate: 3.28.4-0ubuntu18.04.1 Version table: *** 3.28.4-0ubuntu18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.3+git20190124-0ubuntu18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` Here are the steps to recreate the issue: The blank screen issue can be recreated very easily: Power on system - NOT LIVE DISK. It gets to the ubuntu login screen. Do NOT login and stay at this screen until the screen goes blank. try to wake screen and unable to. only course of action here is to hard power off. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev [origin: LP-PPA-system76-dev-stable] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Tags: bionic third-party-packages Uname: Linux 5.0.0-23-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841679/+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 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
Please try: 1. Open a Terminal window and run: journalctl -f 2. Right click on the desktop and reproduce this bug. 3. Do you see any new messages in the Terminal window? -- 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/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: 2015 15" Macbook Pro, Integrated graphics. Description: Ubuntu 19.04 Release: 19.04 On occasion when I right-click on an item or two on the desktop to move to trash the Gnome Wayland session will lockup forcing me to hard reboot. Upon reboot, the items will be deleted as expected however. This has happened multiple times since I did a fresh install of 19.04, the most recent was just after booting. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-09 (79 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell-extension-desktop-icons PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Tags: wayland-session disco Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+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 1841673] Re: GNOME Shell crashed
** Changed in: gnome-shell (Ubuntu) Status: Fix Released => Invalid -- 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/1841673 Title: GNOME Shell crashed Status in gnome-shell package in Ubuntu: Invalid Bug description: Photo of the problem: https://photos.app.goo.gl/D8PfrYnG2dt4B6N97 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 00:04:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-25 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-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/1841673/+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 1831369] Re: Gnome Shell pauses and stutters while waiting (several seconds) for programs to launch
Thanks. That doesn't seem to show any single recurring problem though. So it looks like log file flushing is not the explanation for this bug. I wonder if disk performance is a factor. Can you please run: lsblk and sudo hdparm -I /dev/sda and send the output? -- 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/1831369 Title: Gnome Shell pauses and stutters while waiting (several seconds) for programs to launch Status in gnome-shell package in Ubuntu: Incomplete Bug description: My laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 4 GB RAM, Ubuntu 19.04 Details in my video: https://photos.app.goo.gl/ERUaSS6Qc8jFhHnn9 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 14:32:17 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-05-31 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash 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/1831369/+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 1842009] [NEW] [Wayland] Screen blanks for a second whenever discrete GPU is powered up
Public bug reported: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. Because the GPU powers down quite aggressively (I think it's about 5sec without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. + + Because the GPU powers down quite aggressively (I think it's about 5sec + without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell 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 in Ubuntu. https://bugs.launchpad.net/bugs/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up Status in gnome-shell package in Ubuntu: New Bug description: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. Because the GPU powers down quite aggressively (I think it's about 5sec without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-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/1842009/+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 1815172] Autopkgtest regression report (mesa/19.0.8-0ubuntu0~18.04.2)
All autopkgtests for the newly accepted mesa (19.0.8-0ubuntu0~18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: vtk6/unknown (armhf) kf5-messagelib/4:17.12.3-0ubuntu3 (armhf) firefox/68.0.2+build1-0ubuntu0.18.04.1 (armhf) openjdk-8/8u222-b10-1ubuntu1~18.04.1 (i386, s390x, arm64, armhf, ppc64el, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1841412] Autopkgtest regression report (mesa/19.0.8-0ubuntu0~18.04.2)
All autopkgtests for the newly accepted mesa (19.0.8-0ubuntu0~18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: vtk6/unknown (armhf) kf5-messagelib/4:17.12.3-0ubuntu3 (armhf) firefox/68.0.2+build1-0ubuntu0.18.04.1 (armhf) openjdk-8/8u222-b10-1ubuntu1~18.04.1 (i386, s390x, arm64, armhf, ppc64el, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841412 Title: Build with NDEBUG again Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Bug description: [Impact] Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. This means that some asserts are enabled, and at least nouveau is affected. [Test case] chech the build log that -DNDEBUG is passed [Regression potential] none really, it just adds a build flag which should've been there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1841412/+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 1809507] Re: gnome crashes when opening gnome-control-center
** Also affects: nouveau Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1809507 Title: gnome crashes when opening gnome-control-center Status in Nouveau Xorg driver: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Version information: Ubuntu Release: Ubuntu 18.10 xserver-xorg-video-nouveau: 1:1.0.15-3 gnome-control-center: 3.30.2 Expected Behavior: Launching gnome-control-center should show Ubuntu settings. What Happens: Launching gnome-control-center causes gnome to crash, resulting in user being logged out and returned to login screen. Further Information: I ran `gnome-control-center -v > out.log 2>&1&` to investigate and get the following in the log... nvc0_screen_create:983 - Error allocating PGRAPH context for M2MF: -16 XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 11 requests (11 known processed) with 0 events remaining. Disabling gnome extensions does not help. Switching to proprietary drivers resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1809507/+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 1841679] Re: [nvidia] Login screen never wakes after sleeping and there is no way to recover
This is not a dual GPU system, only the Nvidia GPU is usable. -- 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/1841679 Title: [nvidia] Login screen never wakes after sleeping and there is no way to recover Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This was recreated on a System76 Serval WS (serw11) on Ubuntu 18.04 with the following versions of packages: ```cat /etc/os-release NAME="Ubuntu" VERSION="18.04.3 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.3 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic apt policy gdm3 gdm3: Installed: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 Candidate: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev Version table: *** 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 100 100 /var/lib/dpkg/status 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev 1001 1001 http://ppa.launchpad.net/system76-dev/stable/ubuntu bionic/main amd64 Packages 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages apt policy gnome-shell gnome-shell: Installed: 3.28.4-0ubuntu18.04.1 Candidate: 3.28.4-0ubuntu18.04.1 Version table: *** 3.28.4-0ubuntu18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.3+git20190124-0ubuntu18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` Here are the steps to recreate the issue: The blank screen issue can be recreated very easily: Power on system - NOT LIVE DISK. It gets to the ubuntu login screen. Do NOT login and stay at this screen until the screen goes blank. try to wake screen and unable to. only course of action here is to hard power off. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev [origin: LP-PPA-system76-dev-stable] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Tags: bionic third-party-packages Uname: Linux 5.0.0-23-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841679/+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 1841679] Re: [nvidia] Login screen never wakes after sleeping and there is no way to recover
When running 'apport-cli --hanging $(pidof gnome-shell)' in a ssh shell, it wants to spawn a browser to login to launchpad.net; since it did not, I saved the apport and linked it here. After I ran the killall command and ran the ubuntu-bug command it did not show an ID to link here. ** Attachment added: "apport.gnome-shell.oeeef49r.apport" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841679/+attachment/5285702/+files/apport.gnome-shell.oeeef49r.apport -- 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/1841679 Title: [nvidia] Login screen never wakes after sleeping and there is no way to recover Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This was recreated on a System76 Serval WS (serw11) on Ubuntu 18.04 with the following versions of packages: ```cat /etc/os-release NAME="Ubuntu" VERSION="18.04.3 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.3 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic apt policy gdm3 gdm3: Installed: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 Candidate: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev Version table: *** 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 100 100 /var/lib/dpkg/status 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev 1001 1001 http://ppa.launchpad.net/system76-dev/stable/ubuntu bionic/main amd64 Packages 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages apt policy gnome-shell gnome-shell: Installed: 3.28.4-0ubuntu18.04.1 Candidate: 3.28.4-0ubuntu18.04.1 Version table: *** 3.28.4-0ubuntu18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.3+git20190124-0ubuntu18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` Here are the steps to recreate the issue: The blank screen issue can be recreated very easily: Power on system - NOT LIVE DISK. It gets to the ubuntu login screen. Do NOT login and stay at this screen until the screen goes blank. try to wake screen and unable to. only course of action here is to hard power off. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7~dev [origin: LP-PPA-system76-dev-stable] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Tags: bionic third-party-packages Uname: Linux 5.0.0-23-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841679/+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 1792300] Re: Chromium Speech Synthesis Not Working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1792300 Title: Chromium Speech Synthesis Not Working Status in chromium-browser package in Ubuntu: Confirmed Bug description: In Ubuntu 16.04.5, Firefox supports Speech Synthesis by utilizing Text-To-Speech voices provided by default from the operating system. In Windows 10, both both Firefox and Chrome support Speech Synthesis by utilizing Text-To-Speech voices provided by default from the operating system. However,in Chromium 68 and 69, although the API is supported, Chromium cannot speak, because it doesn't seem to know how to load those Text- To-Speech voices that Firefox is successfully utilizing. Here's what users said at Ask Ubuntu, regarding the issue: https://askubuntu.com/questions/761975/ For example, this page should speak the text is shows: http://www.lonniebest.com/CardTrick/ The link above does not work in Chromium 69 on Ubuntu, however it does work in the following browser/os combinations: - Firefox (Ubuntu 16.04.5) - Chrome (Windows 10) - Firefox (Windows 10) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 69.0.3497.81-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 00:38:53 2018 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2018-09-12 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Load-Avg-1min: 0.51 Load-Processes-Running-Percent: 0.1% MachineType: System76 Bonobo WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=c57c4be3-fe0f-4162-804e-627e28920546 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04RSA5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Bonobo WS dmi.board.vendor: System76 dmi.board.version: bonw13 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Bonobo WS dmi.product.version: bonw13 dmi.sys.vendor: System76 modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1792300/+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 1422004] Re: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop'
The thread at https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1430561? is quite active in 2019, due to possibly unrelated issue. In any case, I managed to get firmware to load and scanning to work in Debian 10, and what I did is listed at : https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1430561/comments/39 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1422004 Title: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop' Status in HPLIP: Fix Committed Status in hplip package in Ubuntu: Fix Released Status in hplip source package in Vivid: Fix Released Bug description: If an HP printer needs HPLIP with HP's proprietary plug-in (firmware files for printers, proprietary driver code pieces for printing and/or scanning) the automatically initiated installation of the plug-in fails and causes crash reports, leading to crash report pop-ups and non-working printing and scanning functionality. The problem is caused by the switchover from Python2 to Python3 in Vivid, especially also that the Python3 executable is named "python3" and not "python". If the crash happens shortly before shutdown or reboot the pop-up can appear right after log-in. [Impact] All Vivid users who use a printer or multi-function device which needs HP's proprietary plug-in get crash pop-ups and their devices will not completely work or not work at all. [Test Case] Connect an HP printer or multi-function device which needs the plug-in (for which models see this bug report and the numerous duplicates) and set it up. As soon as the plug-in gets downloaded and installed, crash reports pop up, and the devices functionality which needs the plug-in will not work as plug-in installation does not complete. The proposed package solves the problem. To test without having an appropriate printer, simply run the command hp-plugin in a terminal window. With the current package it will fail as mentioned, with the proposed package plug-in installation will succeed. [Regression Potential] Very low. The patch is trivial and it affects only users who need the plug-in. All users of other HP printers or non-HP printers are not affected. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: hplip-data 3.15.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CupsErrorLog: E [14/Feb/2015:19:56:52 +0100] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. Date: Sat Feb 14 05:59:51 2015 ExecutablePath: /usr/share/hplip/pkservice.py InstallationDate: Installed on 2014-05-08 (282 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 Lpstat: device for HP-Deskjet-1000-J110-series: usb://HP/Deskjet%201000%20J110%20series?serial=CN33A18VXG05YD device for PDF: cups-pdf:/ MachineType: Acer Aspire 5943G PackageArchitecture: all Papersize: a4 PpdFiles: HP-Deskjet-1000-J110-series: HP Deskjet 1000 j110 Series, hpcups 3.15.2 PDF: Generic CUPS-PDF Printer ProcCmdline: /usr/bin/python3 /usr/bin/hp-pkservice ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic root=UUID=e9be64c9-5b7e-438a-ac82-6b89bf946a86 ro quiet splash vt.handoff=7 PythonArgs: ['/usr/bin/hp-pkservice'] SourcePackage: hplip Title: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/21/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5943G dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnAcer:bvrV1.15:bd10/21/2010:svnAcer:pnAspire5943G:pvrV1.15:rvnAcer:rnAspire5943G:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire 5943G dmi.product.version: V1.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1422004/+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 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed
*** This bug is a duplicate of bug 1422004 *** https://bugs.launchpad.net/bugs/1422004 I had this sort of problem on Debian 10, and found several things which together got scanning working for me on HP Color LaserJet Pro MFP M277dw. I hope the proceedure below is of help to someone else. 1. Fix the source for the gpg key to avoid the problem with the pgp.mit.edu server: sudo cp -a /usr/share/hplip/base/validation.py /usr/share/hplip/base/validation.py.ORIG vim /usr/share/hplip/base/validation.py # replace pgp.mit.edu with pool.sks-keyservers.net on line 44 2. After getting the plugin to install using "hp-plugin" as a regular user and the root password when requested, the software still complained... 3. It seems that hplip expects the libraries in a different location than where they are getting installed: find /usr/lib -name "*sane*" | grep hp2000S sudo ln -s /usr/lib /usr/lib/i386-linux-gnu sudo ln -s /usr/lib64 /usr/lib64/x86_64-linux-gnu (Based on https://bugs.launchpad.net/hplip/+bug/1818629) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1430561 Title: hp-plugin crashes with error: Python gobject/dbus may be not installed Status in HPLIP: Confirmed Status in One Hundred Papercuts: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: When trying to configure an HP LaserJet P1102w, when running hp-plugin I get errors and can not proceed: nessita@miro:~$ hp-plugin error: Unable to locate models.dat file HP Linux Imaging and Printing System (ver. 3.15.2) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9 Creating directory plugin_tmp Verifying archive integrity... All good. Uncompressing HPLIP 3.15.2 Plugin Self Extracting Archive... Error importing HPLIP modules. Is HPLIP installed? error: Python gobject/dbus may be not installed error: Plug-in install failed. Done. nessita@miro:~$ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: hplip 3.15.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 19:23:41 2015 InstallationDate: Installed on 2014-11-30 (100 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet MachineType: LENOVO 3249CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago) dmi.bios.date: 10/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET61WW (1.31 ) dmi.board.name: 3249CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1430561/+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 1841673] Re: GNOME Shell crashed
After a while I have been not noticed the same problem, so I believe it had fixed. So I think we can change the status from "Incomplete" to "Fix released". ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1841673 Title: GNOME Shell crashed Status in gnome-shell package in Ubuntu: Fix Released Bug description: Photo of the problem: https://photos.app.goo.gl/D8PfrYnG2dt4B6N97 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 00:04:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-25 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-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/1841673/+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
Re: [Desktop-packages] [Bug 1841673] Re: GNOME Shell crashed
"No errors have been reported from this system" чт, 29 авг. 2019 г. в 04:50, Daniel van Vugt : > Please follow the steps in comment #2, or choose one of the above bugs > you would like this to be a duplicate of. > > ** Changed in: gnome-shell (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1841673 > > Title: > GNOME Shell crashed > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Photo of the problem: https://photos.app.goo.gl/D8PfrYnG2dt4B6N97 > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-shell 3.33.91-1ubuntu1 > ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 > Uname: Linux 5.2.0-13-generic x86_64 > ApportVersion: 2.20.11-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 28 00:04:20 2019 > DisplayManager: gdm3 > InstallationDate: Installed on 2019-08-25 (2 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) > ProcEnviron: >LANGUAGE=ru_UA:ru >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ru_UA.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: mutter-common 3.33.91-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/1841673/+subscriptions > -- 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/1841673 Title: GNOME Shell crashed Status in gnome-shell package in Ubuntu: Fix Released Bug description: Photo of the problem: https://photos.app.goo.gl/D8PfrYnG2dt4B6N97 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 00:04:20 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-25 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-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/1841673/+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 1841740] Re: Xwayland crashed with SIGABRT
** Changed in: xorg-server (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1841740 Title: Xwayland crashed with SIGABRT Status in xorg-server package in Ubuntu: Fix Released Bug description: Bug from /var/crash ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20190820-0ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Aug 26 16:43:14 2019 Disassembly: => 0x7f9106b92bfb: Cannot access memory at address 0x7f9106b92bfb DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.10, 5.2.0-10-generic, x86_64: installed virtualbox, 6.0.10, 5.2.0-13-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExecutableTimestamp: 1554282237 GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:832e] InstallationDate: Installed on 2019-08-25 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) MachineType: HP HP 250 G6 Notebook PC ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcCwd: /var/lib/gdm3 ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-13-generic root=UUID=eddd802f-c63c-43de-8f71-99a2367aa661 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () ?? () ?? () UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/17/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.60 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832E dmi.board.vendor: HP dmi.board.version: 26.37 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.60:bd05/17/2019:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.37:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G6 Notebook PC dmi.product.sku: 3DN65ES#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1841740/+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
Re: [Desktop-packages] [Bug 1831369] Re: Gnome Shell pauses and stutters when under heavy load
Please, take the result. P.S. I will try to descibe the different problems in separate apports. Sorry for my mistakes. It's a less of my experience. чт, 29 авг. 2019 г. в 04:45, Daniel van Vugt : > Please be careful to only discuss one problem per bug report. If you're > experiencing multiple problems then please open separate bugs for them. > > Continuing with this bug... > > I suspect the problem here is that disk IO is directly affecting > animations. They shouldn't normally be related to each other, but one > way that can happen is if gnome-shell is blocked in writing a log > message. It can become blocked if there are regular log messages being > written, and then every 5 seconds the kernel will block in order to > flush to disk. > > Please run this command in a Terminal window: > > journalctl -f > > Now reproduce the problem again and please tell us if the Terminal > window shows NEW log messages while the freeze/stutter is happening. > > ** Changed in: gnome-shell (Ubuntu) >Status: Confirmed => Incomplete > > ** Summary changed: > > - Gnome Shell pauses and stutters when under heavy load > + Gnome Shell pauses and stutters while waiting (several seconds) for > programs to launch > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1831369 > > Title: > Gnome Shell pauses and stutters while waiting (several seconds) for > programs to launch > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > My laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 4 GB > RAM, Ubuntu 19.04 > Details in my video: https://photos.app.goo.gl/ERUaSS6Qc8jFhHnn9 > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-shell 3.32.0+git20190410-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 > Uname: Linux 5.0.0-15-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 2 14:32:17 2019 > DisplayManager: gdm3 > GsettingsChanges: >b'org.gnome.shell' b'app-picker-view' b'uint32 1' >b'org.gnome.shell' b'command-history' redacted by apport >b'org.gnome.shell' b'favorite-apps' redacted by apport >b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano']" >b'org.gnome.desktop.interface' b'gtk-im-module' > b"'gtk-im-context-simple'" > InstallationDate: Installed on 2019-05-31 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > ProcEnviron: >LANGUAGE=ru_UA:ru >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ru_UA.UTF-8 >SHELL=/bin/bash > 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/1831369/+subscriptions > ** Attachment added: "bug.txt" https://bugs.launchpad.net/bugs/1831369/+attachment/5285672/+files/bug.txt -- 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/1831369 Title: Gnome Shell pauses and stutters while waiting (several seconds) for programs to launch Status in gnome-shell package in Ubuntu: Incomplete Bug description: My laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 4 GB RAM, Ubuntu 19.04 Details in my video: https://photos.app.goo.gl/ERUaSS6Qc8jFhHnn9 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 14:32:17 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-05-31 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash 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/1831369/+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 1841969] [NEW] chromium-browser crashes with ThreadPoolSingl trap bringing back to login screen
Public bug reported: Just had chromium-browser 76.0.3809.100-0ubuntu0.16.04.1 idling with a few tabs when it crashed bringing down the system back to login screen. dmesg seems clean enough except couple of lines: [22519.604950] do_trap: 23 callbacks suppressed [22519.604953] traps: ThreadPoolSingl[2609] trap int3 ip:5645e00e7a86 sp:7f2779615f00 error:0 in chromium-browser[5645dc7ce000+8cef000] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 76.0.3809.100-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-DP-4: enabled: enabled dpms: On status: connected edid-base64: AP///wAwrqZhAQEBARsbAQSlNR54OgVlp1ZSnCcPUFSv7wDRwIGAgYqVAKnAqc+zAHFPAjqAGHE4LUBYLEUADyghAAAe/wBWVDU4MTMzOAogICAg/QAySw9TEQAKICAgICAg/ABUMjRpLTEwCiAgICAgAT4CAx7xS5AfBRQBAgMEERITIwkHB4MBAABluRQABAACOoDQcjgtQBAsRYAPKCEAAB4BHYDQchwWIBAsJQAPKCEAAJ4BHQC8UtAeILgoVUAPKCEAAB6MCtCQIEAxIAxAVQAPKCEAABgCOoAYcTgtQFgsRQAPKCEAAB4A/A== modes: 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1600x900 1280x1024 1280x1024 1280x1024 1440x900 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAwrqZhAQEBARsbAQNoNR54KgVlp1ZSnCcPUFSv7wDRwIGAgYqVAKnAqc+zAHFPAjqAGHE4LUBYLEUADyghAAAe/wBWVDU4MzMyNQogICAg/QAySx5TFQAKICAgICAg/ABUMjRpLTEwCiAgICAgAHw= modes: 1920x1080 1680x1050 1600x900 1600x900 1280x1024 1280x1024 1280x1024 1440x900 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wANroIUAB8WAQSVHxF4AsZ1l1hTjyckUFQBAQEBAQEBAQEBAQEBAQEBHCpAVGGEGjAwIDUANa4QAAAY/gBOMTQwRkdFLUVBMgog/gBDTU4KICAgICAgICAg/gBOMTQwRkdFLUVBMgogAA4= modes: 1600x900 Date: Thu Aug 29 19:55:23 2019 Desktop-Session: 'awesome' '/etc/xdg/xdg-awesome:/etc/xdg' '/usr/share/awesome:/usr/local/share/:/usr/share/' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: /usr/lib/mozilla/plugins: => libgnome-shell-browser-plugin.so (size: 18920 bytes, mtime: Mon May 29 17:35:13 2017) Load-Avg-1min: 3.91 Load-Processes-Running-Percent: 0.7% MachineType: LENOVO 20ASA10P00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=bff30551-7f63-42cd-abb9-9542063d2913 ro splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: J4ET73WW(1.73) dmi.board.asset.tag: Not Available dmi.board.name: 20ASA10P00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ4ET73WW(1.73):bd12/25/2014:svnLENOVO:pn20ASA10P00:pvrThinkPadL440:rvnLENOVO:rn20ASA10P00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L440 dmi.product.name: 20ASA10P00 dmi.product.version: ThinkPad L440 dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1841969 Title: chromium-browser crashes with ThreadPoolSingl trap bringing back to login screen Status in chromium-browser package in Ubuntu: New Bug description: Just had chromium-browser 76.0.3809.100-0ubuntu0.16.04.1 idling with a few tabs when it crashed bringing down the system back to login screen. dmesg seems clean enough except couple of lines: [22519.604950] do_trap: 23 callbacks suppressed [22519.604953] traps: ThreadPoolSingl[2609] trap int3 ip:5645e00e7a86 sp:7f2779615f00 error:0 in chromium-browser[5645dc7ce000+8cef000] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 76.0.3809.100-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname:
[Desktop-packages] [Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
It's not quite the same as bug 1724977. This doesn't happen when moving the cursor live, but the second copy "appears" after waking from screen lock. My guess is that the lock screen doesn't use the same video memory config as the desktop, but somehow they "overlap" and the cursor gets left over as you log back in from the lock screen. * The fact that the fake cursor image is large makes me think that it isn't using the same scaling * The fact that the fake cursor image is rotated (as if the screen is in normal landscape) makes me think that the lock screen is unaware of the desktop screen rotation. Both of these points may affect the video memory layout which will therefore be different between the desktop and the lock screen... Currently away from the machine, but I will do the apport-collect next week. -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock Status in mutter package in Ubuntu: Incomplete Bug description: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in OEM Priority Project: Fix Released Status in OEM Priority Project bionic series: Fix Released Status in libxkbcommon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1740894/+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 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
** Also affects: xserver-xorg-video-intel Importance: Undecided Status: New ** Package changed: mesa (Ubuntu) => mesa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in Mesa: New Status in xf86-video-intel: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64
[Desktop-packages] [Bug 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
Ran a terminal with dmesg -w running. Generated a 2gb file on my desktop, copied and pasted into home. After "finished copying" notification I right clicked "move to trash", and lockup. Didn't see anything in the console output. -- 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/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: 2015 15" Macbook Pro, Integrated graphics. Description: Ubuntu 19.04 Release: 19.04 On occasion when I right-click on an item or two on the desktop to move to trash the Gnome Wayland session will lockup forcing me to hard reboot. Upon reboot, the items will be deleted as expected however. This has happened multiple times since I did a fresh install of 19.04, the most recent was just after booting. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-09 (79 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell-extension-desktop-icons PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Tags: wayland-session disco Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+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 1841953] [NEW] Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
Public bug reported: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa VDPAU video acceleration drivers coeur-noir@asgard:~$ SuperTuxKart version is : coeur-noir@asgard:~$ dpkg -l | grep supertu ii supertuxkart1.0~ubuntu18.04.1 amd643D kart racing game ii supertuxkart-data 1.0~ubuntu18.04.1 all 3D kart racing game (data) coeur-noir@asgard:~$ IMPORTANT NOTE #1 : I don't have
[Desktop-packages] [Bug 1709781] Re: Screenshots do not work in Wayland session
hi paul, fixed for me! br -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1709781 Title: Screenshots do not work in Wayland session Status in Gnome Screenshot: Incomplete Status in gnome-screenshot package in Ubuntu: Incomplete Bug description: With the current 17.10 builds, it's not possible to take screenshots when using the Wayland session. Expected result: Screenshot of actual screen/application/rectangle taken and either copied to clipboard or saved to file Actual result: No Image, just a black image To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/1709781/+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 1841548] Re: The upstream updates are not really ones
@Till, I'm reopening that bug and keeping it open to document that those are buggy tarballs/not to package, that way our tools stop nagging about an update being available to package ** Summary changed: - Update to 20190826 + The upstream updates are not really ones ** Changed in: foomatic-db (Ubuntu) Status: Fix Released => Triaged ** Tags added: version-blocked -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foomatic-db in Ubuntu. https://bugs.launchpad.net/bugs/1841548 Title: The upstream updates are not really ones Status in foomatic-db package in Ubuntu: Triaged Bug description: There is a new version available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1841548/+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 1834386] Re: Ebooks thumbnails fail in Nemo over SMB
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- 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/1834386 Title: Ebooks thumbnails fail in Nemo over SMB Status in evince package in Ubuntu: Confirmed Bug description: Nemo is unable to generate ebooks thumbnails over SMB share because of evince-thumbnailer apparmor profile(note that Nautilus is able to do it anyway), i removed apparmor to see and it fixed that issue. Nemo output when generating thumbs: - (nemo:31811): CinnamonDesktop-WARNING **: 01:08:30.200: Error creating thumbnail for smb://akem-hp.local/comics_bds_mangas/Scrooge/Uncle%20Scrooge%20(001-100)%20GetComics.INFO/029%20Uncle%20Scrooge.cbr: Unrecognized image file format Error loading remote document: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.243" (uid=1000 pid=1488 comm="evince-thumbnailer -s 128 smb://akem-hp.local/comi" label="/usr/bin/evince-thumbnailer (enforce)") interface="org.gtk.vfs.MountTracker" member="LookupMount" error name="(unset)" requested_reply="0" destination=":1.10" (uid=1000 pid=1725 comm="/usr/lib/gvfs/gvfsd " label="unconfined") (nemo:31811): CinnamonDesktop-WARNING **: 01:08:30.365: Unable to create loader for mime type application/x-cbr: Unrecognized image file format - Note that it does the same with pdf or some other ebooks format. The problem happens in loopback too, just share a folder with ebooks using SMB, flush the thumbnails and open Nemo to that folder via Network(connect to the SMB). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jun 27 02:11:28 2019 InstallationDate: Installed on 2019-05-31 (26 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1834386/+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 1840597] Re: Web Extension API, `browser.search.get` throws error `An unexpected error occurred`
** Branch linked: lp:firefox/stable ** Branch linked: lp:~mozillateam/firefox/firefox.disco -- 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/1840597 Title: Web Extension API, `browser.search.get` throws error `An unexpected error occurred` Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: In Progress Bug description: Web Extension API, `browser.search.get` throws error `An unexpected error occurred` on ubuntu's version of firefox 68 Steps to reproduce 1. Extract attached ff-extensions.zip 2. In the extracted folder, run `web-ext run` 3. In address bar type about:debugging. Temporary extensions 'Test Extension' will be loaded. 4. Click 'Debug' It gives an error in console tab, Error: "An unexpected error occurred" This issue is reproducible only with the Firefox installations from 'Ubuntu Software', not with the Firefox downloads from Mozilla's page. This is the possible root cause for "Tridactyl is broken on ubuntu's version of firefox 68", see https://github.com/tridactyl/tridactyl/issues/1670 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 68.0.1+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anoop 2183 F pulseaudio BuildID: 20190718135155 Channel: Unavailable CurrentDesktop: Unity Date: Mon Aug 19 01:09:47 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-08 (587 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.100 metric 600 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=69.0/20190807220259 (Out of date) Profile0 (Default) - LastVersion=68.0.1/20190718135155 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to xenial on 2018-09-10 (342 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0G0G6Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd08/07/2017:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0G0G6Y:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1840597/+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 1817537] Autopkgtest regression report (libsoup2.4/2.62.1-1ubuntu0.3)
All autopkgtests for the newly accepted libsoup2.4 (2.62.1-1ubuntu0.3) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#libsoup2.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Committed Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1740894] Autopkgtest regression report (systemd/237-3ubuntu10.26)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.26) for bionic have finished running. The following regressions have been reported in tests triggered by the package: network-manager/1.10.6-2ubuntu1.1 (arm64) dovecot/1:2.2.33.2-1ubuntu4.3 (armhf) systemd/237-3ubuntu10.26 (ppc64el) gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in OEM Priority Project: Fix Released Status in OEM Priority Project bionic series: Fix Released Status in libxkbcommon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1740894/+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 1825626] Re: nvLock: client timed out, taking the lock
A discussion at https://forum.manjaro.org/t/desktop-gnome-frequently- get-frozen-few-seconds-and-works-again/81603/29 for manjaro seems to nail down: * It looks related to mutter (a gnome desktop component), since some guys report that the freeze disappears when updating mutter. * It does not seem to appear under under non-gnome desktop. ** Also affects: gnome-desktop Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: 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/1825626 Title: nvLock: client timed out, taking the lock Status in gnome-desktop: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+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 1825626] Re: nvLock: client timed out, taking the lock
Did anyone try setting __GL_MaxFramesAllowed=1 as discussed in https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 ? It helped me to get rid of the lockups on manjaro (didn't try on ubuntu though) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1202 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 -- 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/1825626 Title: nvLock: client timed out, taking the lock Status in gnome-desktop: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+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 1841897] Re: Cursor missing from slider
The first one (global volume) is fixed by Robert already, but the second is not, I just reported that upstream. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #652 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/652 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/652 Importance: Unknown Status: Unknown -- 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/1841897 Title: Cursor missing from slider Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Bug description: There is no cursor on the slider in gnome-control-center (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 09:59:11 2019 InstallationDate: Installed on 2014-07-15 (1870 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-03-24 (522 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1841897/+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 1841929] [NEW] Volume up/down repeat keys don't work on Xorg
Public bug reported: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan rls-ee-incoming ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1554 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1554 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1554 Importance: Unknown Status: Unknown ** Tags added: rls-ee-incoming -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+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 1841696] Re: Upgrade of g-c-c from 1:3.32.2-1ubuntu4 to 1:3.33.90-1ubuntu2 installs media libraries
It's because it recommends rygel now which recommends gst-libav, that goes lowered to a suggest now https://launchpad.net/ubuntu/+source/rygel/0.38.1-2ubuntu2 ** Package changed: gnome-control-center (Ubuntu) => rygel (Ubuntu) ** Changed in: rygel (Ubuntu) Status: New => Fix Released -- 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/1841696 Title: Upgrade of g-c-c from 1:3.32.2-1ubuntu4 to 1:3.33.90-1ubuntu2 installs media libraries Status in rygel package in Ubuntu: Fix Released Bug description: Ex. $ sudo apt -s install gnome-control-center [sudo] password for doug: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libebook-contacts-1.2-2 libip4tc0 libip6tc0 libmysqlclient20 libvpx5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gnome-control-center-data gstreamer1.0-libav i965-va-driver intel-media-va-driver libaacs0 libaom0 libass9 libavcodec58 libavfilter7 libavformat58 libavutil56 libbdplus0 libbluray2 libbs2b0 libchromaprint1 libcodec2-0.8.1 libfftw3-double3 libflite1 libgme0 libgsm1 libgssdp-1.2-0 libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libigdgmm9 liblilv-0-0 libmysofa0 libnorm1 libopenjp2-7 libopenmpt0 libpgm-5.2-0 libpostproc55 librubberband2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libserd-0-0 libshine3 libsnappy1v5 libsord-0-0 libsratom-0-0 libssh-gcrypt-4 libswresample3 libswscale5 libva-drm2 libva-x11-2 libva2 libvdpau1 libvidstab1.1 libx264-155 libx265-176 libxvidcore4 libzmq5 libzvbi-common libzvbi0 mesa-va-drivers mesa-vdpau-drivers rygel va-driver-all vdpau-driver-all Suggested packages: gnome-user-share realmd libcanberra-gtk-module i965-va-driver-shaders libbluray-bdj libfftw3-bin libfftw3-dev serdi sordi rygel-playbin rygel-preferences rygel-ruih rygel-tracker tumbler gstreamer1.0-plugins-ugly libvdpau-va-gl1 nvidia-vdpau-driver nvidia-legacy-340xx-vdpau-driver nvidia-legacy-304xx-vdpau-driver The following NEW packages will be installed: gstreamer1.0-libav i965-va-driver intel-media-va-driver libaacs0 libaom0 libass9 libavcodec58 libavfilter7 libavformat58 libavutil56 libbdplus0 libbluray2 libbs2b0 libchromaprint1 libcodec2-0.8.1 libfftw3-double3 libflite1 libgme0 libgsm1 libgssdp-1.2-0 libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libigdgmm9 liblilv-0-0 libmysofa0 libnorm1 libopenjp2-7 libopenmpt0 libpgm-5.2-0 libpostproc55 librubberband2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libserd-0-0 libshine3 libsnappy1v5 libsord-0-0 libsratom-0-0 libssh-gcrypt-4 libswresample3 libswscale5 libva-drm2 libva-x11-2 libva2 libvdpau1 libvidstab1.1 libx264-155 libx265-176 libxvidcore4 libzmq5 libzvbi-common libzvbi0 mesa-va-drivers mesa-vdpau-drivers rygel va-driver-all vdpau-driver-all The following packages will be upgraded: gnome-control-center gnome-control-center-data 2 upgraded, 60 newly installed, 0 to remove and 14 not upgraded. Inst gnome-control-center [1:3.32.2-1ubuntu4] (1:3.33.90-1ubuntu2 Ubuntu:19.10/eoan [amd64]) [] Inst gnome-control-center-data [1:3.32.2-1ubuntu4] (1:3.33.90-1ubuntu2 Ubuntu:19.10/eoan [all]) ect., ect. Whereas upgrading g-c-c-data does not, ex. $ sudo apt -s install gnome-control-center-data [sudo] password for doug: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libebook-contacts-1.2-2 libip4tc0 libip6tc0 libmysqlclient20 libvpx5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gnome-control-center Suggested packages: gnome-user-share realmd libcanberra-gtk-module Recommended packages: rygel | rygel-tracker The following packages will be upgraded: gnome-control-center gnome-control-center-data 2 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. Inst gnome-control-center [1:3.32.2-1ubuntu4] (1:3.33.90-1ubuntu2 Ubuntu:19.10/eoan [amd64]) [] Inst gnome-control-center-data [1:3.32.2-1ubuntu4] (1:3.33.90-1ubuntu2 Ubuntu:19.10/eoan [all]) Conf gnome-control-center (1:3.33.90-1ubuntu2 Ubuntu:19.10/eoan [amd64]) Conf gnome-control-center-data (1:3.33.90-1ubuntu2 Ubuntu:19.10/eoan [all]) Would also happen with software-updater , doesn't with apt-get. Possibly this will sort itself out?? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux
[Desktop-packages] [Bug 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed ob
** Tags added: rls-ee-incoming -- 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/1841794 Title: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f ubuntu-bug crash report for bug reported in LP: #1841680 On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 10:42:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-19 (554 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841794/+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 1841897] Re: Cursor missing from slider
Thank you for your bug report, could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues (confirmed and it does the same with Adwaita so not a theme issue) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1841897 Title: Cursor missing from slider Status in gnome-control-center package in Ubuntu: Confirmed Bug description: There is no cursor on the slider in gnome-control-center (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 09:59:11 2019 InstallationDate: Installed on 2014-07-15 (1870 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-03-24 (522 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1841897/+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 1841926] Re: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()
*** This bug is a duplicate of bug 1841794 *** https://bugs.launchpad.net/bugs/1841794 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1841794, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1841926/+attachment/5285611/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285613/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285618/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285619/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285620/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285622/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285623/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1841794 gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1841926 Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance() Status in gnome-shell package in Ubuntu: New Bug description: Reveal dock in intellihide mode, with 2 screens and the dock in between ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:13:31 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::~ObjectInstance() () at /usr/lib/libgjs.so.0 GIWrapperBase::finalize(JSFreeOp*, JSObject*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance() UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841926/+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 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
Strange, these two extensions('sensory-percept...@harlemsquirrel.github.io',
'temperature@xtranophilist', 'gnom...@panacier.gmail.com'
) I've already uninstalled from gnome-tweaks, for a long time.
If they are available and easy to install, I think there is some problem with
gnome shell extensions, it happens to many users that they can't start the
desktop with any extension that doesn't work well (I can fix it because I know
how to fix it, but many users, no).
The bug occurred only on one occasion, but I wanted to report it because I want
to help fix bugs, if there are any.
--
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/1841774
Title:
gnome-shell freezes and continuously logs "JS ERROR: TypeError: null
has no properties" in _addWindowEffect from vfunc_show (both in
closeDialog.js)
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
I was closing the dialog of the "software and updates" tools (I was
checking the repositories and ppa), but the entire desktop went into
freeze, no mouse movement, at the click no action, I pressed the keys
"ctrl + alt + f3 "and I went into a tty session, from there I recorded
the logs via:" journalctl -f> log ", and I restarted.
This is one part of the log, but it seems to repeat itself, I have
attached a file with a longer log.
-- Logs begin at Tue 2019-02-19 00:29:40 CET. --
ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no
properties
_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13
vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9
ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no
properties
_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13
vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.33.91-1ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
Uname: Linux 5.2.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 28 14:51:01 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-02-18 (190 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.33.91-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/1841774/+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 1840675] Re: Expose a button in the Network panel to open nm-connection-editor
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Wishlist -- 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/1840675 Title: Expose a button in the Network panel to open nm-connection-editor Status in gnome-control-center package in Ubuntu: New Bug description: Upstream reverted showing the desktop launcher of nm-connection-editor because it's confusing for the average user, its icon is outdated and does not follow the current GNOME icon design guidelines. https://gitlab.gnome.org/GNOME/network-manager-applet/issues/55 https://gitlab.gnome.org/GNOME/network-manager-applet/commit/a0c31ed5 Upstream follow-up bug: Remove runtime dependency on network-manager-applet (nm-connection-editor) https://gitlab.gnome.org/GNOME/gnome-control-center/issues/512 So in the meantime I suggest exposing a button in the Network panel (or else where it fits) to open nm-connection-editor in order not to lose the tool's functionally. The name of the button could be Advanced Network Configuration. Note: we are already doing the same thing for Region & Language settings and Printer settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1840675/+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 1841921] Re: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()
*** This bug is a duplicate of bug 1841794 *** https://bugs.launchpad.net/bugs/1841794 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1841794, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1841921/+attachment/5285596/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285598/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285603/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285604/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285605/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285607/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285608/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1841794 gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1841921 Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance() Status in gnome-shell package in Ubuntu: New Bug description: Crash with new Shell stack. Maybe related to showing the dock in intellihide mode, where the dock is between 2 monitors, triggering show/hide/show/hide fast flickering (not reproducible 100% of time, but at least, got it 3 times). ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 12:55:49 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::~ObjectInstance() () at /usr/lib/libgjs.so.0 GIWrapperBase::finalize(JSFreeOp*, JSObject*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance() UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841921/+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 1841412] Re: Build with NDEBUG again
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841412 Title: Build with NDEBUG again Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Bug description: [Impact] Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. This means that some asserts are enabled, and at least nouveau is affected. [Test case] chech the build log that -DNDEBUG is passed [Regression potential] none really, it just adds a build flag which should've been there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1841412/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
Hello Alkis, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1841915] [NEW] black screen, unresponsive, after logout from gnome
Public bug reported: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Status in gdm3 package in Ubuntu: New Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1685639] Re: network-manager-gnome must depend on dnsmasq for WiFi/Ethernet hotspots to work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1685639 Title: network-manager-gnome must depend on dnsmasq for WiFi/Ethernet hotspots to work Status in network-manager-applet package in Ubuntu: Confirmed Bug description: There is a button in network-manager-gnome GUI that starts a WiFi hotspot, but it does not work out of the box on Ubuntu GNOME 17.04 untill dnsmasq is installed manually. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-gnome 1.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 23 19:22:02 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-22 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev enx582c80139263 proto static metric 100 192.168.1.0/24 dev enx582c80139263 proto kernel scope link src 192.168.1.100 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enx582c80139263 ethernet connected /org/freedesktop/NetworkManager/Devices/4 Проводное соединение 2 543da71d-1383-469f-95b0-114ce014d787 /org/freedesktop/NetworkManager/ActiveConnection/7 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1685639/+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 1724977] Re: two mouse cursors visible at the same time on rotated screen
** Bug watch added: bugzilla.gnome.org/ #789675 https://bugzilla.gnome.org/show_bug.cgi?id=789675 ** Changed in: mutter Importance: Medium => Unknown ** Changed in: mutter Status: Fix Released => Unknown ** Changed in: mutter Remote watch: GNOME Bug Tracker #789675 => bugzilla.gnome.org/ #789675 -- 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/1724977 Title: two mouse cursors visible at the same time on rotated screen Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Confirmed Bug description: When my 2nd Asus (Ancor) display is in portrait mode and is set to be to the left of my centered landscape display in extended mode, moving the mouse to roughly the left 20% of my landscape display will show a mouse cursor on my landcape display AND portrait display at the same time. Oddly moving a window into this area only shows on the landscape display. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 13:43:30 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724977/+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 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
Sounds like bug 1724977, but we claim to have fixed that(?). also... 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 1841894 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: disco ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock Status in mutter package in Ubuntu: Incomplete Bug description: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+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 1836691] Re: Update to 1.49
Since this is a very specific project I guess I would be willing to accept the verification (especially that the SRU has been accepted by another SRU member), but I do have one formal thing I'd like clarification on. The bug mentions snapd-glib having an SRU exception, but I do not see one 'approved' in https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases . Who approved the SRU exception? Each exception needs to be approved by at least one SRU member and documented (along with the date) on the policy page IIRC. Could you answer those questions before we proceed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1836691 Title: Update to 1.49 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Fix Committed Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Disco: Fix Committed Status in snapd-glib source package in Eoan: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1836691/+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 1841897] [NEW] Cursor missing from slider
Public bug reported: There is no cursor on the slider in gnome-control-center (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 09:59:11 2019 InstallationDate: Installed on 2014-07-15 (1870 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-03-24 (522 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan rls-ee-incoming ** Attachment added: "2019-08-29_09-58.png" https://bugs.launchpad.net/bugs/1841897/+attachment/5285564/+files/2019-08-29_09-58.png -- 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/1841897 Title: Cursor missing from slider Status in gnome-control-center package in Ubuntu: New Bug description: There is no cursor on the slider in gnome-control-center (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 09:59:11 2019 InstallationDate: Installed on 2014-07-15 (1870 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-03-24 (522 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1841897/+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 1841894] [NEW] Wayland: Image of mouse cursor left on screen after unlock
Public bug reported: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description:Ubuntu 19.04 Release:19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Monitor layout showing fake cursor image" https://bugs.launchpad.net/bugs/1841894/+attachment/5285562/+files/CursorImage.jpg -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock Status in mutter package in Ubuntu: New Bug description: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+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 1841886] Re: Join Displays failed when using two external monitor of one Full HD and one Ultra HD
It doesn't look like https://gitlab.gnome.org/GNOME/mutter/issues/728. It is about the hardware limitation that DELL DOCK - WD19 130W only supports two external Full HD at the same time. However mutter doesn't know the hardware limitation. I guest mutter will try to set up external Ultra HD and external Full HD that is over the hardware limitation of DELL DOCK - WD19 130W so it failed. -- 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in mutter package in Ubuntu: New Bug description: [Summary] Join Displays failed when using two external monitor of one Full HD and one Ultra HD [Reproduce Steps] 1. Boot into the desktop environment with DELL DOCK - WD19 130W [1]. 2. Connect one Ultra HD (3840x2160) external monitor and one Full HD (1920x1080) external monitor. 3. Press Win+P to switch to Join Displays mode. [Results] Expected: All monitors including the internal monitor can display with Full HD (1920x1080). Actual: The Ultra HD monitor can not display. [Additional Information] 1. Using only Ultra HD (3840x2160) external monitor with internal Full HD (1920x1020) display works fine. 2. Executing the command like `xrandr --output eDP-1 --primary --preferred --output DP-1-1 --preferred --left-of eDP-1 --output DP-1-2 --above eDP-1 --mode 1920x1080 --rate 60` can work. (P.S. DP-1-2 is connected to Ultra HD.) [1] https://www.dellemc.com/resources/en-us/asset/data-sheets/products /electronics-accessories/dell_dock_wd19_130w_spec_sheet.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New -- 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/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 Status in gnome-shell-extension-dashtodock package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Some extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+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 1841886] Re: Join Displays failed when using two external monitor of one Full HD and one Ultra HD
Sounds like this?... https://gitlab.gnome.org/GNOME/mutter/issues/728 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/728 Importance: Unknown Status: Unknown ** No longer affects: mutter -- 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in mutter package in Ubuntu: New Bug description: [Summary] Join Displays failed when using two external monitor of one Full HD and one Ultra HD [Reproduce Steps] 1. Boot into the desktop environment with DELL DOCK - WD19 130W [1]. 2. Connect one Ultra HD (3840x2160) external monitor and one Full HD (1920x1080) external monitor. 3. Press Win+P to switch to Join Displays mode. [Results] Expected: All monitors including the internal monitor can display with Full HD (1920x1080). Actual: The Ultra HD monitor can not display. [Additional Information] 1. Using only Ultra HD (3840x2160) external monitor with internal Full HD (1920x1020) display works fine. 2. Executing the command like `xrandr --output eDP-1 --primary --preferred --output DP-1-1 --preferred --left-of eDP-1 --output DP-1-2 --above eDP-1 --mode 1920x1080 --rate 60` can work. (P.S. DP-1-2 is connected to Ultra HD.) [1] https://www.dellemc.com/resources/en-us/asset/data-sheets/products /electronics-accessories/dell_dock_wd19_130w_spec_sheet.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+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 1841886] Re: Join Displays failed when using two external monitor of one Full HD and one Ultra HD
Are you able to supply apport info? apport-collect 1841886 ** Tags added: bionic ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #728 https://gitlab.gnome.org/GNOME/mutter/issues/728 -- 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in mutter package in Ubuntu: New Bug description: [Summary] Join Displays failed when using two external monitor of one Full HD and one Ultra HD [Reproduce Steps] 1. Boot into the desktop environment with DELL DOCK - WD19 130W [1]. 2. Connect one Ultra HD (3840x2160) external monitor and one Full HD (1920x1080) external monitor. 3. Press Win+P to switch to Join Displays mode. [Results] Expected: All monitors including the internal monitor can display with Full HD (1920x1080). Actual: The Ultra HD monitor can not display. [Additional Information] 1. Using only Ultra HD (3840x2160) external monitor with internal Full HD (1920x1020) display works fine. 2. Executing the command like `xrandr --output eDP-1 --primary --preferred --output DP-1-1 --preferred --left-of eDP-1 --output DP-1-2 --above eDP-1 --mode 1920x1080 --rate 60` can work. (P.S. DP-1-2 is connected to Ultra HD.) [1] https://www.dellemc.com/resources/en-us/asset/data-sheets/products /electronics-accessories/dell_dock_wd19_130w_spec_sheet.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+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 1841886] [NEW] Join Displays failed when using two external monitor of one Full HD and one Ultra HD
Public bug reported: [Summary] Join Displays failed when using two external monitor of one Full HD and one Ultra HD [Reproduce Steps] 1. Boot into the desktop environment with DELL DOCK - WD19 130W [1]. 2. Connect one Ultra HD (3840x2160) external monitor and one Full HD (1920x1080) external monitor. 3. Press Win+P to switch to Join Displays mode. [Results] Expected: All monitors including the internal monitor can display with Full HD (1920x1080). Actual: The Ultra HD monitor can not display. [Additional Information] 1. Using only Ultra HD (3840x2160) external monitor with internal Full HD (1920x1020) display works fine. 2. Executing the command like `xrandr --output eDP-1 --primary --preferred --output DP-1-1 --preferred --left-of eDP-1 --output DP-1-2 --above eDP-1 --mode 1920x1080 --rate 60` can work. (P.S. DP-1-2 is connected to Ultra HD.) [1] https://www.dellemc.com/resources/en-us/asset/data-sheets/products /electronics-accessories/dell_dock_wd19_130w_spec_sheet.pdf ** Affects: oem-priority Importance: Undecided Status: New ** Affects: oem-priority/bionic Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1841034 somerville ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in mutter package in Ubuntu: New Bug description: [Summary] Join Displays failed when using two external monitor of one Full HD and one Ultra HD [Reproduce Steps] 1. Boot into the desktop environment with DELL DOCK - WD19 130W [1]. 2. Connect one Ultra HD (3840x2160) external monitor and one Full HD (1920x1080) external monitor. 3. Press Win+P to switch to Join Displays mode. [Results] Expected: All monitors including the internal monitor can display with Full HD (1920x1080). Actual: The Ultra HD monitor can not display. [Additional Information] 1. Using only Ultra HD (3840x2160) external monitor with internal Full HD (1920x1020) display works fine. 2. Executing the command like `xrandr --output eDP-1 --primary --preferred --output DP-1-1 --preferred --left-of eDP-1 --output DP-1-2 --above eDP-1 --mode 1920x1080 --rate 60` can work. (P.S. DP-1-2 is connected to Ultra HD.) [1] https://www.dellemc.com/resources/en-us/asset/data-sheets/products /electronics-accessories/dell_dock_wd19_130w_spec_sheet.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
Dash to Dock is currently broken as well. This branch https://github.com/3v1n0/dash-to-dock/tree/gnome-3-34 works, but the intelligent autohide brings down the entire gnome shell if enabled. GNOME Pomodoro currently works, but was compiled under 3.32 from the 3.32 branch. The package has not be in the repos since Cuttlefish. -- 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/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Some extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1835706/+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
