[Desktop-packages] [Bug 1822478] Re: [nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
** Tags added: x11-scaling ** Summary changed: - [nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. + [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418 package in Ubuntu: New Bug description: Recently upgraded to Disco beta. Running a 1080p screen at 100% scaling. uname -a : Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Graphics card : GeForce GT 710/PCIe/SSE2 Drivers version: Nvidia-Driver-418 Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct package to log it against) or an "Idiot User" issue. As I've upgraded this system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean install between upgrades. When I reboot, all on screen text is tiny. Icons are normal size but text is nearly unreadable. This also effects any text input boxes (i.e. user password) Text in "Show Applications" screen is also effected. *Workaroud* Only work around for the desktop is to go in to "Settings" then "Devices" then Adjust the scaling to 200%, hit Apply, then press "Revert Changes", this resets the scaling to normal. This does not fix the scaling in the "Show Applications" screen. Attached images in Scaling_Issues.zip : Image of text scaling after reboot : Scaling_Small.png Image after the "workaround" to show how it should look like: Scaling_Normal.png Image of "Show Applications" screen which is still effected : Applications_Small.png ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Sun Mar 31 16:00:21 2019 DisplayManager: gdm3 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.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-07-09 (264 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822513] Re: [regression] gnome-shell aspect ratio doesn't rotate with the rest of the screen
** Tags added: x11-scaling ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1822513 Title: [regression] gnome-shell aspect ratio doesn't rotate with the rest of the screen Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: I'm testing 19.04 on an Acer-One S1003. An interesting quirk of that tablet is that the default screen orientation is portrait (as can be seen in BIOS setup, grub etc.) Ubuntu 19.04 support screen rotation out of the box. But after a recent update, the landscape mode is broken. In landscape, only the left hand portion the screen displays an image. The right hand part is black. The part that's shown is about as wide as the screen would be in portrait orientation. Another quirk is that landscape screenshots (taken with printscreen) have a portrait size, with some garbage at the bottom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822513/+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 1815550] Re: RSS grows without limit, general slowness
** Tags added: performance ** Summary changed: - RSS grows without limit, general slowness + [nvidia] gnome-shell RSS grows without limit, general slowness -- 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/1815550 Title: [nvidia] gnome-shell RSS grows without limit, general slowness Status in gnome-shell package in Ubuntu: Confirmed Bug description: This *may* be an nvidia-specific problem, but the RSS of gnome-shell on my system grows without limit (over a couple of hours it's increased past 10G). At the same time, gnome-shell appears to become progressively less responsive. Restarting gnome-shell (via restart) drops shell RSS down to ~400MB and improves system responsiveness a bit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 4.20.0 Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 13:35:59 2019 DisplayManager: gdm3 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/1815550/+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 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Recently upgraded to Disco beta. Running a 1080p screen at 100% scaling. uname -a : Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Graphics card : GeForce GT 710/PCIe/SSE2 Drivers version: Nvidia-Driver-418 Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct package to log it against) or an "Idiot User" issue. As I've upgraded this system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean install between upgrades. When I reboot, all on screen text is tiny. Icons are normal size but text is nearly unreadable. This also effects any text input boxes (i.e. user password) Text in "Show Applications" screen is also effected. *Workaroud* Only work around for the desktop is to go in to "Settings" then "Devices" then Adjust the scaling to 200%, hit Apply, then press "Revert Changes", this resets the scaling to normal. This does not fix the scaling in the "Show Applications" screen. Attached images in Scaling_Issues.zip : Image of text scaling after reboot : Scaling_Small.png Image after the "workaround" to show how it should look like: Scaling_Normal.png Image of "Show Applications" screen which is still effected : Applications_Small.png ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Sun Mar 31 16:00:21 2019 DisplayManager: gdm3 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.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-07-09 (264 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Recently upgraded to Disco beta. Running a 1080p screen at 100% scaling. uname -a : Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Graphics card : GeForce GT 710/PCIe/SSE2 Drivers version: Nvidia-Driver-418 Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct package to log it against) or an "Idiot User" issue. As I've upgraded this system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean install between upgrades. When I reboot, all on screen text is tiny. Icons are normal size but text is nearly unreadable. This also effects any text input boxes (i.e. user password) Text in "Show Applications" screen is also effected. *Workaroud* Only work around for the desktop is to go in to "Settings" then "Devices" then Adjust the scaling to 200%, hit Apply, then press "Revert Changes", this resets the scaling to normal. This does not fix the scaling in the "Show Applications" screen. Attached images in Scaling_Issues.zip : Image of text scaling after reboot : Scaling_Small.png Image after the "workaround" to show how it should look like: Scaling_Normal.png Image of "Show Applications" screen which is still effected : Applications_Small.png ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Sun Mar 31 16:00:21 2019 DisplayManager: gdm3 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.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-07-09 (264 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1796251] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1017 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1017 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1017 Importance: Unknown Status: Unknown ** Changed in: gdk-pixbuf (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Tags added: fixed-in-3.32.1 fixed-upstream ** No longer affects: gdk-pixbuf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1796251 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() Status in GNOME Shell: Unknown Status in gdk-pixbuf package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1796251/+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 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
Note that I'm seeing this with modeset=1 (nvidia): - Shell UI has small text (and so, small panel and such…) - icons and application have normal size Going to g-c-c => displays scaling factor is at 100% (I never changed it before on that machine). Going to 200% -> Apply. The text is giant. Then, clicking "abandon configuration" on the modal dialog will reset the text size to an expected "normal" size (and g-c-c is showing a scaling factor of 100%). This works upon next reboot. -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Recently upgraded to Disco beta. Running a 1080p screen at 100% scaling. uname -a : Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Graphics card : GeForce GT 710/PCIe/SSE2 Drivers version: Nvidia-Driver-418 Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct package to log it against) or an "Idiot User" issue. As I've upgraded this system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean install between upgrades. When I reboot, all on screen text is tiny. Icons are normal size but text is nearly unreadable. This also effects any text input boxes (i.e. user password) Text in "Show Applications" screen is also effected. *Workaroud* Only work around for the desktop is to go in to "Settings" then "Devices" then Adjust the scaling to 200%, hit Apply, then press "Revert Changes", this resets the scaling to normal. This does not fix the scaling in the "Show Applications" screen. Attached images in Scaling_Issues.zip : Image of text scaling after reboot : Scaling_Small.png Image after the "workaround" to show how it should look like: Scaling_Normal.png Image of "Show Applications" screen which is still effected : Applications_Small.png ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Sun Mar 31 16:00:21 2019 DisplayManager: gdm3 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.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-07-09 (264 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
s/upon/until -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Recently upgraded to Disco beta. Running a 1080p screen at 100% scaling. uname -a : Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Graphics card : GeForce GT 710/PCIe/SSE2 Drivers version: Nvidia-Driver-418 Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct package to log it against) or an "Idiot User" issue. As I've upgraded this system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean install between upgrades. When I reboot, all on screen text is tiny. Icons are normal size but text is nearly unreadable. This also effects any text input boxes (i.e. user password) Text in "Show Applications" screen is also effected. *Workaroud* Only work around for the desktop is to go in to "Settings" then "Devices" then Adjust the scaling to 200%, hit Apply, then press "Revert Changes", this resets the scaling to normal. This does not fix the scaling in the "Show Applications" screen. Attached images in Scaling_Issues.zip : Image of text scaling after reboot : Scaling_Small.png Image after the "workaround" to show how it should look like: Scaling_Normal.png Image of "Show Applications" screen which is still effected : Applications_Small.png ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Sun Mar 31 16:00:21 2019 DisplayManager: gdm3 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.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-07-09 (264 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822746] Re: Xorg crashed with SIGSEGV
*** This bug is a duplicate of bug 1733292 *** https://bugs.launchpad.net/bugs/1733292 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 #1733292, 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/1822746/+attachment/5251956/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1822746/+attachment/5251959/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1822746/+attachment/5251968/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1822746/+attachment/5251970/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1822746/+attachment/5251971/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1822746/+attachment/5251972/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1822746/+attachment/5251973/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1733292 Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events ** 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 xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1822746 Title: Xorg crashed with SIGSEGV Status in xorg-server package in Ubuntu: New Bug description: todays updates installed then crash. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: xserver-xorg-core 2:1.20.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Mar 26 19:24:51 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-7-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-8-generic, x86_64: installed v4l2loopback, 0.12.1, 5.0.0-7-generic, x86_64: installed v4l2loopback, 0.12.1, 5.0.0-8-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:05a4] InstallationDate: Installed on 2014-08-13 (1692 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810) MachineType: Dell Inc. OptiPlex 9020 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=e2d4a833-d4fd-4295-95a5-57c52551e6ba ro splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x562d5f7e1340:movswl 0x8(%rdi),%ecx PC (0x562d5f7e1340) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%ecx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: () miPointerSetPosition () () () GetPointerEvents () Title: Xorg crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo dmi.bios.date: 10/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06X1TJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd10/24/2018:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9020 dmi.product.sku: 05A4 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-me
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-l10n in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in geogebra source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix Committed Status in javamail source package in Bionic: Fix Committed Status in javatools source package in Bionic: Fix Committed Status in jboss-classfilewriter source package in Bionic: Fix Committed Status in jboss-jdeparser2 source package in Bionic: Fix Committed Status in jboss-modules source package in Bionic: Fix Committed Status in jcommander source package in Bionic: Fix Committed Status in jersey1 source package in Bionic: Fix Committed Status in jftp source package in Bionic: Fix Committed Status in jhove source package in Bionic: Fix Committed Status in jmdns source package in Bionic: Fix Committed Status in jnr-posix source package in Bionic: Fix Committed Status in jruby source package in Bionic: Fix Committed Status in jruby-openssl source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in jts source package in Bionic: Fix Committed Status in junit4 source package in Bionic: Fix Committed Status in jxgrabkey source package in Bionic: Fix Committed Status in jython source package in Bionic: Fix Committed Status in libapache-poi-java source package in Bionic: Fix Committed Status in libbtm-java source package in Bionic: Fix Committed Stat
[Desktop-packages] [Bug 1733292] Re: Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events
** Tags added: disco -- 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/1733292 Title: Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events Status in xorg-server package in Ubuntu: Confirmed Bug description: occasional screen locks up, the session ends, reverts to display manager (lightdm?), have to log in again. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Nov 20 09:11:46 2017 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.0, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:05a4] InstallationDate: Installed on 2014-08-13 (1194 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810) MachineType: Dell Inc. OptiPlex 9020 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=e2d4a833-d4fd-4295-95a5-57c52551e6ba ro splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x56286fd4bad0:movswl 0x8(%rdi),%ecx PC (0x56286fd4bad0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%ecx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: () miPointerSetPosition () () () GetPointerEvents () Title: Xorg crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo dmi.bios.date: 05/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06X1TJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/23/2017:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9020 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.88-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 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Sep 12 12:13:51 2017 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1733292/+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 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
** Changed in: mutter (Ubuntu Cosmic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Disco) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu Cosmic) Status: Triaged => Invalid ** Changed in: gnome-shell (Ubuntu Disco) Status: Triaged => Invalid ** Tags added: fixed-in-3.32.1 -- 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/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Triaged Status in gnome-shell source package in Cosmic: Invalid Status in mutter source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Invalid Status in mutter source package in Disco: Triaged Bug description: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log-out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: 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 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Changed in: libreoffice-l10n (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: libreoffice (Ubuntu Cosmic) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: libreoffice-l10n (Ubuntu Cosmic) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-l10n in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in geogebra source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix Committed Status in javamail source package in Bionic: Fix Committed Status in javatools source package in Bionic: Fix Committed Status in jboss-classfilewriter source package in Bionic: Fix Committed Status in jboss-jdeparser2 source package in Bionic: Fix Committed Status in jboss-modules source package in Bionic: Fix Committed Status in jcommander source package in Bionic: Fix Committed Status in jersey1 source package in Bionic: Fix Committed Status in jftp source package in Bionic: Fix Committed Status in jhove source package in Bionic: Fix Committed Status in jmdns source package in Bionic: Fix Committed Status in jnr-posix source package in Bionic: Fix Committed Status in jruby source package in Bionic: Fix Committed Status in jruby-openssl source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in jts source package in Bionic: Fix Committed Status in junit4 source package in Bionic: Fix Committed Status in jxgrabkey source package in Bionic: Fix
[Desktop-packages] [Bug 1796251] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from
** Changed in: gnome-shell Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1796251 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() Status in GNOME Shell: Fix Released Status in gdk-pixbuf package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1796251/+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 1817924] Re: (In Xorg sessions only) apps launched from gnome shell do not get input focus
** Changed in: mutter (Ubuntu Disco) Status: In Progress => Triaged -- 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/1817924 Title: (In Xorg sessions only) apps launched from gnome shell do not get input focus Status in Mutter: Fix Released Status in mutter package in Ubuntu: Triaged Status in mutter source package in Disco: Triaged Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1817924/+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 1822753] Re: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref
The first issues it that gedit should use gvfs to store file metadata. Since the port of gedit to meson this feature has been lost. I've proposed a fix upstream here: https://gitlab.gnome.org/GNOME/gedit/merge_requests/32 ** Changed in: gedit (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gedit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822753 Title: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref Status in gedit package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1822753/+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 1822753] [NEW] /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gedit (Ubuntu) Importance: Undecided Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Tags: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822753 Title: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref Status in gedit package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1822753/+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 1822754] [NEW] Chrome and other programs not resizing on HiDPI and Non-Hidpi setup
Public bug reported: To try the new support for EGLStreams and Wayland I have directly tried some programs to see how this performs. Unfortunately there are multiple problems: Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes while scrolling on normal pages). Also the automatic resizing when a program is moved from one display to another only works with system applications such as settings, terminal etc. The programs then are still scaled 2x on the Non-HIDPI screen. I am running the latest NVIDIA Drivers with 418.56. Is there a fix for this behaviour? Best Nicolas ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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-3ubuntu1) ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 11:25:53 2019 DistUpgraded: 2019-03-31 23:11:06,205 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-8-generic, x86_64: installed rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070 Ti] [1462:c303] InstallationDate: Installed on 2019-01-04 (87 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7976 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=UUID=367ba2c7-63e9-46a2-9d19-aa86d3dcc21d ro quiet splash nvidia-drm.modeset=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-03-31 (1 days ago) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7976 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 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 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco performance possible-manual-nvidia-install ubuntu wayland-session ** Package changed: xorg (Ubuntu) => wayland (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1822754 Title: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup Status in wayland package in Ubuntu: New Bug description: To try the new support for EGLStreams and Wayland I have directly tried some programs to see how this performs. Unfortunately there are multiple problems: Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes while scrolling on normal pages). Also the automatic resizing when a program is moved from one display to another only works with system applications such as settings, terminal etc. The programs then are still scaled 2x on the Non-HIDPI screen. I am running the latest NVIDIA Drivers with 418.56. Is there a fix for this behaviour? Best Nicolas ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature:
[Desktop-packages] [Bug 1822754] Re: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup
Could you please try installing the previous mutter version by downloading the .deb files from here: https://launchpad.net/ubuntu/+source/mutter/3.32.0-1/+build/16489975 and then install them all. ** Tags added: nvidia ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: hidpi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1822754 Title: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup Status in mutter package in Ubuntu: Incomplete Bug description: To try the new support for EGLStreams and Wayland I have directly tried some programs to see how this performs. Unfortunately there are multiple problems: Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes while scrolling on normal pages). Also the automatic resizing when a program is moved from one display to another only works with system applications such as settings, terminal etc. The programs then are still scaled 2x on the Non-HIDPI screen. I am running the latest NVIDIA Drivers with 418.56. Is there a fix for this behaviour? Best Nicolas ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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-3ubuntu1) ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 11:25:53 2019 DistUpgraded: 2019-03-31 23:11:06,205 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-8-generic, x86_64: installed rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070 Ti] [1462:c303] InstallationDate: Installed on 2019-01-04 (87 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7976 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=UUID=367ba2c7-63e9-46a2-9d19-aa86d3dcc21d ro quiet splash nvidia-drm.modeset=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-03-31 (1 days ago) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7976 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 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/ubuntu/+source/mutter/+bug/1822754/+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 1822754] Re: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup
Also I wonder if this is related: [17.738] (II) NVIDIA(0): Validated MetaModes: [17.738] (II) NVIDIA(0): "NULL" [17.738] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480 [17.770] (II) NVIDIA(0): Setting mode "NULL" -- 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/1822754 Title: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup Status in mutter package in Ubuntu: Incomplete Bug description: To try the new support for EGLStreams and Wayland I have directly tried some programs to see how this performs. Unfortunately there are multiple problems: Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes while scrolling on normal pages). Also the automatic resizing when a program is moved from one display to another only works with system applications such as settings, terminal etc. The programs then are still scaled 2x on the Non-HIDPI screen. I am running the latest NVIDIA Drivers with 418.56. Is there a fix for this behaviour? Best Nicolas ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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-3ubuntu1) ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 11:25:53 2019 DistUpgraded: 2019-03-31 23:11:06,205 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-8-generic, x86_64: installed rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070 Ti] [1462:c303] InstallationDate: Installed on 2019-01-04 (87 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7976 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=UUID=367ba2c7-63e9-46a2-9d19-aa86d3dcc21d ro quiet splash nvidia-drm.modeset=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-03-31 (1 days ago) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7976 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 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/ubuntu/+source/mutter/+bug/1822754/+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 1822754] Re: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup
While still experiencing the bug please run: glxinfo > glxinfo.txt in a terminal and then send us the file 'glxinfo.txt'. -- 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/1822754 Title: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup Status in mutter package in Ubuntu: Incomplete Bug description: To try the new support for EGLStreams and Wayland I have directly tried some programs to see how this performs. Unfortunately there are multiple problems: Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes while scrolling on normal pages). Also the automatic resizing when a program is moved from one display to another only works with system applications such as settings, terminal etc. The programs then are still scaled 2x on the Non-HIDPI screen. I am running the latest NVIDIA Drivers with 418.56. Is there a fix for this behaviour? Best Nicolas ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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-3ubuntu1) ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 11:25:53 2019 DistUpgraded: 2019-03-31 23:11:06,205 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-8-generic, x86_64: installed rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070 Ti] [1462:c303] InstallationDate: Installed on 2019-01-04 (87 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7976 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=UUID=367ba2c7-63e9-46a2-9d19-aa86d3dcc21d ro quiet splash nvidia-drm.modeset=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-03-31 (1 days ago) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7976 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 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/ubuntu/+source/mutter/+bug/1822754/+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 1822349] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1822753 *** https://bugs.launchpad.net/bugs/1822753 ** This bug is no longer a duplicate of private bug 1821404 ** This bug has been marked a duplicate of bug 1822753 /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822349 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: Gedit sometimes takes some time before opening and sometimes forcefully shuts down.Sometimes it works perfectly,but then also it asks that gedit has stopped working and to restart it. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 21:38:00 2019 ExecutablePath: /usr/bin/gedit ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_IN SegvAnalysis: Segfault happened at: 0x7f8a52b0067a : mov(%rax),%esi PC (0x7f8a52b0067a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: Upgraded to disco on 2019-03-17 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1822349/+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 1821453] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1822753 *** https://bugs.launchpad.net/bugs/1822753 ** This bug is no longer a duplicate of private bug 1821404 ** This bug has been marked a duplicate of bug 1822753 /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1821453 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: None ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 19:27:52 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-03-23 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190315) ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff67c30967a : mov(%rax),%esi PC (0x7ff67c30967a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1821453/+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 1821946] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1822753 *** https://bugs.launchpad.net/bugs/1822753 ** This bug is no longer a duplicate of private bug 1821404 ** This bug has been marked a duplicate of bug 1822753 /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1821946 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: No significant information about the bug ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 27 16:46:53 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-26 (28 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7f41e7e1367a : mov(%rax),%esi PC (0x7f41e7e1367a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1821946/+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 1821522] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1822753 *** https://bugs.launchpad.net/bugs/1822753 ** This bug is no longer a duplicate of private bug 1821404 ** This bug has been marked a duplicate of bug 1822753 /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1821522 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: Was using gedit to examine multiple files. When completed close with wondow "X" and let my system. When returning found the crash alert. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 08:43:38 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-06 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f25840ba67a : mov(%rax),%esi PC (0x7f25840ba67a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () at /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () at /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so () at /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () at /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1821522/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This bug was fixed in the package linux - 4.15.0-47.50
---
linux (4.15.0-47.50) bionic; urgency=medium
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
adjustments are in progress
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
* BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
* squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
* CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* Bionic update: upstream stable patchset 2019-02-08 (LP: #1815234)
- fork: unconditionally clear stack on fork
- spi: spi-s3c64xx: Fix system resume support
- Input: elan_i2c - add ACPI ID for lenovo ideapad 330
- Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
- Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
- kvm, mm: account shadow page tables to kmemcg
- delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
- tracing: Fix double free of event_trigger_data
- tracing: Fix possible double free in event_enable_trigger_func()
- kthread, tracing: Don't expose half-written comm when creating kthreads
- tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure
- tracing: Quiet gcc warning about maybe unused link variab
[Desktop-packages] [Bug 1822768] [NEW] libgtk window resize problem
Public bug reported: An app using libgtk-3 as GUI-lib shows strange behaviour since on ubuntu 18.04 an later. The problem is, that a not resizeable window not sets its correct size, when it shows up a second and all further times - but the first time, the size is correct. In that window a gtk element is inserted while showing up, so the size have to be recalculated. This stange behaviour is only found on Ubuntu 18.04 and later (libgtk-3-0 >> 3.22.30-1ubuntu2 ONLY on ubuntu - not kubuntu). On Debian systems (stable and testing) and Kubuntu systems of the same version all things are all right. A short list, which versions have failures (os and libgtk-3-0 version) : debian stretch with 3.22.11 is OK debian buster with 3.24.5 is OK ubuntu 17.10with 3.22.25-0ubuntu0.1 is OK ubuntu 18.04 (also LTS version)with 3.22.30-1ubuntu2 failure ubuntu 18.10with 3.24.4-0ubuntu1 failure A screenshot of the correct first show of the window an the second on is attached. A minimal example would also be attached in a replay to this report. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot of correct window size (left) and the faulty on (right)" https://bugs.launchpad.net/bugs/1822768/+attachment/5252034/+files/screenshot_gtk_window_resize_problem.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1822768 Title: libgtk window resize problem Status in gtk+3.0 package in Ubuntu: New Bug description: An app using libgtk-3 as GUI-lib shows strange behaviour since on ubuntu 18.04 an later. The problem is, that a not resizeable window not sets its correct size, when it shows up a second and all further times - but the first time, the size is correct. In that window a gtk element is inserted while showing up, so the size have to be recalculated. This stange behaviour is only found on Ubuntu 18.04 and later (libgtk-3-0 >> 3.22.30-1ubuntu2 ONLY on ubuntu - not kubuntu). On Debian systems (stable and testing) and Kubuntu systems of the same version all things are all right. A short list, which versions have failures (os and libgtk-3-0 version) : debian stretch with 3.22.11 is OK debian buster with 3.24.5 is OK ubuntu 17.10with 3.22.25-0ubuntu0.1 is OK ubuntu 18.04 (also LTS version)with 3.22.30-1ubuntu2 failure ubuntu 18.10with 3.24.4-0ubuntu1 failure A screenshot of the correct first show of the window an the second on is attached. A minimal example would also be attached in a replay to this report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822768/+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 1822771] [NEW] The poweroff menu is not working in Disco installation session
Public bug reported: Steps: 1. Create a Live USB with Disco daily image (20190331) 2. Boot with the Live USB, it should take you to the installation screen directly 3. Click on the upper right icon sets to expand the menu 4. Click on the power icon Expected result: * A menu should pop-up and asking user what to do (reboot / poweroff) Actual result: * Nothing happens gnome-shell 3.32.0-1ubuntu1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: disco ** Tags added: disco -- 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/1822771 Title: The poweroff menu is not working in Disco installation session Status in gnome-shell package in Ubuntu: New Bug description: Steps: 1. Create a Live USB with Disco daily image (20190331) 2. Boot with the Live USB, it should take you to the installation screen directly 3. Click on the upper right icon sets to expand the menu 4. Click on the power icon Expected result: * A menu should pop-up and asking user what to do (reboot / poweroff) Actual result: * Nothing happens gnome-shell 3.32.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822771/+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 1822771] Re: The poweroff menu is not working in Disco installation session
Tested on a Dell Inspiron 7737. ** Tags added: amd64 iso-testing -- 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/1822771 Title: The poweroff menu is not working in Disco installation session Status in gnome-shell package in Ubuntu: New Bug description: Steps: 1. Create a Live USB with Disco daily image (20190331) 2. Boot with the Live USB, it should take you to the installation screen directly 3. Click on the upper right icon sets to expand the menu 4. Click on the power icon Expected result: * A menu should pop-up and asking user what to do (reboot / poweroff) Actual result: * Nothing happens (it works in the Live session after clicking on the Try Ubuntu button) gnome-shell 3.32.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822771/+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 1822771] Re: The poweroff menu is not working in Disco installation session
** Description changed: Steps: - 1. Create a Live USB with Disco daily image (20190331) - 2. Boot with the Live USB, it should take you to the installation screen directly - 3. Click on the upper right icon sets to expand the menu - 4. Click on the power icon + 1. Create a Live USB with Disco daily image (20190331) + 2. Boot with the Live USB, it should take you to the installation screen directly + 3. Click on the upper right icon sets to expand the menu + 4. Click on the power icon Expected result: - * A menu should pop-up and asking user what to do (reboot / poweroff) + * A menu should pop-up and asking user what to do (reboot / poweroff) Actual result: - * Nothing happens + * Nothing happens (it works in the Live session after clicking on the Try Ubuntu) gnome-shell 3.32.0-1ubuntu1 ** Description changed: Steps: 1. Create a Live USB with Disco daily image (20190331) 2. Boot with the Live USB, it should take you to the installation screen directly 3. Click on the upper right icon sets to expand the menu 4. Click on the power icon Expected result: * A menu should pop-up and asking user what to do (reboot / poweroff) Actual result: - * Nothing happens (it works in the Live session after clicking on the Try Ubuntu) + * Nothing happens (it works in the Live session after clicking on the Try Ubuntu button) gnome-shell 3.32.0-1ubuntu1 -- 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/1822771 Title: The poweroff menu is not working in Disco installation session Status in gnome-shell package in Ubuntu: New Bug description: Steps: 1. Create a Live USB with Disco daily image (20190331) 2. Boot with the Live USB, it should take you to the installation screen directly 3. Click on the upper right icon sets to expand the menu 4. Click on the power icon Expected result: * A menu should pop-up and asking user what to do (reboot / poweroff) Actual result: * Nothing happens (it works in the Live session after clicking on the Try Ubuntu button) gnome-shell 3.32.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822771/+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 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial
I'm back with a workaround (i know, it is not elegant) I copied the libstdc++ library from IBM toolchain (see my first post to find the url) to /usr/lib/powerpc64le-linux-gnu and made the symlink. Now I have in /usr/lib/powerpc64le-linux-gnu : libstdc++.so.6.0.25 and libstdc++.so.6 -> libstdc++.so.6.0.25 (The symlink) Firefox 66.0.2+build1-0ubuntu0.16.04.1 (update version) works fine. lsb_releas -a Distributor ID: Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 Codename: xenial uname -a Linux testubu16 4.4.0-143-generic #169-Ubuntu SMP Thu Feb 7 07:56:40 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux -- 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/1819013 Title: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial Status in firefox package in Ubuntu: Confirmed Bug description: $ firefox XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so) Couldn't load XPCOM. $ ldd /usr/lib/firefox/libxul.so | head -1 /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 65.0.1+build2-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic ppc64le AddonCompatCheckDisabled: False AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 7 10:00 seq crw-rw 1 root audio 116, 33 Mar 7 10:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BuildID: 20190215002040 Channel: Unavailable Date: Thu Mar 7 10:02:49 2019 ForcedLayersAccel: False InstallationDate: Installed on 2018-01-11 (419 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el (20170801) IpRoute: default via 10.128.60.1 dev enP2p1s0f0 10.128.60.0/25 dev enP2p1s0f0 proto kernel scope link src 10.128.60.99 NoProfiles: True PciMultimedia: ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239 ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition379411841110016 -2 ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu SMP Wed Jul 18 08:50:43 UTC 2018 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 16 cpu_coreson: Number of cores online = 16 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1819013/+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 1822773] [NEW] Volume resets to 0 on startup
Public bug reported: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. Ubuntu 18.10 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1822773 Title: Volume resets to 0 on startup Status in gnome-settings-daemon package in Ubuntu: New Bug description: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1822773/+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 1822775] [NEW] Different input sources per window not work
Public bug reported: Ubuntu 19.04 The option to apply different input source for each window doesn't work (it automatically reset itself) However, I manually change org.gnome.desktop.input-sources.per-window and it works. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1822775 Title: Different input sources per window not work Status in ibus package in Ubuntu: New Bug description: Ubuntu 19.04 The option to apply different input source for each window doesn't work (it automatically reset itself) However, I manually change org.gnome.desktop.input-sources.per-window and it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1822775/+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 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
Drew Walton (drewwalton19216801), Thanks! it works. Currently I run this command on startup using systemd. Is there a simpler way? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1822072] Re: User selector doesn't have focus from login screen after screen turned off
This bug is being marked as notfixing for the Disco release. This doesnt mean it won't get fixed, but it won't block release. ** Tags removed: rls-dd-incoming ** Tags added: rls-dd-notfixing -- 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/1822072 Title: User selector doesn't have focus from login screen after screen turned off Status in gnome-shell package in Ubuntu: Confirmed Bug description: In gdm usually the user name is pre-selected. This means that you can just hit enter and then put your password in. In Disco this is the case on boot up. If you wait for the screensaver to kick in (i.e. boot and do nothing for 5 mins) then when the screen comes back again the username is not selected. Steps To Reproduce 1. Boot Disco 2. Once you get to the login screen, notice that your username is selected. 3. Do nothing, touch nothing. Wait for the screensaver to kick in and blank the screens. 4. Wiggle the mouse, dismiss the clock screen and you will be back at the login screen 5. Notice that you user is no longer selected and in order to log in you have to move the mouse and click on the user name What should happen The username should be pre-selected so that I can log in without having to use the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822072/+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 1822072] Re: User selector doesn't have focus from login screen after screen turned off
Setting to low, it's not an action users are going to do often and the workaround is easy. Would still be nice to upstream/get fixed though ** Changed in: gnome-shell (Ubuntu) Importance: Medium => 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/1822072 Title: User selector doesn't have focus from login screen after screen turned off Status in gnome-shell package in Ubuntu: Confirmed Bug description: In gdm usually the user name is pre-selected. This means that you can just hit enter and then put your password in. In Disco this is the case on boot up. If you wait for the screensaver to kick in (i.e. boot and do nothing for 5 mins) then when the screen comes back again the username is not selected. Steps To Reproduce 1. Boot Disco 2. Once you get to the login screen, notice that your username is selected. 3. Do nothing, touch nothing. Wait for the screensaver to kick in and blank the screens. 4. Wiggle the mouse, dismiss the clock screen and you will be back at the login screen 5. Notice that you user is no longer selected and in order to log in you have to move the mouse and click on the user name What should happen The username should be pre-selected so that I can log in without having to use the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822072/+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 1821901] Re: Location services option should be off by default
** Changed in: gnome-initial-setup (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Also affects: gnome-initial-setup (Ubuntu Disco) Importance: Undecided Assignee: Sebastien Bacher (seb128) Status: New ** Tags removed: rls-dd-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1821901 Title: Location services option should be off by default Status in gnome-initial-setup package in Ubuntu: New Status in gnome-initial-setup source package in Disco: New Bug description: During first run of g-i-s in Disco the Privacy screen has an option for enabling/disabling Location Services. From review with the legal team, this should be off by default but it is currently on by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1821901/+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 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
** Also affects: mutter (Ubuntu Disco) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged ** Also affects: gnome-shell (Ubuntu Disco) Importance: High Status: Triaged ** Also affects: nvidia-graphics-drivers-418 (Ubuntu Disco) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Tags removed: rls-dd-incoming -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in gnome-shell source package in Disco: Triaged Status in mutter source package in Disco: Triaged Status in nvidia-graphics-drivers-418 source package in Disco: Confirmed Bug description: Recently upgraded to Disco beta. Running a 1080p screen at 100% scaling. uname -a : Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Graphics card : GeForce GT 710/PCIe/SSE2 Drivers version: Nvidia-Driver-418 Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct package to log it against) or an "Idiot User" issue. As I've upgraded this system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean install between upgrades. When I reboot, all on screen text is tiny. Icons are normal size but text is nearly unreadable. This also effects any text input boxes (i.e. user password) Text in "Show Applications" screen is also effected. *Workaroud* Only work around for the desktop is to go in to "Settings" then "Devices" then Adjust the scaling to 200%, hit Apply, then press "Revert Changes", this resets the scaling to normal. This does not fix the scaling in the "Show Applications" screen. Attached images in Scaling_Issues.zip : Image of text scaling after reboot : Scaling_Small.png Image after the "workaround" to show how it should look like: Scaling_Normal.png Image of "Show Applications" screen which is still effected : Applications_Small.png ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Sun Mar 31 16:00:21 2019 DisplayManager: gdm3 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.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-07-09 (264 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1821895] Re: Gnome Shell crashes after resume on Disco
This bug is being marked as notfixing for the release. This doesnt mean it wont get fixed, but that we won't block release on it. ** Tags added: wayland ** Tags removed: rls-dd-incoming ** Tags added: rls-dd-notfixing -- 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/1821895 Title: Gnome Shell crashes after resume on Disco Status in gnome-shell package in Ubuntu: Incomplete Bug description: System - XPS13 9370 To the best of my knowledge, this was working fine last week. I updated the system via Apt, the system fails to resume after being suspended (via lid close). There is a blank screen for a few seconds, followed by the cursor appearing (still blank background) and then gnome crashes and comes back to the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821895/+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 1815550] Re: [nvidia] gnome-shell RSS grows without limit, general slowness
** Also affects: gnome-shell (Ubuntu Disco) Importance: Critical Status: Confirmed ** Changed in: gnome-shell (Ubuntu Disco) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Tags removed: rls-dd-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/1815550 Title: [nvidia] gnome-shell RSS grows without limit, general slowness Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Disco: Confirmed Bug description: This *may* be an nvidia-specific problem, but the RSS of gnome-shell on my system grows without limit (over a couple of hours it's increased past 10G). At the same time, gnome-shell appears to become progressively less responsive. Restarting gnome-shell (via restart) drops shell RSS down to ~400MB and improves system responsiveness a bit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 4.20.0 Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 13:35:59 2019 DisplayManager: gdm3 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/1815550/+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 1821019] Re: gnome-terminal does not gain focus upon launch via clicking icon
*** This bug is a duplicate of bug 1817924 *** https://bugs.launchpad.net/bugs/1817924 ** This bug has been marked a duplicate of bug 1817924 (In Xorg sessions only) apps launched from gnome shell do not get input focus ** Tags removed: rls-dd-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1821019 Title: gnome-terminal does not gain focus upon launch via clicking icon Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Ubuntu 19.04, 64 bit machine, nvidia graphics drivers Upon first and subsequent launches of gnome-terminal via clicking the icon, the window shows but does not immediately gain focus to start typing in commands. Using Ctrl+alt+T launches the terminal the way I expect, with immediate focus to start typing commands. I expect it to immediately gain focus to type commands upon launch each and every time using both methods. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 10:40:18 2019 InstallationDate: Installed on 2018-03-02 (382 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1821019/+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 1821695] Re: No typing focus on terminal opening
*** This bug is a duplicate of bug 1817924 *** https://bugs.launchpad.net/bugs/1817924 ** This bug is no longer a duplicate of bug 1821019 gnome-terminal does not gain focus upon launch via clicking icon ** This bug has been marked a duplicate of bug 1817924 (In Xorg sessions only) apps launched from gnome shell do not get input focus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1821695 Title: No typing focus on terminal opening Status in gnome-terminal package in Ubuntu: New Bug description: Normally when the terminal opens I can start typing straight away. Now I have to click anywhere on the terminal to bring focus to begin typing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 08:11:45 2019 InstallationDate: Installed on 2019-03-21 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190318) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1821695/+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 1821933] Automatically added comment
Added to Trello: https://trello.com/c/zteRvbzR/300-bug1821933-touch- input-is-offset-with-two-screens-even-appearing-on-the-wrong-screen ** Tags removed: desktop-trello-import -- 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/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+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 1821895] Re: Gnome Shell crashes after resume on Disco
This _seems_ to have resolved itself, I'm not sure if it was an update but I've not had it so far this week. -- 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/1821895 Title: Gnome Shell crashes after resume on Disco Status in gnome-shell package in Ubuntu: Incomplete Bug description: System - XPS13 9370 To the best of my knowledge, this was working fine last week. I updated the system via Apt, the system fails to resume after being suspended (via lid close). There is a blank screen for a few seconds, followed by the cursor appearing (still blank background) and then gnome crashes and comes back to the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821895/+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 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
This bug is being marked notfixing. That doesn't mean it wont get fixed, but that we won't block release on it. ** Tags removed: rls-dd-incoming ** Tags added: releasenotes rls-dd-notfixing ** Tags removed: releasenotes rls-dd-notfixing ** Tags added: desktop-trello-import rls-dd-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/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+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 1821895] Re: Gnome Shell crashes after resume on Disco
https://gitlab.gnome.org/GNOME/mutter/issues/509 Pending the crash report requested in #3, it's likely to be that I think. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #509 https://gitlab.gnome.org/GNOME/mutter/issues/509 -- 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/1821895 Title: Gnome Shell crashes after resume on Disco Status in gnome-shell package in Ubuntu: Incomplete Bug description: System - XPS13 9370 To the best of my knowledge, this was working fine last week. I updated the system via Apt, the system fails to resume after being suspended (via lid close). There is a blank screen for a few seconds, followed by the cursor appearing (still blank background) and then gnome crashes and comes back to the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821895/+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 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty
Hi guys Ubuntu Software continues to crash, as can be seen in the appendix. What should we do? Wait for updates or a downgrade done by you? Thank You ** Attachment added: "Captura de tela de 2019-04-02 10-43-50.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1817223/+attachment/5252069/+files/Captura%20de%20tela%20de%202019-04-02%2010-43-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1817223 Title: [disco-proposed] The list of applications in Ubuntu Software is empty Status in gnome-software package in Ubuntu: Triaged Status in libxmlb package in Ubuntu: Triaged Status in gnome-software source package in Disco: Won't Fix Status in libxmlb source package in Disco: Won't Fix Bug description: Hi The COMPLETE LIST of applications in Ubuntu Software is not showing up See attached image Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.31.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 19:11:23 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.31.2-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1817223/+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 1821264] Re: gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults
Any updates on this bug? What is needed from the customer or Dell to isolate this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1821264 Title: gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults Status in gnome-software package in Ubuntu: Incomplete Bug description: installing Dell Oem. Running update/upgrade sudo -s sudo apt-get update && sudo apt-get upgrade -y Then running gnome-software results in the GUI loading but after 10 seconds it crashes and you see a segfault. I tried information in +Bug/1798236 but U16 does not have a later version of gnome-software. I also saw a bug similar that mentioned we need packagekit 1.12 but U16 doesn't bundle that only U19 does. I tried download a package for testing purposes but it does not resolve the issue. I saw another case within our Dell database that suggests appstream might cause the crash so I removed appstream and did and update/upgrade again. It stopped the crash initially but not on reboot. I also added the gnome3 repository in hopes I could get the updates that way and that did not help either. It is unclear what is needed to resolve this issue. Please let me know what logs you need me to provide to look into this further. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.11 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 21 19:11:27 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-rebase-20170712-0 InstallationDate: Installed on 2019-03-04 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170712-02:34 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+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 1821264] Re: gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults
** Changed in: gnome-software (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1821264 Title: gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults Status in gnome-software package in Ubuntu: New Bug description: installing Dell Oem. Running update/upgrade sudo -s sudo apt-get update && sudo apt-get upgrade -y Then running gnome-software results in the GUI loading but after 10 seconds it crashes and you see a segfault. I tried information in +Bug/1798236 but U16 does not have a later version of gnome-software. I also saw a bug similar that mentioned we need packagekit 1.12 but U16 doesn't bundle that only U19 does. I tried download a package for testing purposes but it does not resolve the issue. I saw another case within our Dell database that suggests appstream might cause the crash so I removed appstream and did and update/upgrade again. It stopped the crash initially but not on reboot. I also added the gnome3 repository in hopes I could get the updates that way and that did not help either. It is unclear what is needed to resolve this issue. Please let me know what logs you need me to provide to look into this further. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.11 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 21 19:11:27 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-rebase-20170712-0 InstallationDate: Installed on 2019-03-04 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170712-02:34 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+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 1791405] Re: bluetooth always in discoverable mode (security issue)
That has been fixed in bluez upstream but there has been no new version since ** Package changed: gnome-bluetooth (Ubuntu) => bluez (Ubuntu) ** Changed in: bluez (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1791405 Title: bluetooth always in discoverable mode (security issue) Status in bluez package in Ubuntu: Fix Committed Status in gnome-bluetooth package in Fedora: Confirmed Bug description: Excerpt from a similar report (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) : Opening the Bluetooth settings will make the device discoverable again, but does not make the device undiscoverable after the settings are closed (this is not intended behavior; devices should only be discoverable when the bluetooth settings UI is open). There seem to be a merge request : https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1 Could you please merge it asap, it should be treated as a security issue IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
iso april 2 2019 tested .. adding xorg.0.log & xorg.0.log.old files from first boot into fresh install .. There was a 1 to 2 second flicker in lightdm appearing then blanking and then reappearing on first boot .. have not yet rebooted into this from grub as installed by sda1 .. wanted to save the above log files first. files are prefixed with "zl10-" ** Attachment added: "zl10-xorg.0.log first boot" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252072/+files/zl10-Xorg.0.log -- 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/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/lightdm/+bug/1821609/+subscriptions -- Mailing lis
[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
the " surprise log file " not expected on a first boot .. with normal xorg startup should not exist .. ** Attachment added: "zl10-xorg.0.log.old -- first boot (inital xorg-server start which flickered lightdm?)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252073/+files/zl10-Xorg.0.log.old -- 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/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/lightdm/+bug/1821609/+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/L
[Desktop-packages] [Bug 1821435] Re: nautilus crashed with SIGABRT in g_assertion_message()
Thank you for your bug report, I've reported it upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/970 (the error tracker report https://errors.ubuntu.com/problem/e31ebe2117daadf5ea0a969148735d423e102293 seems to be the same issue) ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #970 https://gitlab.gnome.org/GNOME/nautilus/issues/970 ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/970 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1821435 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Copied a file from a server to ~/Documents and used the Star function. Got this crash two times with different files. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 07:53:09 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-11-24 (118 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124) ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 nautilus_window_slot_get_location () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1821435/+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 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)
try to "sudo apt-get install libsane1/bionic libsane-common/bionic sane- utils/bionic" to go back to the ubuntu versions of those binaries -- 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/1821809 Title: gnome-control-center won't install: Depends: colord (>= 0.1.30) Status in gnome-control-center package in Ubuntu: Invalid Bug description: This bug looks similar to https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/1762256. I noticed Settings has gone missing from my ubuntu 18.04. When I click on the spanner icon under the power icon in the top right nothing appears to happen. Attempting to install it fails with: $ sudo apt install gnome-control-center [sudo] password for lucas: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. gnome-control-center : Depends: colord (>= 0.1.30) E: Unable to correct problems, you have held broken packages. This may have come about as a side-effect of trying to install simple- scan. I raised a question about that at https://askubuntu.com/q/1108407/103266 but it never got fixed. I couldn't resolve the error "Unable to correct problems, you have held broken packages". Any suggestions welcome, please. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center (not installed) ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 21:15:46 2019 InstallationDate: Installed on 2017-09-03 (569 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
okay after rebooting via grub installed by sda1 .. as before .. red flash (no plymouth) lightdm briefly displays login screen .. then underline cursor then blank screen. attached is zl10-boot2-xorg.0.log xorg.0.log.old is now the already uploaded zl10-xorg.0.log above a crashing time is revealed in the log file .. ** Attachment added: "zl10-boot2-xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252075/+files/zl10-boot2-Xorg.0.log -- 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/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/lightdm/+bug/1821609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-p
[Desktop-packages] [Bug 1821435] Re: nautilus crashed with SIGABRT in g_assertion_message()
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1821435 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Copied a file from a server to ~/Documents and used the Star function. Got this crash two times with different files. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 07:53:09 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-11-24 (118 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124) ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 nautilus_window_slot_get_location () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1821435/+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 1822072] Re: User selector doesn't have focus from login screen after screen turned off
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1132 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1132 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1132 Importance: Unknown Status: Unknown -- 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/1822072 Title: User selector doesn't have focus from login screen after screen turned off Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: In gdm usually the user name is pre-selected. This means that you can just hit enter and then put your password in. In Disco this is the case on boot up. If you wait for the screensaver to kick in (i.e. boot and do nothing for 5 mins) then when the screen comes back again the username is not selected. Steps To Reproduce 1. Boot Disco 2. Once you get to the login screen, notice that your username is selected. 3. Do nothing, touch nothing. Wait for the screensaver to kick in and blank the screens. 4. Wiggle the mouse, dismiss the clock screen and you will be back at the login screen 5. Notice that you user is no longer selected and in order to log in you have to move the mouse and click on the user name What should happen The username should be pre-selected so that I can log in without having to use the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822072/+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 1822839] [NEW] LibreOffice doesn't detect JVM because of unexpected java.vendor property value
Public bug reported: libreoffice autopkgtests are failing on disco with openjdk 11.0.3+4-2ubuntu1. The likely culprit is that change: +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium + + * Sync packages with 11.0.3+4-2: +[ Matthias Klose ] +- Configure with vendor flags. Indeed with version 11.0.3+4-1ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Oracle Corporation And with version 11.0.3+4-2ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Private Build Looking at the code in Libreoffice that looks for a JVM, it validates the vendor against a hardcoded list of known vendors: https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33 Not sure what the purpose of that upstream code is, but this means the new openjdk-11 build in Ubuntu breaks it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:06:25 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1003 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: openjdk-lts UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago) ** Affects: df-libreoffice Importance: Unknown Status: Unknown ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Affects: openjdk-lts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: libreoffice autopkgtests are failing on disco with openjdk 11.0.3+4-2ubuntu1. The likely culprit is that change: +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium + + * Sync packages with 11.0.3+4-2: +[ Matthias Klose ] +- Configure with vendor flags. Indeed with version 11.0.3+4-1ubuntu1: - $ java -XshowSettings -version 2>&1 | grep "java.vendor " - java.vendor = Oracle Corporation + $ java -XshowSettings -version 2>&1 | grep "java.vendor " + java.vendor = Oracle Corporation And with version 11.0.3+4-2ubuntu1: - $ java -XshowSettings -version 2>&1 | grep "java.vendor " - java.vendor = Private Build + $ java -XshowSettings -version 2>&1 | grep "java.vendor " + java.vendor = Private Build Looking at the code in Libreoffice that looks for a JVM, it validates the vendor against a hardcoded list of known vendors: https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33 Not sure what the purpose of that upstream code is, but this means the new openjdk-11 build in Ubuntu breaks it. ProblemType: Bug DistroRelease: Ubuntu 19.04 - Package: openjdk-11-jre-headless 11.0.3+4-1ubuntu1 + Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:06:25 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1003 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: openjdk-lts UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago) ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Bug description: libreoffice autopkgtests are failing on disco with openjdk 11.0.3+4-2ubuntu1. The likely culprit is that change: +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium + + * Sync packages with 11.0.3+4-2: +[ Matthias Klose ] +- Configure with vendor flags. Indeed with version 11.0.3+4-1ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Oracle Corporation And with version 11.0.3+4-2ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Private Build Looking at the code in Libreoffice that looks for a JVM, it validates the vendor against a hardcoded list of known vendors: https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cx
[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
** Bug watch added: Document Foundation Bugzilla #124503 https://bugs.documentfoundation.org/show_bug.cgi?id=124503 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=124503 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Bug description: libreoffice autopkgtests are failing on disco with openjdk 11.0.3+4-2ubuntu1. The likely culprit is that change: +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium + + * Sync packages with 11.0.3+4-2: +[ Matthias Klose ] +- Configure with vendor flags. Indeed with version 11.0.3+4-1ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Oracle Corporation And with version 11.0.3+4-2ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Private Build Looking at the code in Libreoffice that looks for a JVM, it validates the vendor against a hardcoded list of known vendors: https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33 Not sure what the purpose of that upstream code is, but this means the new openjdk-11 build in Ubuntu breaks it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:06:25 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1003 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: openjdk-lts UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+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 1817128] Re: gnome-keyring not automatically unlocked on login
Hello guys The problem returned, see attachment Your Considerations *** Olá Pessoal O problema retornou, vide anexo Suas Considerações ** Attachment added: "WhatsApp Image 2019-04-02 at 12.05.34.jpeg" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+attachment/5252088/+files/WhatsApp%20Image%202019-04-02%20at%2012.05.34.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1817128 Title: gnome-keyring not automatically unlocked on login Status in gnome-keyring package in Ubuntu: Fix Released Bug description: Hi After initializing and filling the login screen, at the start screen prompts for password to unlock the session keyring. Is this normal on Ubuntu disk 19.04.02? Note: When filling the login screen to start the micro, should it not be unlocked automatically? Attached the image of the request I fired it. Thank you ** Hi Após inicialização e preenchimento da tela de login, ao iniciar a tela pede senha para desbloqueio do chaveiro de sessão. Isso é normal no Ubuntu disco 19.04.02? Obs: Quando do preenchimento da tela de login para iniciar o micro o desbloqueio não deveria ser automático? Em anexo a imagem da solicitação de desboquei-o. Obrigado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+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 1822838] [NEW] gnome-shell is very large
Public bug reported: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. - Notifications, etc are extremely large. + Notifications, etc are extremely large. - Just everything from the shell is like 40% larger as it should be. This - also happens with default themes, settings, etc. + Just everything from the shell is like 40% larger than it should be. + This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) -- 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/1822838 Title: gnome-shell is very large Status in gnome-shell package in Ubuntu: New Bug description: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+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 1822775] Re: Different input sources per window not work
Confirmed. The setting can be changed in the "Region & Languague" panel: gnome-control-center region (cog icon next to "Input Sources" section) But this doesn't actually change the corresponding gsetting: $ gsettings get org.gnome.desktop.input-sources per-window false ** Package changed: ibus (Ubuntu) => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1822775 Title: Different input sources per window not work Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Ubuntu 19.04 The option to apply different input source for each window doesn't work (it automatically reset itself) However, I manually change org.gnome.desktop.input-sources.per-window and it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1822775/+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 1819023] Re: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen
Apologies, I forgot to get back. Please see the attachment included in this response. Note the effect is very minimal when recorded or shot as a moving GIF. ** Attachment added: "Note the effect appeats very minimal when recorded with a camera." https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1819023/+attachment/5252101/+files/20190402_113806-ANIMATION.gif ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed -- 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/1819023 Title: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen Status in xorg-server package in Ubuntu: Confirmed Bug description: My screen is experiencing a weird "scrolling" flicker, especially while displaying blue, indigo, and violet hues/colors, such as on the default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker scrolls up and down, with the brightest part of the flicker being towards the top, with a gradient that fades back to the original color near the bottom. Problem occurs on any one monitor on any one video output protocol (DVI-D, HDMI, and VGA). I will upload an illustration or render as soon as possible for better explanation. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 10:39:50 2019 DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828] InstallationDate: Installed on 2018-08-17 (202 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: BIOSTAR Group A880G+ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: BIOSTAR Group version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1819023/+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 1822846] Re: Chrome icon disappears from dash
** Attachment added: "Screenshot from 2019-04-02 17-49-09.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822846/+attachment/5252113/+files/Screenshot%20from%202019-04-02%2017-49-09.png -- 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/1822846 Title: Chrome icon disappears from dash Status in gnome-shell package in Ubuntu: New Bug description: From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822846/+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 1822846] [NEW] Chrome icon disappears from dash
Public bug reported: >From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- 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/1822846 Title: Chrome icon disappears from dash Status in gnome-shell package in Ubuntu: New Bug description: From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822846/+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 1815708] Re: Use ODRS for reviews
This bug was fixed in the package gnome-software - 3.30.2-0ubuntu10 --- gnome-software (3.30.2-0ubuntu10) cosmic; urgency=medium * debian/rules: - Switch from deprecated Ubuntu reviews to ODRS (LP: #1815708) * debian/patches/0025-snap-Use-new-media-API.patch: * debian/control: - Disable for now, still blocked on snapd-glib update -- Robert Ancell Thu, 14 Feb 2019 11:52:46 +1300 ** Changed in: gnome-software (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1815708 Title: Use ODRS for reviews Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: New Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Status in gnome-software source package in Disco: Fix Released Bug description: [Impact] The Ubuntu review server is being retired which will cause all Ubuntu package reviews to stop working. We are switching to using the Open Desktop Review Service (https://odrs.gnome.org/). This plugin has existed for sometime in the GNOME Software source, so it is well tested. This change will allow Snap packages to be reviewed (new feature). [Test Case] 1. Open GNOME Software 2. Select a popular app (e.g. Firefox) [Expected Result] Reviews are shown for this package. They will be different to the previous reviews. You are able to create reviews for both .deb and snap apps. [Regression Potential] There is a risk of new bugs encountered in the ODRS plugin. This has been enabled in Disco without major issue and has been used in other distributions for many releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815708/+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 1815708] Update Released
The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1815708 Title: Use ODRS for reviews Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: New Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Status in gnome-software source package in Disco: Fix Released Bug description: [Impact] The Ubuntu review server is being retired which will cause all Ubuntu package reviews to stop working. We are switching to using the Open Desktop Review Service (https://odrs.gnome.org/). This plugin has existed for sometime in the GNOME Software source, so it is well tested. This change will allow Snap packages to be reviewed (new feature). [Test Case] 1. Open GNOME Software 2. Select a popular app (e.g. Firefox) [Expected Result] Reviews are shown for this package. They will be different to the previous reviews. You are able to create reviews for both .deb and snap apps. [Regression Potential] There is a risk of new bugs encountered in the ODRS plugin. This has been enabled in Disco without major issue and has been used in other distributions for many releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815708/+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 1822082] Re: [disco] Shell sometimes shows username instead of full name in top-right menu
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1133 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1133 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1133 Importance: Unknown Status: Unknown -- 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/1822082 Title: [disco] Shell sometimes shows username instead of full name in top- right menu Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The drop-down menu of gnome-shell where you can logout etc. sometimes shows my username (jak) isntead of my fullname. Closing and opening again fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822082/+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 1822846] Re: Chrome icon disappears from dash
** Attachment added: "Screenshot from 2019-04-02 17-49-37.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822846/+attachment/5252114/+files/Screenshot%20from%202019-04-02%2017-49-37.png -- 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/1822846 Title: Chrome icon disappears from dash Status in gnome-shell package in Ubuntu: New Bug description: From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822846/+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 1822846] Re: Chrome icon disappears from dash
See attached screenshots. Not sure if upstream bug or Ubuntu bug, hence reporting here first. -- 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/1822846 Title: Chrome icon disappears from dash Status in gnome-shell package in Ubuntu: New Bug description: From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822846/+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 1799614] Re: Use new media API
This bug was fixed in the package gnome-software - 3.30.2-0ubuntu10 --- gnome-software (3.30.2-0ubuntu10) cosmic; urgency=medium * debian/rules: - Switch from deprecated Ubuntu reviews to ODRS (LP: #1815708) * debian/patches/0025-snap-Use-new-media-API.patch: * debian/control: - Disable for now, still blocked on snapd-glib update -- Robert Ancell Thu, 14 Feb 2019 11:52:46 +1300 ** Changed in: gnome-software (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: In Progress Status in gnome-software source package in Cosmic: Fix Released Status in snapd-glib source package in Cosmic: In Progress Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
Launchpad has imported 1 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=124503. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-04-02T15:27:42+00:00 Olivier Tilloy wrote: Originally reported in Ubuntu: https://launchpad.net/bugs/1822839. A recent OpenJDK update in Ubuntu 19.04 (to be released later this month) changes the value of the "java.vendor" property, from the well- known name "Oracle Corporation" to "Private Build". This breaks the code in LibreOffice that detects an installed JVM, because the vendor name is validated against a hardcoded list: https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33. This change can probably be reverted in Ubuntu, but I'm wondering what the purpose of that hardcoded list of vendors is? Isn't it a valid use case for distributions to change the vendor name? Reply at: https://bugs.launchpad.net/ubuntu/+source/openjdk- lts/+bug/1822839/comments/2 ** Changed in: df-libreoffice Status: Unknown => New ** Changed in: df-libreoffice Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: New Status in libreoffice package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Bug description: libreoffice autopkgtests are failing on disco with openjdk 11.0.3+4-2ubuntu1. The likely culprit is that change: +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium + + * Sync packages with 11.0.3+4-2: +[ Matthias Klose ] +- Configure with vendor flags. Indeed with version 11.0.3+4-1ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Oracle Corporation And with version 11.0.3+4-2ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Private Build Looking at the code in Libreoffice that looks for a JVM, it validates the vendor against a hardcoded list of known vendors: https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33 Not sure what the purpose of that upstream code is, but this means the new openjdk-11 build in Ubuntu breaks it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:06:25 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1003 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: openjdk-lts UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+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 1818595] Update Released
The verification of the Stable Release Update for snapd-glib has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1818595 Title: Update to 1.46 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Status in snapd-glib source package in Disco: Fix Released Bug description: https://wiki.ubuntu.com/SnapdGlibUpdates Overview of changes in snapd-glib 1.46 * New API: - snapd_channel_get_released_at - SNAPD_ERROR_DNS_FAILURE * Fix tests breaking due to undefined order of results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818595/+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 1818766] Update Released
The verification of the Stable Release Update for snapd-glib has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1818766 Title: Update to 1.47 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 Released Status in snapd-glib source package in Cosmic: Fix Released Status in snapd-glib source package in Disco: 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/1818766/+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 1818595] Re: Update to 1.46
This bug was fixed in the package snapd-glib - 1.47-0ubuntu0.18.10.0 --- snapd-glib (1.47-0ubuntu0.18.10.0) cosmic; urgency=medium * New upstream release (LP: #1818766) snapd-glib (1.46-0ubuntu0.18.10.0) cosmic; urgency=medium * New upstream release (LP: #1818595) * debian/rules: - Build with --enable-installed-tests * debian/tests/control: * debian/tests/unit: * debian/snapd-glib-tests.install: - Add autopkg tests * debian/libsnapd-glib-dev.install: * debian/libsnapd-qt-dev.install: - Fix Qt .pc file being in wrong package * debian/libsnapd-glib1.symbols: * debian/libsnapd-qt1.symbols: - Updated -- Robert Ancell Wed, 06 Mar 2019 15:43:11 +1300 ** Changed in: snapd-glib (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1818595 Title: Update to 1.46 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Status in snapd-glib source package in Disco: Fix Released Bug description: https://wiki.ubuntu.com/SnapdGlibUpdates Overview of changes in snapd-glib 1.46 * New API: - snapd_channel_get_released_at - SNAPD_ERROR_DNS_FAILURE * Fix tests breaking due to undefined order of results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818595/+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 1818766] Re: Update to 1.47
This bug was fixed in the package snapd-glib - 1.47-0ubuntu0.18.10.0 --- snapd-glib (1.47-0ubuntu0.18.10.0) cosmic; urgency=medium * New upstream release (LP: #1818766) snapd-glib (1.46-0ubuntu0.18.10.0) cosmic; urgency=medium * New upstream release (LP: #1818595) * debian/rules: - Build with --enable-installed-tests * debian/tests/control: * debian/tests/unit: * debian/snapd-glib-tests.install: - Add autopkg tests * debian/libsnapd-glib-dev.install: * debian/libsnapd-qt-dev.install: - Fix Qt .pc file being in wrong package * debian/libsnapd-glib1.symbols: * debian/libsnapd-qt1.symbols: - Updated -- Robert Ancell Wed, 06 Mar 2019 15:43:11 +1300 ** Changed in: snapd-glib (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1818766 Title: Update to 1.47 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 Released Status in snapd-glib source package in Cosmic: Fix Released Status in snapd-glib source package in Disco: 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/1818766/+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 1818766] Re: Update to 1.47
This bug was fixed in the package snapd-glib - 1.47-0ubuntu0.18.04.0 --- snapd-glib (1.47-0ubuntu0.18.04.0) bionic; urgency=medium * New upstream release (LP: #1818766) * debian/rules: - Build with --enable-installed-tests * debian/tests/control: * debian/tests/unit: * debian/snapd-glib-tests.install: - Add autopkg tests * debian/libsnapd-glib-dev.install: * debian/libsnapd-qt-dev.install: - Fix Qt .pc file being in wrong package * debian/libsnapd-glib1.symbols: * debian/libsnapd-qt1.symbols: - Updated -- Robert Ancell Wed, 06 Mar 2019 15:27:45 +1300 ** Changed in: snapd-glib (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1818766 Title: Update to 1.47 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 Released Status in snapd-glib source package in Cosmic: Fix Released Status in snapd-glib source package in Disco: 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/1818766/+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 1646762] Re: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch
** Changed in: gedit (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gedit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1646762 Title: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch Status in gedit package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.22.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1646762/+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 1822082] Re: [disco] Shell sometimes shows username instead of full name in top-right menu
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822082 Title: [disco] Shell sometimes shows username instead of full name in top- right menu Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The drop-down menu of gnome-shell where you can logout etc. sometimes shows my username (jak) isntead of my fullname. Closing and opening again fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822082/+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 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"
** Changed in: mutter Status: New => Fix Released -- 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/1820331 Title: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON" Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/509 https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971 --- In the last few weeks, gnome-shell has been crashing almost every time I open my laptop to wake it from suspend. The rapid pace of package updates has stopped Apport from letting me report it until now, but the problem persists. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 15 11:22:20 2019 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (1120 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to disco on 2018-12-15 (90 days ago) UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd mock plugdev sambashare sbuild sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820331/+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 1822072] Re: User selector doesn't have focus from login screen after screen turned off
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822072 Title: User selector doesn't have focus from login screen after screen turned off Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: In gdm usually the user name is pre-selected. This means that you can just hit enter and then put your password in. In Disco this is the case on boot up. If you wait for the screensaver to kick in (i.e. boot and do nothing for 5 mins) then when the screen comes back again the username is not selected. Steps To Reproduce 1. Boot Disco 2. Once you get to the login screen, notice that your username is selected. 3. Do nothing, touch nothing. Wait for the screensaver to kick in and blank the screens. 4. Wiggle the mouse, dismiss the clock screen and you will be back at the login screen 5. Notice that you user is no longer selected and in order to log in you have to move the mouse and click on the user name What should happen The username should be pre-selected so that I can log in without having to use the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822072/+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 1818790] Re: [regression] Desktop zoom is missing the mouse pointer
** Changed in: gnome-shell Status: New => 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/1818790 Title: [regression] Desktop zoom is missing the mouse pointer Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Disco: Fix Committed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454 --- Desktop zoom is missing the mouse pointer. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Wed Mar 6 15:12:04 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.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1818790/+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 1646762] Re: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch
Fix proposed upstream: https://gitlab.gnome.org/GNOME/gedit/merge_requests/34 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1646762 Title: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch Status in gedit package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.22.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1646762/+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 1822775] Re: Different input sources per window not work
The corresponding code was added at https://gitlab.gnome.org/GNOME /gnome-control-center/commit/a86cf1eca2734b5ce8b250a7b16db3328945cf42. The problem is the call to g_settings_delay in setup_input_section (https://gitlab.gnome.org/GNOME/gnome-control- center/blob/master/panels/region/cc-region-panel.c#L1207): the corresponding call to g_settings_apply is never issued when changing the per-window setting. -- 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/1822775 Title: Different input sources per window not work Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Ubuntu 19.04 The option to apply different input source for each window doesn't work (it automatically reset itself) However, I manually change org.gnome.desktop.input-sources.per-window and it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1822775/+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 1822854] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1822854/+attachment/5252137/+files/WifiSyslog.txt ** Description changed: - I have this issue where my external monitor (a ThinkVision P24h-10) - connected to my ThinkPad T480s turns off for short times while actively - working on the system. I noticed that if I don't move my mouse at all - while it's off, it stays off. + In disco; I have this issue where my external monitor (a ThinkVision + P24h-10) connected to my ThinkPad T480s turns off for short times while + actively working on the system. I noticed that if I don't move my mouse + at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. - I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). - --- - ProblemType: Bug - ApportVersion: 2.20.10-0ubuntu23 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: jak 17606 F pulseaudio - /dev/snd/controlC1: jak 17606 F pulseaudio - /dev/snd/controlC0: jak 17606 F pulseaudio - CurrentDesktop: GNOME - DistroRelease: Ubuntu 19.04 - InstallationDate: Installed on 2018-03-14 (383 days ago) - InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) - MachineType: LENOVO 20L8S02D00 - Package: linux (not installed) - ProcFB: 0 inteldrmfb - ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash i915.enable_gvt=1 intel_iommu=on vt.handoff=1 - ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 - RelatedPackageVersions: - linux-restricted-modules-5.0.0-7-generic N/A - linux-backports-modules-5.0.0-7-generic N/A - linux-firmware 1.178 - Tags: disco - Uname: Linux 5.0.0-7-generic x86_64 - UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) - UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo - _MarkForUpload: True - dmi.bios.date: 02/19/2019 - dmi.bios.vendor: LENOVO - dmi.bios.version: N22ET53W (1.30 ) - dmi.board.asset.tag: Not Available - dmi.board.name: 20L8S02D00 - 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: None - dmi.modalias: dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: - dmi.product.family: ThinkPad T480s - dmi.product.name: 20L8S02D00 - dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s - dmi.product.version: ThinkPad T480s - dmi.sys.vendor: LENOVO + I have attached /sys/debug/dri/0 output from when the monitor was off + (a) vs on (b). ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822854 Title: External monitor turns off for short period of times / until moving mouse Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: In disco; I have this issue where my external monitor (a ThinkVision P24h-10) connected to my ThinkPad T480s turns off for short times while actively working on the system. I noticed that if I don't move my mouse at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). Other related bits: * This also happens on HDMI, but much less often * There are no log messages when the display turns on/off in the journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+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 1822854] Re: External monitor turns off for short period of times / until moving mouse
** Attachment added: "Display-off debug state" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+attachment/5252138/+files/a -- 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/1822854 Title: External monitor turns off for short period of times / until moving mouse Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: In disco; I have this issue where my external monitor (a ThinkVision P24h-10) connected to my ThinkPad T480s turns off for short times while actively working on the system. I noticed that if I don't move my mouse at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). Other related bits: * This also happens on HDMI, but much less often * There are no log messages when the display turns on/off in the journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+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 1822854] Re: External monitor turns off for short period of times / until moving mouse
** Attachment added: "Display-on debug state (b)" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+attachment/5252139/+files/b -- 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/1822854 Title: External monitor turns off for short period of times / until moving mouse Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: In disco; I have this issue where my external monitor (a ThinkVision P24h-10) connected to my ThinkPad T480s turns off for short times while actively working on the system. I noticed that if I don't move my mouse at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). Other related bits: * This also happens on HDMI, but much less often * There are no log messages when the display turns on/off in the journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+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 1822854] Re: External monitor turns off for short period of times / until moving mouse
** Attachment added: "head of dmesg (journalctl -k) for that boot" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+attachment/5252140/+files/dmesg-boot.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/1822854 Title: External monitor turns off for short period of times / until moving mouse Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: In disco; I have this issue where my external monitor (a ThinkVision P24h-10) connected to my ThinkPad T480s turns off for short times while actively working on the system. I noticed that if I don't move my mouse at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). Other related bits: * This also happens on HDMI, but much less often * There are no log messages when the display turns on/off in the journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+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 1822854] Re: External monitor turns off for short period of times / until moving mouse
Also, FYI: There are no log messages when the display turns on/off in the journal. ** Description changed: In disco; I have this issue where my external monitor (a ThinkVision P24h-10) connected to my ThinkPad T480s turns off for short times while actively working on the system. I noticed that if I don't move my mouse at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). + + Other related bits: + * This also happens on HDMI, but much less often + * There are no log messages when the display turns on/off in the journal. -- 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/1822854 Title: External monitor turns off for short period of times / until moving mouse Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: In disco; I have this issue where my external monitor (a ThinkVision P24h-10) connected to my ThinkPad T480s turns off for short times while actively working on the system. I noticed that if I don't move my mouse at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). Other related bits: * This also happens on HDMI, but much less often * There are no log messages when the display turns on/off in the journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+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 1822854] Re: External monitor turns off for short period of times / until moving mouse
Interesting (?) difference between the i915 debug files: --- display off +++ display on - Active context: [0] user_handle 0 hw_id 0, prio 0, ban score 0 (unbannable) guilty 0 active 0 + ELSP[0]: pid 12429, ban score 0, seqno5:010cd84c, prio 0, emitted 0ms, start 00e21000, head 3c50, tail 3cd8 + Active context: Xorg[12429] user_handle 1 hw_id 5, prio 0, ban score 0 guilty 0 active 0 -- 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/1822854 Title: External monitor turns off for short period of times / until moving mouse Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: In disco; I have this issue where my external monitor (a ThinkVision P24h-10) connected to my ThinkPad T480s turns off for short times while actively working on the system. I noticed that if I don't move my mouse at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). Other related bits: * This also happens on HDMI, but much less often * There are no log messages when the display turns on/off in the journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+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 1822855] [NEW] /usr/lib/gnome-terminal/gnome-terminal-server:11:gdk_x11_device_manager_xi2_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event:
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-terminal. This problem was most recently seen with package version 3.30.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/7033d4850246c8d90bfd2ef08dfcf502078a17c6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco kylin-17.10 zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1822855 Title: /usr/lib/gnome-terminal/gnome-terminal- server:11:gdk_x11_device_manager_xi2_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event:_gdk_x11_display_queue_events:gdk_display_get_event Status in gnome-terminal package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-terminal. This problem was most recently seen with package version 3.30.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/7033d4850246c8d90bfd2ef08dfcf502078a17c6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1822855/+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 1822854] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1822854 Title: External monitor turns off for short period of times / until moving mouse Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: In disco; I have this issue where my external monitor (a ThinkVision P24h-10) connected to my ThinkPad T480s turns off for short times while actively working on the system. I noticed that if I don't move my mouse at all while it's off, it stays off. The T480s is connected to the monitor via USB-C; the monitor provides DP, USB, and Power over that connection. When the display turns off, USB devices continue working. I have attached /sys/debug/dri/0 output from when the monitor was off (a) vs on (b). Other related bits: * This also happens on HDMI, but much less often * There are no log messages when the display turns on/off in the journal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822854/+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 1822857] [NEW] Alt+Tab produces visual artefacts when a child window is open
Public bug reported: Steps to reproduce: 0. Change the default Alt+Tab to switch windows 1. Have some windows open to switch between them 2. Start Thunderbird 3. Go to Account Settings, which is a child window for account settings (or any child window of another app) 4. Press Alt+Tab to switch windows Going through Alt+Tab produces visual artefacts. See the attached screencast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 18:35:42 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (123 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed third-party-packages ** Attachment added: "Screencast_Alt+Tab_visual-artefacts.webm" https://bugs.launchpad.net/bugs/1822857/+attachment/5252141/+files/Screencast_Alt+Tab_visual-artefacts.webm -- 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/1822857 Title: Alt+Tab produces visual artefacts when a child window is open Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 0. Change the default Alt+Tab to switch windows 1. Have some windows open to switch between them 2. Start Thunderbird 3. Go to Account Settings, which is a child window for account settings (or any child window of another app) 4. Press Alt+Tab to switch windows Going through Alt+Tab produces visual artefacts. See the attached screencast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 18:35:42 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (123 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1822857/+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 1816808] Re: [disco] OSK does not appear under wayland when a text-entry is focused
On 2019-03-26 22:38, Gunnar Hjalmarsson wrote: > However, I have a problem with making OSK show up (not using a touch > screen). In LibreOffice Writer it shows up after a mouse click in > the text entry area, but I fail to enable OSK in gedit, > gnome-terminal and Firefox. After an update today, the OSK shows up both in gedit and gnome-terminal (not in FF, though). Anyway, I see no reason to not stop setting GTK_IM_MODULE in Wayland, so I have uploaded a change. ** Changed in: im-config (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: im-config (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: im-config (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: im-config (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1816808 Title: [disco] OSK does not appear under wayland when a text-entry is focused Status in im-config package in Ubuntu: Fix Committed Status in im-config source package in Bionic: Triaged Bug description: 1. Login in a wayland session 2. Open an application with a text entry (e.g. gedit) 3. Focus gedit using the touch screen Expected result: The OSK appears Actual results: The OSK does not appear. --- This is caused by the fact that we still set GTK_IM_MODULE in Wayland. IIRC during the cosmic cycle we introduced a change to not set GTK_IM_MODULE under Wayland but we dropped it because there were users experiencing crashes when using libreoffice: upstream should have fixed those crashes to my knowledge. Also why are we setting GTK_IM_MODULE in X11 too? gnome-settings- daemon should be smart enough to load/unload that at run-time when required/not-required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1816808/+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 1811900] Re: SRU 3.28 latest git to bionic
Bug #1822857 Alt+Tab in gnome-shell produces visual artefacts when a child window is open -- 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/1811900 Title: SRU 3.28 latest git to bionic Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] 3.28 gnome git branch has various upstream approved fixes for many months now, but no release has been done yet, thus we're releasing a git snapshot of the latest approved fixes. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been included in upstream git now, various optimizations to clutter actors could cause drawing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+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 1815889]
(In reply to Michel Dänzer from comment #8) > Mesa doesn't really need explicit thread affinity at all. All it wants is > that certain sets of threads run on the same CPU module; it doesn't care > which particular CPU module that is. What's really needed is an API to > express this affinity between threads, instead of to specific CPU cores. I think the thread affinity API is a correct way to optimize for CPU cache topologies. pthread is a basic user API. Security policies shouldn't disallow pthread functions. -- 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/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Confirmed Status in QEMU: New Status in mesa package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Triaged Status in mesa source package in Disco: Fix Released Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
FYI the QEMU change merged in the following pull request changed to return an EPERM errno for the thread affinity syscalls: commit 12f067cc14b90aef60b2b7d03e1df74cc50a0459 Merge: 84bdc58c06 035121d23a Author: Peter Maydell Date: Thu Mar 28 12:04:52 2019 + Merge remote-tracking branch 'remotes/otubo/tags/pull-seccomp-20190327' into staging pull-seccomp-20190327 # gpg: Signature made Wed 27 Mar 2019 12:12:39 GMT # gpg:using RSA key DF32E7C0F0FFF9A2 # gpg: Good signature from "Eduardo Otubo (Senior Software Engineer) " [full] # Primary key fingerprint: D67E 1B50 9374 86B4 0723 DBAB DF32 E7C0 F0FF F9A2 * remotes/otubo/tags/pull-seccomp-20190327: seccomp: report more useful errors from seccomp seccomp: don't kill process for resource control syscalls Signed-off-by: Peter Maydell IOW, mesa's usage of this syscalls will still be blocked, but it will no longer kill the process. ** Changed in: qemu Status: New => Fix Committed -- 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/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Confirmed Status in QEMU: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Triaged Status in mesa source package in Disco: Fix Released Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1817287] Re: SRU xdg-desktop-portal-gtk 1.0.2
This bug was fixed in the package xdg-desktop-portal-gtk - 1.0.2-0ubuntu1.1 --- xdg-desktop-portal-gtk (1.0.2-0ubuntu1.1) bionic-proposed; urgency=medium * New upstream release 1.0.2 (LP: #1817287) -- Ken VanDine Mon, 10 Dec 2018 14:48:59 -0500 ** Changed in: xdg-desktop-portal-gtk (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1817287 Title: SRU xdg-desktop-portal-gtk 1.0.2 Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Status in xdg-desktop-portal-gtk source package in Xenial: Fix Released Status in xdg-desktop-portal-gtk source package in Bionic: Fix Released Bug description: [Impact] * To improve the snap experience on the desktop we have been working with xdg-desktop-portal-gtk upstream to enable snap support. Portals will greatly improve the snap experience. Full snap support landed in xdg-desktop-portal-gtk 1.0. We're SRU'ing 1.0.2 as it includes bug fixes. * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and xenial, so these will be promoted to main as well. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 Also requires xdg-desktop-portal https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285 [Test Case] * This can be tested by installing the portal-test snap from the edge channel and xdg-desktop-portal also from proposed. Verify the file selection lets you select a file and open local opens test.txt in a text editor of your choice. [Regression Potential] * No regression potential. This package was not seeded by default. It could only have been used by flatpak, however the version in bionic had limited functionality. The package was never available in xenial. [Other Info] * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+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 1817285] Re: SRU xdg-desktop-portal 1.0.3
While the package may not be interesting on ppc64el it's odd that the autopkgtests pass on later releases e.g. cosmic and disco. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1817285 Title: SRU xdg-desktop-portal 1.0.3 Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Xenial: Fix Committed Status in xdg-desktop-portal source package in Bionic: Fix Committed Bug description: [Impact] * To improve the snap experience on the desktop we have been working with xdg-desktop-portal upstream to enable snap support. Portals will greatly improve the snap experience. Full snap support landed in xdg-desktop-portal 1.0. We're SRU'ing 1.0.3 as it includes bug fixes. * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, so these will be promoted to main as well. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 [Test Case] * This can be tested by installing the portal-test snap from the edge channel and xdg-desktop-portal-gtk also from proposed. Verify the file selection lets you select a file and open local opens test.txt in a text editor of your choice. [Regression Potential] * No regression potential. This package was not seeded by default. It could only have been used by flatpak, however, the version in bionic had limited functionality. The package was never available in xenial. [Other Info] * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Does the samba task need fixing in disco at all? ** Changed in: samba (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Invalid Status in samba package in Ubuntu: Incomplete Status in gvfs source package in Bionic: Triaged Status in gvfs source package in Cosmic: Triaged Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM). [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. --- Nautilus should show smbtree and host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor) smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the processing engine) smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5708) smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo) smb-network: send_reply(0x55b19a2e7820), failed=0 () smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708) smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate) smb-network: send_reply(0x55b19a2c30c0), failed=0 () Proposed solution: Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394 which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe NT1 which most users are doing to correct this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+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
