[Desktop-packages] [Bug 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/mag
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/38 -- 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/1826797 Title: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9] Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: [ Impact ] gnome-shell crashes if booted with the monitor off. This leaves me with just a black screen and flashing cursor when I turn the monitor on. [ Test Case ] Boot ubuntu with the monitor off, turn on the monitor. GNOME-Shell should run properly with no errors [ Regression potential ] Mouse cursor isn't scaled properly when using the a11y magnifier Apr 29 09:31:02 kab gnome-shell[995]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:02 kab gnome-shell[995]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:02 kab org.gnome.Shell.desktop[995]: (EE) failed to read Wayland events: Connection reset by peer Apr 29 09:31:03 kab gnome-shell[1076]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1076]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:03 kab gnome-shell[1094]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1094]: Execution of main.js threw exception: Script threw an exception ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Mon Apr 29 09:33:16 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-04 (145 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/ubuntu/+source/gnome-shell/+bug/1826797/+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 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/mag
** Also affects: gnome-shell (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Disco) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Disco) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Disco) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: + [ Impact ] + gnome-shell crashes if booted with the monitor off. This leaves me with just a black screen and flashing cursor when I turn the monitor on. + + [ Test Case ] + + Boot ubuntu with the monitor off, turn on the monitor. + GNOME-Shell should run properly with no errors + + [ Regression potential ] + + Mouse cursor isn't scaled properly when using the a11y magnifier + + Apr 29 09:31:02 kab gnome-shell[995]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:02 kab gnome-shell[995]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:02 kab org.gnome.Shell.desktop[995]: (EE) failed to read Wayland events: Connection reset by peer Apr 29 09:31:03 kab gnome-shell[1076]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1076]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:03 kab gnome-shell[1094]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1094]: Execution of main.js threw exception: Script threw an exception - ProblemType: Bug - DistroRelease: Ubuntu 19.04 + ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Mon Apr 29 09:33:16 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-04 (145 days ago) - InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) - SourcePackage: gnome-shell + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826797 Title: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9] Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: [ Impact ] gnome-shell crashes if booted with the monitor off. This leaves me with just a black screen and flashing cursor when I turn the monitor on. [ Test Case ] Boot ubuntu with the monitor off, turn on the monitor. GNOME-Shell should run properly with no errors [ Regression potential ] Mouse cursor isn't scaled properly when using the a11y magnifier Apr 29 09:31:02 kab gnome-shell[995]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:02 kab gnome-shell[995]: Execution of main.js threw exception: Script
[Desktop-packages] [Bug 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/mag
** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- 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/1826797 Title: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9] Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: [ Impact ] gnome-shell crashes if booted with the monitor off. This leaves me with just a black screen and flashing cursor when I turn the monitor on. [ Test Case ] Boot ubuntu with the monitor off, turn on the monitor. GNOME-Shell should run properly with no errors [ Regression potential ] Mouse cursor isn't scaled properly when using the a11y magnifier Apr 29 09:31:02 kab gnome-shell[995]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:02 kab gnome-shell[995]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:02 kab org.gnome.Shell.desktop[995]: (EE) failed to read Wayland events: Connection reset by peer Apr 29 09:31:03 kab gnome-shell[1076]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1076]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:03 kab gnome-shell[1094]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1094]: Execution of main.js threw exception: Script threw an exception ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Mon Apr 29 09:33:16 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-04 (145 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/ubuntu/+source/gnome-shell/+bug/1826797/+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 1826201] Re: Green vertical bars when using gstreamer-vaapi in Totem under Xorg
Also gst-play-1.0 seems to work fine, and that does use gstreamer-vaapi. So maybe the bug here is more Totem-specific in package 'gstreamer1.0-clutter-3.0'? ** Also affects: clutter-gst-3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: clutter-gst-3.0 (Ubuntu) Status: New => Triaged ** Changed in: clutter-gst-3.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clutter-gst-3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1826201 Title: Green vertical bars when using gstreamer-vaapi in Totem under Xorg Status in GStreamer: New Status in clutter-gst-3.0 package in Ubuntu: Triaged Status in gstreamer-vaapi package in Ubuntu: Triaged Bug description: MP4 videos cannot be played using the video player (TOTEM). This might be an upgrade problem. VLC and other video players are working fine but i prefer to use totem I have attached a video recording showing the problem in detail. All was working fine before the upgrade. PS : I understand this problem is not related to the package "ubuntu-release-upgrader" but i cannot change it without getting errors( Launchpad and Ubuntu-bug problem ) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-release-upgrader-core 1:19.04.16.1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 13:32:53 2019 InstallationDate: Installed on 2018-06-12 (315 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to disco on 2019-04-20 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1826201/+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 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide
Launchpad has imported 2 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1696788. 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-05T16:04:51+00:00 mkrajnak wrote: Description of problem: I am getting those messages while running yelp in 7.7, I am not seeing them on RHEL-8 with X session Version-Release number of selected component (if applicable): yelp-libs-3.28.1-1.el7.x86_64 yelp-xsl-3.28.0-1.el7.noarch yelp-3.28.1-1.el7.x86_64 yelp-tools-3.28.0-1.el7.noarch How reproducible: always Steps to Reproduce: 1.Run yelp from terminal 2.Click on getting started with Gnome Actual results: [test@localhost ~]$ yelp failed to create drawable Xlib: sequence lost (0x100cd > 0xcf) in reply type 0x0! Xlib: sequence lost (0x100cb > 0xcf) in reply type 0x0! Xlib: sequence lost (0x100d2 > 0xd6) in reply type 0x0! Xlib: sequence lost (0x100d9 > 0xdd) in reply type 0x0! Xlib: sequence lost (0x100e0 > 0xe4) in reply type 0x0! Xlib: sequence lost (0x100e7 > 0xeb) in reply type 0x0! Xlib: sequence lost (0x100ee > 0xf2) in reply type 0x0! Xlib: sequence lost (0x100f5 > 0xf7) in reply type 0x0! Xlib: sequence lost (0x100fa > 0xfc) in reply type 0x0! Expected results: no err messages Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-getting- started-docs/+bug/1804786/comments/9 On 2019-04-05T16:10:09+00:00 mkrajnak wrote: Also something like this, not sure if those indicating some errors as well Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating bg color Recursion depth exceeded calculating fg color Recursion depth exceeded calculating bg color Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-getting- started-docs/+bug/1804786/comments/10 ** Changed in: yelp Status: Unknown => Confirmed ** Changed in: yelp Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-getting-started-docs in Ubuntu. https://bugs.launchpad.net/bugs/1804786 Title: Garbage occurred when Playing the video in the Ubuntu Desktop Guide Status in Yelp: Confirmed Status in gnome-getting-started-docs package in Ubuntu: Confirmed Bug description: Garbage occurred when Playing the video in the Ubuntu Desktop Guide. Reproduce step 1. Ubuntu 18.04.1. 2. ubuntu-docs 18.04.4 3. Playing the video(Launch applications) from Help-->Getting started with GNOME. 4. Garbage occurred after the video repeat about 3 times==> issue. Expected results: The Video can be played normally no-matter how many times. Actual results: Garbage occurred after the video repeat about 3 times Note: 1. the video will show blank but still have the voice after the issue finish. 2. Right click the mouse and choice "save video as", this application will crashed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-docs 18.04.4 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 23 16:46:00 2018 InstallationDate: Installed on 2018-04-30 (206 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-docs UpgradeStatus:
[Desktop-packages] [Bug 1813716] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_na
** Changed in: gnome-shell (Ubuntu Disco) Status: New => In Progress ** Changed in: mutter (Ubuntu Disco) Status: New => In Progress ** Description changed: + [ Impact ] + + GNOME Shell crashes on restart or when ending the session + + [ Test Case ] + + Under X11, try to reload the shell multiple times using + - Alt+F2: write 'r', press 'enter'. + - Or quit it writing in the run dialog 'debugexit'. + + Repeat multiple times, no crash caused by x11 calls should happen. + + [ Regression potential ] + + Nothing known, window actors might not be painted on reload. + + --- + + Tracked upstream in https://gitlab.gnome.org/GNOME/mutter/issues/576 Proposed fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/557 - 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.2-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/a27089759201dfe884a9070c2d62c50680fb2de4 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/. ** Changed in: mutter (Ubuntu Disco) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Disco) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Disco) Importance: High => Medium ** Changed in: gnome-shell (Ubuntu Eoan) Importance: High => Medium ** Changed in: mutter (Ubuntu Disco) Importance: High => Medium -- 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/1813716 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_native_object Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Status in mutter source package in Disco: In Progress Status in gnome-shell source package in Eoan: In Progress Status in mutter source package in Eoan: In Progress Bug description: [ Impact ] GNOME Shell crashes on restart or when ending the session [ Test Case ] Under X11, try to reload the shell multiple times using - Alt+F2: write 'r', press 'enter'. - Or quit it writing in the run dialog 'debugexit'. Repeat multiple times, no crash caused by x11 calls should happen. [ Regression potential ] Nothing known, window actors might not be painted on reload. --- Tracked upstream in https://gitlab.gnome.org/GNOME/mutter/issues/576 Proposed fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/557 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.2-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/a27089759201dfe884a9070c2d62c50680fb2de4 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/mutter/+bug/1813716/+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 1813716] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_na
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/36 -- 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/1813716 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_native_object Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Status in mutter source package in Disco: In Progress Status in gnome-shell source package in Eoan: In Progress Status in mutter source package in Eoan: In Progress Bug description: [ Impact ] GNOME Shell crashes on restart or when ending the session [ Test Case ] Under X11, try to reload the shell multiple times using - Alt+F2: write 'r', press 'enter'. - Or quit it writing in the run dialog 'debugexit'. Repeat multiple times, no crash caused by x11 calls should happen. [ Regression potential ] Nothing known, window actors might not be painted on reload. --- Tracked upstream in https://gitlab.gnome.org/GNOME/mutter/issues/576 Proposed fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/557 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.2-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/a27089759201dfe884a9070c2d62c50680fb2de4 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/mutter/+bug/1813716/+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 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)
Great!
By the way, one possible reason why you were unable to follow comment #2
is that gdm is designed to catch mutter/gnome-shell crashes in the
Wayland backend (which it tries first). If such a crash occurs then it
is meant to automatically fall back to Xorg.
Regardless of whether the automatic fallback was working for you, that
crash handling done by gdm would possibly prevent any crash in mutter
/gnome-shell Wayland start-up from being saved and sent to Ubuntu :(
--
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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
New
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
I can also confirm that this is still happening with Ubuntu 16.04 LTS
duplicity-backup.sh v1.6.0
duplicity 0.7.19
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename: xenial
---[ Program versions ]---
duplicity-backup.sh v1.6.0
duplicity 0.7.19
--
LFTP version is 4.6.3a
Traceback (innermost last):
File "/usr/bin/duplicity", line 1581, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1567, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1419, in main
do_backup(action)
File "/usr/bin/duplicity", line 1441, in do_backup
action).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 684,
in set_values
backend_filename_list = self.backend.list()
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 301:
ordinal not in range(128)
[ Duplicity Cleanup ]
LFTP version is 4.6.3a
Traceback (innermost last):
File "/usr/bin/duplicity", line 1581, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1567, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1419, in main
do_backup(action)
File "/usr/bin/duplicity", line 1441, in do_backup
action).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 684,
in set_values
backend_filename_list = self.backend.list()
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 301:
ordinal not in range(128)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
Status in Duplicity:
Fix Committed
Status in duplicity package in Ubuntu:
Fix Released
Bug description:
backup worked under Ubuntu 17.10
It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
my drive is encrypted
this is the error message in the error frame
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 09:55:00 2018
InstallationDate: Installed on 2018-05-01 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)
I didn't know how to log into "Ubuntu" instead of "Ubuntu on Wayland"
since I only got a blinking cursor and no logon prompt. I edited
/etc/gdm3/custom.conf and rebooted.
Successfully got a GUI logon prompt and was able to log in to the
desktop.
--
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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
New
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide
The problem seems not to be Ubuntu specific.
https://bugzilla.redhat.com/show_bug.cgi?id=1696788
(I get those "Recursion depth exceeded calculating {bg,fg} color"
messages too on eoan and disco.
** Bug watch added: Red Hat Bugzilla #1696788
https://bugzilla.redhat.com/show_bug.cgi?id=1696788
** Also affects: yelp via
https://bugzilla.redhat.com/show_bug.cgi?id=1696788
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-getting-started-docs in Ubuntu.
https://bugs.launchpad.net/bugs/1804786
Title:
Garbage occurred when Playing the video in the Ubuntu Desktop Guide
Status in Yelp:
Unknown
Status in gnome-getting-started-docs package in Ubuntu:
Confirmed
Bug description:
Garbage occurred when Playing the video in the Ubuntu Desktop Guide.
Reproduce step
1. Ubuntu 18.04.1.
2. ubuntu-docs 18.04.4
3. Playing the video(Launch applications) from Help-->Getting started with
GNOME.
4. Garbage occurred after the video repeat about 3 times==> issue.
Expected results: The Video can be played normally no-matter how many
times.
Actual results: Garbage occurred after the video repeat about 3 times
Note:
1. the video will show blank but still have the voice after the issue finish.
2. Right click the mouse and choice "save video as", this application will
crashed
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-docs 18.04.4
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 23 16:46:00 2018
InstallationDate: Installed on 2018-04-30 (206 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: ubuntu-docs
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/yelp/+bug/1804786/+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 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)
** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
New
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1827169] Re: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1827169 Title: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in desktop-file-utils package in Ubuntu: New Bug description: Attempting to install lyx from command-line with sudo apt install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: desktop-file-utils 0.22-1ubuntu5.2 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed May 1 13:14:35 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-19 (43 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1827169/+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 1827169] [NEW] package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Attempting to install lyx from command-line with sudo apt install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: desktop-file-utils 0.22-1ubuntu5.2 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed May 1 13:14:35 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-19 (43 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1827169 Title: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in desktop-file-utils package in Ubuntu: New Bug description: Attempting to install lyx from command-line with sudo apt install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: desktop-file-utils 0.22-1ubuntu5.2 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed May 1 13:14:35 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-19 (43 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1827169/+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 1827059] Re: Gnome-shell won't lock screen anymore
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827059 Title: Gnome-shell won't lock screen anymore Status in gnome-shell package in Ubuntu: Invalid Bug description: When I press the lock shortcut Gnome Shell won't lock screen: instead it "blinks" (top bar disappears for a moment) and comes back, no lock screen or password asked. Closing screen (laptop) does the same but I still get low consumption, so hibernation seems to be working, but there is no password asked after opening. I get this error in dmesg: ``` [10413.140792] gnome-shell[28745]: segfault at fbc8 ip 7f37ab2c6ec8 sp 7ffdc4a371d0 error 5 in libst-1.0.so[7f37ab2a+2b000] [10413.140798] Code: 00 00 48 8d 3d 57 78 00 00 e9 34 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d db 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d ``` I tried to "apt-get install --reinstall gnome-shell", or "uninstall --purge" it and install back, but nothing works. It has started right after an update 2 or 3 days ago, supposedly related to 19.04? I obviously never disabled the password on lock screen :) by the way it's working perfectly if I chose standard GNOME desktop on login. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.2-0ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 14:33:31 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-04-13 (381 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/zsh SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-24 (188 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827059/+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 1827118] Re: Boot black screen
I can't see any problem in the files attached so far. We need a log file covering the period of time when the problem actually happened. To get that please: 1. Reproduce the problem. 2. Reboot and then immediately run: journalctl -b-1 > prevboot.txt and then attach the file 'prevboot.txt' to this bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1827118 Title: Boot black screen Status in Ubuntu: Incomplete Bug description: At several times boot stops and each time no boot menu (Grub) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 20:53:28 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21dd] InstallationDate: Installed on 2019-04-29 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 7829A71 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=4f77cbd0-dae8-4ab6-a7bb-2af4093855de ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 7829A71 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn7829A71:pvrThinkPadL420:rvnLENOVO:rn7829A71:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L420 dmi.product.name: 7829A71 dmi.product.version: ThinkPad L420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827118/+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 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly
This bug appear a few time today after I upgrade my system to ubuntu19.04. This is definitely a bug. widon@widon-X555YI:~$ uname -a Linux widon-X555YI 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1805077 Title: [ASUS X555YI] the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: Incomplete Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1805077/+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 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)
Also, to avoid Wayland fully, please edit /etc/gdm3/custom.conf and
uncomment:
#WaylandEnable=false
then 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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1827031] Re: Desktop wallpaper and lock screen wallpaper corrupted after waking up the system
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1809407, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1809407 [nvidia] Corrupted wallpaper after resuming from suspend -- 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/1827031 Title: Desktop wallpaper and lock screen wallpaper corrupted after waking up the system Status in gnome-shell package in Ubuntu: New Bug description: Desktop wallpaper and lock screen wallpaper corrupted after waking up the system ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 13:39:10 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell XPS 15 9550 [1028:06e4] Subsystem: Dell XPS 15 9550 [1028:06e4] InstallationDate: Installed on 2019-04-28 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=/dev/nvme0n1p4 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0Y9N5X dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd02/25/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA07:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827031/+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 1826944] Re: Green bars in ubuntu videos when using gstreamer1.0-vaapi
*** This bug is a duplicate of bug 1826201 *** https://bugs.launchpad.net/bugs/1826201 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1826201, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - green bars in ubuntu videos + Green bars in ubuntu videos when using gstreamer1.0-vaapi ** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu) ** Changed in: gstreamer-vaapi (Ubuntu) Status: Incomplete => New ** This bug has been marked a duplicate of bug 1826201 Green vertical bars when using gstreamer-vaapi in Totem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1826944 Title: Green bars in ubuntu videos when using gstreamer1.0-vaapi Status in gstreamer-vaapi package in Ubuntu: New Bug description: When I try to play a .mp4 video in Ubuntu Video, I get a screen with green bars all over. The problem does not occur when I switch to my nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:02:44 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] [1043:1590] InstallationDate: Installed on 2019-04-28 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. GL753VE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1826944/+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 1826025] Re: gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling gbm_surface_lock_front_buffer)
** No longer affects: linux (Ubuntu)
** Summary changed:
- gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer:
Function not implemented" on Matrox graphics card)
** Changed in: mesa (Ubuntu)
Importance: High => Low
** Changed in: mutter (Ubuntu)
Importance: High => Low
** Changed in: mesa (Ubuntu)
Status: New => Triaged
** Changed in: mutter (Ubuntu)
Status: New => 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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications
[Desktop-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot
Dear Sebastian, Thanks for your response. I've raised the bug upstream here: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166 I'll try to keep this bug stream and that one coordinated. ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #166 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in network-manager package in Ubuntu: Confirmed Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)
Tracking upstream (I think) in
https://gitlab.gnome.org/GNOME/mutter/issues/57
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu)
** Summary changed:
- gnome-shell trap int3 no desktop (MGA G200eW fails when calling
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling
gbm_surface_lock_front_buffer)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #57
https://gitlab.gnome.org/GNOME/mutter/issues/57
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/57
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
[Desktop-packages] [Bug 1826025] 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)
** Package changed: glib2.0 (Ubuntu) => mutter (Ubuntu)
--
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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile: /home/greg/xorg.conf.new
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.20.4-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop
It appears this message keeps happening with the gnome-shell crash:
"Impossible to lock surface front buffer: Function not implemented"
that's from mutter's "native" (Wayland) backend:
next_bo = gbm_surface_lock_front_buffer (gbm_surface);
if (!next_bo)
{
g_error ("Impossible to lock surface front buffer: %m");
return FALSE;
}
so it means your kernel graphics driver (mgag200) does not fully support
Wayland sessions.
Please just use Xorg sessions instead (log into "Ubuntu" instead of
"Ubuntu on Wayland").
** Summary changed:
- gnome-shell trap int3 no desktop
+ gnome-shell trap int3 no desktop (MGA G200eW fails when calling
gbm_surface_lock_front_buffer)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer: Function not implemented" on Matrox graphics card)
Status in Mutter:
Unknown
Status in mesa package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36
PST 2019
GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
Date: Tue Apr 23 09:56:22 2019
DistUpgraded: 2019-04-22 15:16:02,086 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: disco
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
(prog-if 00 [VGA controller])
Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
[1458:3703]
InstallationDate: Installed on 2012-02-14 (2625 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64
(20111011)
MachineType: Supermicro X8DT3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.2
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT3
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.family: 1234567890
dmi.product.name: X8DT3
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
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-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Mon Apr 22 20:53:09 2019
xserver.configfile:
[Desktop-packages] [Bug 1817620] Re: High cpu usage on alt-tab-ing
Please try: (1) Updating your system, since the fix mentioned in comment #1 should now be included in 18.04 updates. Maybe this bug has been fixed. (2) If you do restart gnome-shell and find that improves performance, then wait another 30 seconds or more and retest. Does it get slower again after 30 seconds? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1817620 Title: High cpu usage on alt-tab-ing Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Switching between apps was feeling extremely laggy and unsmooth after some days of keeping the laptop on and just alt-tab-ing between apps would keep the cpu consistently at 100% when hitting it more than 8-9 times per second and *not* letting go of Alt (meaning I stay at the same app). Some investigation (1) led me to try out restarting the gnome-shell instance (killall followed by manually starting it in the terminal), upon which everything seemed zippy again. No lagginess. The restart was a supposed fix for a memory leak bug (2), but according to the comments a bug fix was supposed to have landed in 18.04 long ago. So either this has not been fixed or this bug is about something else - probably the latter, as the reported memory usage in htop was nowhere near the gigabytes of memory reported in the bug issue for 16722297. Another thing worth mentioning perhaps, based on comments in (3) found through (4), is that I have disabled all extensions. I used to use the Coverflow extension. Expected behaviour: There should be no percieved lag or stuttering in the interface when switching between applications. Actual behaviour: Switching between applications causes a noticable lag/stuttering when the computer has been running for an extended period of time (weeks, but where it has mostly been suspended, meaning actual usage is limited to 3-4 days). 1. https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts 2. https://bugs.launchpad.net/gnome-shell/+bug/1672297 3. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959 4. https://askubuntu.com/a/1090987/165026 System info: Running Wayland. Description: Ubuntu 18.04.1 LTS Release: 18.04 gnome-shell: Installert: 3.28.3-0ubuntu0.18.04.4 Kandidat: 3.28.3-0ubuntu0.18.04.4 Versjonstabell: *** 3.28.3-0ubuntu0.18.04.4 500 500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages edit: removed info on high cpu usage when using mouse. supposedly unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+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 1822392] Re: gsd-media-keys fails to adjust the screen brightness after unlocking
that does never work for me `sudo /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93 fish: “sudo /usr/lib/gnome-settings-da…” terminated by signal SIGSEGV (Address boundary error) ` gsd-backlight-h[19085]: segfault at 0 ip 7f7235fe25ee sp 7fff88c62278 error 4 in libc-2.29.so[7f7235e86000+173000] [499265.506514] Code: 0f 84 f9 fe ff ff e9 51 89 f3 ff 90 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 56 03 00 00 c5 fe 6f 0f f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 74 7e f3 0f -- 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/1822392 Title: gsd-media-keys fails to adjust the screen brightness after unlocking Status in gnome-settings-daemon package in Ubuntu: New Bug description: Whne my machine sat for some time (laptop, screen off) it is not possible to change the screen brighness of the display for some time after unlocking. After 3-5 minutes it will eventually just work again. journalctl logs the following är 30 01:17:02 dbus-daemon[975]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.212' (uid=1000 pid=14229 comm="/usr/bin/gnome-shell " label="uncon Mär 30 01:17:02 systemd[1]: Starting Fingerprint Authentication Daemon... Mär 30 01:17:02 dbus-daemon[975]: [system] Successfully activated service 'net.reactivated.Fprint' Mär 30 01:17:02 systemd[1]: Started Fingerprint Authentication Daemon. Mär 30 01:17:06 gdm-password][605]: gkr-pam: unlocked login keyring Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.137' (uid=1000 pid=808 comm="/usr/ Mär 30 01:17:45 systemd[14145]: Starting GNOME Terminal Server... Mär 30 01:17:45 gnome-terminal-server[813]: Display does not support owner-change; copy/paste will be broken! Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Successfully activated service 'org.gnome.Terminal' Mär 30 01:17:45 systemd[14145]: Started GNOME Terminal Server. Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/interface/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/sound/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage: Timeout was reached Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage: Timeout was reached Mär 30 01:17:55 pkexec[845]: pam_unix(polkit-1:session): session opened
[Desktop-packages] [Bug 1824738] Re: gvfsd-admin crashed with signal 5
** Changed in: gvfs Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1824738 Title: gvfsd-admin crashed with signal 5 Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Fix Committed Bug description: I'm afraid I have no further information on what may have caused this to occur. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.36.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 03:19:01 2019 ExecutablePath: /usr/lib/gvfs/gvfsd-admin ProcCmdline: /usr/lib/gvfs/gvfsd-admin --help Signal: 5 SourcePackage: gvfs StacktraceTop: () () __libc_start_main (main=0x55cf5bb5f8d0, argc=2, argv=0x7fff172c4978, init=, fini=, rtld_fini=, stack_end=0x7fff172c4968) at ../csu/libc-start.c:310 () Title: gvfsd-admin crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax libvirt libvirtd lpadmin lxd plugdev sambashare sudo users vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1824738/+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 1816231] Re: There is regular screen flickering/flashing (when the mouse isn't moving)
The file 'journal.txt' is created in the current directory when you run: journalctl -b0 > journal.txt But if you have successfully removed 'xserver-xorg-video-intel' then you may not need to do anything more. Did that fix it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1816231 Title: There is regular screen flickering/flashing (when the mouse isn't moving) Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I have installed the 18.04.2 lts version. I have a basic intel graphics card It says unable to locate package pkgname when I type apt-cache policy pkgname. I think it's a problem with the xorg file. not sure. When the mouse tracker is moving there does'nt seem to be a problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 18:06:57 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2019-02-16 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. X555LAB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef09309f-b8f6-4d98-9c90-7b08ac5e2392 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1816231/+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 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
** Changed in: gnome-control-center Status: Unknown => New -- 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/1827154 Title: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 --- [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1809788] Re: Shell dialog messages are truncated and ellipsized...
** 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/1809788 Title: Shell dialog messages are truncated and ellipsized... Status in GNOME Shell: New Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Bug description: When plugging in a Thunderbolt device, under certain conditions, there could be a pop-up window asking for authentication from the user. In the dialog box, the prompt text is truncated. Please refer to attached screen shot for more details. The issue can be found in the gnome-control-center package for bionic: 1:3.28.2-0ubuntu0.18.04.2 1:3.28.1-0ubuntu1 However, the issue is confirmed to be gone in latest such package for Cosmic: 1:3.30.2-1ubuntu0.18.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809788/+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 1809788] Re: bionic - TBT authentication message will be cut from the dialog box
Tracking upstream in https://gitlab.gnome.org/GNOME/gnome- shell/issues/922 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #922 https://gitlab.gnome.org/GNOME/gnome-shell/issues/922 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/922 Importance: Unknown Status: Unknown ** Summary changed: - bionic - TBT authentication message will be cut from the dialog box + Shell dialog messages are truncated and ellipsized... -- 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/1809788 Title: Shell dialog messages are truncated and ellipsized... Status in GNOME Shell: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Bug description: When plugging in a Thunderbolt device, under certain conditions, there could be a pop-up window asking for authentication from the user. In the dialog box, the prompt text is truncated. Please refer to attached screen shot for more details. The issue can be found in the gnome-control-center package for bionic: 1:3.28.2-0ubuntu0.18.04.2 1:3.28.1-0ubuntu1 However, the issue is confirmed to be gone in latest such package for Cosmic: 1:3.30.2-1ubuntu0.18.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809788/+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 1809788] Re: Shell dialog messages are truncated and ellipsized...
I would say remove Yaru here. The theme can't directly control whether the dialog is too small and needs wrapping. Although it can control the dialog size indirectly with some tweaks, but doing that would be a hack. I think this is a pure Gnome Shell bug. -- 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/1809788 Title: Shell dialog messages are truncated and ellipsized... Status in GNOME Shell: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Bug description: When plugging in a Thunderbolt device, under certain conditions, there could be a pop-up window asking for authentication from the user. In the dialog box, the prompt text is truncated. Please refer to attached screen shot for more details. The issue can be found in the gnome-control-center package for bionic: 1:3.28.2-0ubuntu0.18.04.2 1:3.28.1-0ubuntu1 However, the issue is confirmed to be gone in latest such package for Cosmic: 1:3.30.2-1ubuntu0.18.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809788/+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 1809788] Re: Shell dialog messages are truncated and ellipsized...
I can't see any history of a fix. But it's only reported in 3.28 here and 3.30 upstream...? -- 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/1809788 Title: Shell dialog messages are truncated and ellipsized... Status in GNOME Shell: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Bug description: When plugging in a Thunderbolt device, under certain conditions, there could be a pop-up window asking for authentication from the user. In the dialog box, the prompt text is truncated. Please refer to attached screen shot for more details. The issue can be found in the gnome-control-center package for bionic: 1:3.28.2-0ubuntu0.18.04.2 1:3.28.1-0ubuntu1 However, the issue is confirmed to be gone in latest such package for Cosmic: 1:3.30.2-1ubuntu0.18.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809788/+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 1826688] Re: GNOME Shell icon grid fade in/out is sometimes missing at the top/bottom of the screen
I added the newest journalctl to the post above, and here's the entire thing. ** Description changed: After installing an update for Ubuntu 18.04 LTS, GNOME's App Launcher screen faces graphical issues when scrolling. To reproduce this, simply open the Application menu and scroll in the paginated list. If the bug is present, the screen will fail to update completly; the animation wil play through, but the icons will remain in place or "chopped off," it seems the frame isn't completly refreshed? It's fixed after a few seconds or by moving the mouse. I'm using GNOME 3.28.2 on Ubuntu 18.04 LTS I'm also using an Nvidia card for graphics (with drivers installed) I attached a picture (Sorry that it isn't a screenshot!) + + EDIT 4/30/19: Here's `journalctl` (I ran the command, performed the + action. If this doesn't cut it, I attached the entire journalctl + below.): + + ``` + Apr 30 21:24:15 pj-desktop anacron[14623]: Updated timestamp for job `cron.daily' to 2019-04-30 + Apr 30 21:24:15 pj-desktop cracklib[14653]: no dictionary update necessary. + Apr 30 21:24:16 pj-desktop systemd[1]: Stopping Make remote CUPS printers available locally... + Apr 30 21:24:16 pj-desktop systemd[1]: Stopped Make remote CUPS printers available locally. + Apr 30 21:24:16 pj-desktop systemd[1]: Stopping CUPS Scheduler... + Apr 30 21:24:16 pj-desktop systemd[1]: Stopped CUPS Scheduler. + Apr 30 21:24:16 pj-desktop gsd-color[2010]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_Canon_MF720C_Series + Apr 30 21:24:16 pj-desktop gsd-color[1624]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_Canon_MF720C_Series + Apr 30 21:24:16 pj-desktop systemd[1]: Closed CUPS Scheduler. + Apr 30 21:24:16 pj-desktop systemd[1]: Stopping CUPS Scheduler. + Apr 30 21:24:16 pj-desktop systemd[1]: Listening on CUPS Scheduler. + Apr 30 21:24:16 pj-desktop systemd[1]: Stopped CUPS Scheduler. + Apr 30 21:24:16 pj-desktop systemd[1]: Stopping CUPS Scheduler. + Apr 30 21:24:16 pj-desktop systemd[1]: Started CUPS Scheduler. + Apr 30 21:24:16 pj-desktop systemd[1]: Started CUPS Scheduler. + Apr 30 21:24:16 pj-desktop systemd[1]: Started Make remote CUPS printers available locally. + Apr 30 21:24:16 pj-desktop colord[1115]: failed to get session [pid 14745]: No data available + Apr 30 21:24:16 pj-desktop rsyslogd[1038]: [origin software="rsyslogd" swVersion="8.32.0" x-pid="1038" x-info="http://www.rsyslog.com;] rsyslogd was HUPed + Apr 30 21:24:17 pj-desktop colord[1115]: failed to get session [pid 14745]: No data available + Apr 30 21:24:18 pj-desktop pkexec[14767]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) + Apr 30 21:24:18 pj-desktop pkexec[14767]: pj: Executing command [USER=root] [TTY=unknown] [CWD=/home/pj] [COMMAND=/usr/lib/update-notifier/package-system-locked] + Apr 30 21:24:30 pj-desktop anacron[10055]: Job `cron.daily' terminated + Apr 30 21:24:30 pj-desktop anacron[10055]: Normal exit (1 job run) + + ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Apr 27 20:51:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-25 (123 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Attachment added: "gnomelog.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826688/+attachment/5260439/+files/gnomelog.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/1826688 Title: GNOME Shell icon grid fade in/out is sometimes missing at the top/bottom of the screen Status in gnome-shell package in Ubuntu: New Bug description: After installing an update for Ubuntu 18.04 LTS, GNOME's App Launcher screen faces graphical issues when scrolling. To reproduce this, simply open the Application menu and scroll in the paginated list. If the bug is present, the screen will fail to update completly; the animation wil play through, but the icons will remain in place or "chopped off," it seems the frame isn't completly refreshed? It's fixed after a few seconds or by moving the mouse. I'm using GNOME 3.28.2 on Ubuntu 18.04 LTS I'm also using an Nvidia card for graphics (with drivers
[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
Marking as verification-failed as per the last couple of comments. It looks like that might want to be split out into a new bug, particularly as it also affects cosmic (and disco?) ** Tags removed: verification-done ** Tags added: regression-proposed verification-failed ** Tags removed: verification-done-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom
Yeah, we seem to only be getting crash reports from 3.28 (bionic) now... https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a ** Also affects: gnome-session (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Also affects: gnome-session (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: gnome-session (Ubuntu Eoan) Status: Confirmed => Fix Released ** Changed in: gnome-session (Ubuntu Bionic) Status: New => Confirmed ** Changed in: gnome-session (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gnome-session (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: gnome-session (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: gnome-session (Ubuntu Disco) Status: New => Fix Released ** Changed in: gnome-session (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1715365 Title: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display() Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Bionic: Confirmed Status in gnome-session source package in Cosmic: Fix Released Status in gnome-session source package in Disco: Fix Released Status in gnome-session source package in Eoan: Fix Released Bug description: Possibly: https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a --- bug at login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-session-bin 3.25.90-0ubuntu2 Uname: Linux 4.12.0-041200-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Sep 3 09:34:09 2017 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated InstallationDate: Installed on 2015-04-16 (874 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: () g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gdk_x11_atom_to_xatom_for_display () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, init=, fini=, rtld_fini=, stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291 Title: gnome-session-check-accelerated crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1715365/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 [ Impact ] - GNOME Shell crashes in st_widget_get_theme_node [ Test Case ] - No clear test case for this, monitoring errors.ubuntu.com is the only feasible solution [ Regression Potential ] Shell actors might have wrong theming. The crash will be converted in error trackable through journalctl --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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/1796606/+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 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- 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/1827154 Title: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 --- [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1827158] Re: nautilus 1:3.26.4-0~ubuntu18.04.4 crash
** Attachment added: "_usr_bin_nautilus.1000.crash" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1827158/+attachment/5260436/+files/_usr_bin_nautilus.1000.crash -- 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/1827158 Title: nautilus 1:3.26.4-0~ubuntu18.04.4 crash Status in nautilus package in Ubuntu: New Bug description: widon@widon-X555YI:/var/log$ dpkg -l | grep nautilus ii nautilus 1:3.26.4-0~ubuntu18.04.4 amd64file manager and graphical shell for GNOME I don't how to reproduce it, it happens when I copy some picture from Desktop to Pictures folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1827158/+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 1827158] [NEW] nautilus 1:3.26.4-0~ubuntu18.04.4 crash
Public bug reported: widon@widon-X555YI:/var/log$ dpkg -l | grep nautilus ii nautilus 1:3.26.4-0~ubuntu18.04.4 amd64file manager and graphical shell for GNOME I don't how to reproduce it, it happens when I copy some picture from Desktop to Pictures folder. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "It happens in 22:34, you can search "crash" in syslog" https://bugs.launchpad.net/bugs/1827158/+attachment/5260435/+files/syslog -- 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/1827158 Title: nautilus 1:3.26.4-0~ubuntu18.04.4 crash Status in nautilus package in Ubuntu: New Bug description: widon@widon-X555YI:/var/log$ dpkg -l | grep nautilus ii nautilus 1:3.26.4-0~ubuntu18.04.4 amd64file manager and graphical shell for GNOME I don't how to reproduce it, it happens when I copy some picture from Desktop to Pictures folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1827158/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
@EDEMPCO I haven't had the issue since I updated to Ubuntu 18.04 (or stopped using the 4.13.x series on 16.04). Are you using the kernel provided by the distribution? Can you try running one of the 4.10.x kernels to see if that fixes it? Also are you sure you have this specific bug, and not any of the many other hibernation bugs? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Won't Fix Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1826025] Re: gnome-shell trap int3 no desktop
Uninstalled xorgxrdp, no change: /var/log/apport.log: ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: called for pid 2790, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: debug: session gdbus call: (false,) ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: happens for shutting down session, ignoring syslog: Apr 30 16:47:43 mizuno kernel: [ 101.347616] traps: gnome-shell[2790] trap int3 ip:7efffdf69955 sp:7ffc6beecca0 error:0 in libglib-2.0.so.0.6000.0[7efffdf3+8] Apr 30 16:47:43 mizuno gnome-shell[2790]: Impossible to lock surface front buffer: Function not implemented -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1826025 Title: gnome-shell trap int3 no desktop Status in gdm3 package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking cursor. [ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955 sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8] Restarting gdm3 service results in the same trap. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell] Date: Tue Apr 23 09:56:22 2019 DistUpgraded: 2019-04-22 15:16:02,086 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: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-13-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3703] InstallationDate: Installed on 2012-02-14 (2625 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Supermicro X8DT3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT3 dmi.board.vendor: Supermicro dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890: dmi.product.family: 1234567890 dmi.product.name: X8DT3 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro 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-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Mon Apr 22 20:53:09 2019 xserver.configfile: /home/greg/xorg.conf.new
[Desktop-packages] [Bug 1813716] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_na
** Changed in: mutter 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/1813716 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_native_object Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Disco: New Status in mutter source package in Disco: New Status in gnome-shell source package in Eoan: In Progress Status in mutter source package in Eoan: In Progress Bug description: Tracked upstream in https://gitlab.gnome.org/GNOME/mutter/issues/576 Proposed fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/557 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.2-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/a27089759201dfe884a9070c2d62c50680fb2de4 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/mutter/+bug/1813716/+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 1826025] Re: gnome-shell trap int3 no desktop
apport is enabled. >From /var/log/apport.log.1: ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: called for pid 2699, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: debug: session gdbus call: (false,) ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: happens for shutting down session, ignoring >From dpkg -l | grep rdp: ii libfreerdp-client2-2:amd64 2.0.0~git20190204.1.2693389a+dfsg1-1amd64Free Remote Desktop Protocol library (client library) ii libfreerdp-common1.1.0:amd64 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 amd64Free Remote Desktop Protocol library (common library) ii libfreerdp-plugins-standard:amd64 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 amd64RDP client for Windows Terminal Services (plugins) ii libfreerdp-utils1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 amd64Free Remote Desktop Protocol library (freerdp-utils library) rc libfreerdp1:amd641.0.2-2ubuntu1 amd64RDP client for Windows Terminal Services (library) ii libfreerdp2-2:amd64 2.0.0~git20190204.1.2693389a+dfsg1-1amd64Free Remote Desktop Protocol library (core library) ii remmina-plugin-rdp:amd64 1.3.3+dfsg-2ubuntu1 amd64RDP plugin for Remmina ii xorgxrdp 1:0.2.9-1 amd64Remote Desktop Protocol (RDP) modules for X.org ii xrdp 0.9.9-1 amd64Remote Desktop Protocol (RDP) server -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1826025 Title: gnome-shell trap int3 no desktop Status in gdm3 package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking cursor. [ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955 sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8] Restarting gdm3 service results in the same trap. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell] Date: Tue Apr 23 09:56:22 2019 DistUpgraded: 2019-04-22 15:16:02,086 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: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-13-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3703] InstallationDate: Installed on 2012-02-14 (2625 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Supermicro X8DT3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT3 dmi.board.vendor: Supermicro dmi.board.version: 2.0
[Desktop-packages] [Bug 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827154 Title: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 --- [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1827154] [NEW] gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
Public bug reported: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 --- [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) ** Affects: gnome-control-center Importance: Unknown Status: Unknown ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session ** Attachment added: "BackTrace.txt" https://bugs.launchpad.net/bugs/1827154/+attachment/5260430/+files/BackTrace.txt ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 + + --- + [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #503 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 -- 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/1827154 Title: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 --- [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Since 18.04 is the latest LTS, how does this change get distributed to those of us who rely on the LTS to be upgraded and effective until the next LTS? In other words, how and when does it get integrated into 18.04LTS? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Won't Fix Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom
This crash seems to be fixed in this commit, included in gnome-session 3.30.0: https://github.com/GNOME/gnome-session/commit/3aafcf0f0129e28b5c52f32284f1164a93867ea3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1715365 Title: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display() Status in gnome-session package in Ubuntu: Confirmed Bug description: Possibly: https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a --- bug at login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-session-bin 3.25.90-0ubuntu2 Uname: Linux 4.12.0-041200-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Sep 3 09:34:09 2017 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated InstallationDate: Installed on 2015-04-16 (874 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: () g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gdk_x11_atom_to_xatom_for_display () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, init=, fini=, rtld_fini=, stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291 Title: gnome-session-check-accelerated crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1715365/+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 1779432] Re: [upstream] Libre Writer doesn't do duplex printing
Finally! After only 5 years beingf reported! Code can be easily corrected by copying the duplex-printing code from any other app like Atril, FireFox, Chromium, etc.—they all work. -- 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/1779432 Title: [upstream] Libre Writer doesn't do duplex printing Status in LibreOffice: Unknown Status in Ubuntu MATE: New Status in libreoffice package in Ubuntu: New Bug description: The Libre Writer print settings are set to two side printing, but program only prints single side. Is not HP Linux driver because both FireFox and Chrome print both sides. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: ufsd ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jun 29 22:17:38 2018 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-06-15 (14 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+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 1827110] Re: nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.1.0-1.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1827110 Title: nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.1.0-1.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/n/nvidia-graphics-drivers-340/20190429_130458_3a112@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/n/nvidia-graphics-drivers-340/20190429_125012_3a112@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1827110/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 [ Impact ] - GNOME Shell crashes in st_widget_get_theme_node [ Test Case ] - No clear test case for this, monitoring errors.ubuntu.com is the only feasible solution [ Regression Potential ] Shell actors might have wrong theming. The crash will be converted in error trackable through journalctl --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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/1796606/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
1.8.2-1 from cosmic also has this regression [1556659895.024512] Starting detailed registration state check [1556659895.024533] Skipping detailed registration state check [1556659895.024543] All CDMA registration state checks done [1556659895.024636] Will start keeping track of state for subsystem 'cdma1x' [1556659895.024671] Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabled -> registered) [1556659895.024907] Periodic signal checks enabled [1556659895.024921] Periodic signal check refresh requested [1556659895.024931] loading signal quality... [1556659895.024956] (rfcomm0) device open count is 4 (open) [1556659895.025046] Will start keeping track of state for subsystem 'evdo' [1556659895.025076] Modem is currently registered in a CDMA network (CDMA1x: 'yes', EV-DO: 'no') [1556659895.025092] Simple connect state (6/8): Bearer [1556659895.025104] Creating new bearer... [1556659895.025120] Creating Broadband bearer in broadband modem [1556659895.025620] (rfcomm0) device open count is 5 (open) [1556659895.025679] (rfcomm0) device open count is 4 (close) [1556659895.026094] Simple connect state (7/8): Connect [1556659895.026129] Connecting bearer '/org/freedesktop/ModemManager1/Bearer/0' [1556659895.026155] Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) [1556659895.026456] Launching 3GPP2 connection attempt [1556659895.026485] (rfcomm0) device open count is 5 (open) [1556659895.026495] Connection through a plain serial AT port (rfcomm0) [1556659895.026515] (rfcomm0) device open count is 6 (open) [1556659895.026554] (rfcomm0) device open count is 5 (close) [1556659895.026584] (rfcomm0): --> 'AT+CSS?' [1556659895.049351] (rfcomm0): <-- '?, 26OK' [1556659895.049510] Starting detailed registration state check [1556659895.049527] Skipping detailed registration state check [1556659895.049537] All CDMA registration state checks done [1556659895.049702] Initial CDMA registration checks finished [1556659895.049727] (rfcomm0) device open count is 4 (close) [1556659895.049766] (rfcomm0): --> 'AT+CSQ' [1556659895.070553] (rfcomm0): <-- '22, 99OK' [1556659895.070772] Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (70) [1556659895.070809] EVDO registration: 0 [1556659895.070818] CDMA1x registration: 1 [1556659895.070825] Fallback access tech: 0x0400 [1556659895.070836] Fallback access technology: 0x0400 [1556659895.070867] (rfcomm0) device open count is 3 (close) [1556659895.071116] Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> 1xrtt) [1556659895.071149] Periodic signal quality checks scheduled in 30s [1556659895.071290] (rfcomm0): --> 'ATDT#777' [1556659896.924337] (rfcomm0): <-- 'CONNECT 240' [1556659896.924406] [rfcomm0] Setting flow control: rts-cts [1556659896.924414] (rfcomm0): enabling RTS/CTS flow control [1556659896.924431] (rfcomm0): port now connected [1556659896.924450] Connected bearer '/org/freedesktop/ModemManager1/Bearer/0' [1556659896.924532] Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) [1556659896.924655] Simple connect state (8/8): All done [1556659896.924705] (rfcomm0) device open count is 2 (close) [1556659896.952641] (net/ppp0): adding device at sysfs path: /sys/devices/virtual/net/ppp0 [1556659896.952743] [filter] (net/ppp0) port filtered: virtual device [1556659925.033012] Running registration checks (CDMA1x: 'yes', EV-DO: 'yes') [1556659925.033073] Will skip all QCDM-based registration checks [1556659925.033086] Will skip generic detailed registration check, we don't have Sprint commands [1556659925.033111] loading signal quality... [1556659925.033158] Starting QCDM-based registration checks [1556659925.033169] Skipping all QCDM-based checks and falling back to AT-based checks [1556659925.033210] Starting AT-based registration checks [1556659925.033260] Couldn't refresh signal quality: 'No AT port available to run command' [1556659925.033324] EVDO registration: 0 [1556659925.033346] CDMA1x registration: 1 [1556659925.033375] Fallback access tech: 0x0400 [1556659925.033389] Fallback access technology: 0x0400 [1556659925.033448] No CDMA service found [1556659925.033470] All CDMA registration state checks done [1556659925.033565] Connected bearer not registered in CDMA network [1556659925.033686] Periodic signal quality checks scheduled in 30 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source
[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
i downgraded ModemManager back to 1.6.8-2ubuntu1 and the problem went away, so it is caused by ModemManager. attached are the logs for ModemManager 1.6.8-2ubuntu1 ** Attachment added: "mm.log" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5260385/+files/mm.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1746598] Re: [MIR] libnfs
This MIR request has been abandoned a support point of view. ** Changed in: libnfs (Ubuntu Bionic) Assignee: Eric Desrochers (slashd) => (unassigned) ** Changed in: libnfs (Ubuntu Cosmic) Assignee: Eric Desrochers (slashd) => (unassigned) ** Changed in: libnfs (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: libnfs (Ubuntu Cosmic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnfs in Ubuntu. https://bugs.launchpad.net/bugs/1746598 Title: [MIR] libnfs Status in libnfs package in Ubuntu: Fix Released Status in libnfs source package in Bionic: Won't Fix Status in libnfs source package in Cosmic: Won't Fix Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year ago, but we can't enable it in Ubuntu until libnfs is promoted to main. The Ubuntu bug for this feature to be enabled in gvfs is LP: #1637988 qemu-block-extra could also enable libnfs support. Security No known CVEs. https://security-tracker.debian.org/tracker/source-package/libnfs https://launchpad.net/ubuntu/+source/libnfs/+cve Quality assurance = - Desktop Packages team is subscribed. - dh_auto_test runs but the tests shipped by upstream cant'b be run at build time since they modify the system. - Autopkgtests are added in 3.0.0-1, running upstream's test suite which includes running tests with valgrind, too. https://bugs.launchpad.net/ubuntu/+source/libnfs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnfs https://github.com/sahlberg/libnfs/issues https://autopkgtest.ubuntu.com/packages/libn/libnfs (failing, never passed: see https://bugs.debian.org/921578 ) https://ci.debian.net/packages/libn/libnfs/ (tests aren't run in Debian because they request machine isolation which isn't implemented there yet) Dependencies No universe binary dependencies Standards compliance 3.9.8, debhelper compat 9, dh7 simple rules Maintenance === Actively maintained: https://github.com/sahlberg/libnfs Not team maintained in Debian. https://tracker.debian.org/pkg/libnfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
yparitcher, as this SRU consists of three packages, ModemManager itself and the two libraries, try at first to downgrade only modemmanager to the original. If this solves the problem, it is caused by modemmanager, if not, downgrade one of the libraries, then try to downgrade the other, ... until you could spot one of the three packages having caused your problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1164016] Re: restore type-ahead find
> The Gnome team is extremely resistant to bring back the old intuitive > functionality. > I tried to explain the problems at > https://gitlab.gnome.org/GNOME/nautilus/issues/244 > , as did many others. Trying to reason with the Gnome team is a complete waste of time. That's why Ubuntu should either patch it, or drop Nautilus completely. Why the f*** is this bug still in the "fix released" status? It should either be reopened or a new one created. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1827131] [NEW] Restore type-ahead select (i.e. #1164016)
Public bug reported: It has long been known that #1164016 has regressed, but for some reason nobody yet has changed back the status of the bug from "fix released", so (since I can't do that) I'm opening a new one. Feel free to mark this as duplicate if (and only if) #1164016 is reopened. All the information is there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 30 22:19:55 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1135x824+526+137'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2027 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages xenial ** Changed in: nautilus (Ubuntu) Status: New => Incomplete ** Changed in: nautilus (Ubuntu) Status: Incomplete => Confirmed -- 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/1827131 Title: Restore type-ahead select (i.e. #1164016) Status in nautilus package in Ubuntu: Confirmed Bug description: It has long been known that #1164016 has regressed, but for some reason nobody yet has changed back the status of the bug from "fix released", so (since I can't do that) I'm opening a new one. Feel free to mark this as duplicate if (and only if) #1164016 is reopened. All the information is there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 30 22:19:55 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1135x824+526+137'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2027 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1827131/+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 1827126] [NEW] /usr/lib/udisks2/udisksd:11:ped_geometry_set_start:resize_part:add_part_to_disk:bd_part_create_part:udisks_linux_partition_table_handle_create_partition
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding udisks2. This problem was most recently seen with package version 2.7.6-3ubuntu3, the problem page at https://errors.ubuntu.com/problem/7517813598de87375f0cb88a03bf92e7386d4ee5 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: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1827126 Title: /usr/lib/udisks2/udisksd:11:ped_geometry_set_start:resize_part:add_part_to_disk:bd_part_create_part:udisks_linux_partition_table_handle_create_partition Status in udisks2 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding udisks2. This problem was most recently seen with package version 2.7.6-3ubuntu3, the problem page at https://errors.ubuntu.com/problem/7517813598de87375f0cb88a03bf92e7386d4ee5 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/udisks2/+bug/1827126/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
I would like to report a regression. i have a verizon samsung phone using as a bluetooth CDMA/3G modem. after the upgrade modemmanager disconnects ~30sec after connecting. attached find modem manager --debug logs [1556654159.032559] Running registration checks (CDMA1x: 'yes', EV-DO: 'yes') [1556654159.032629] Will skip all QCDM-based registration checks [1556654159.032649] Will skip generic detailed registration check, we don't have Sprint commands [1556654159.032684] loading signal quality... [1556654159.032748] Starting QCDM-based registration checks [1556654159.032766] Skipping all QCDM-based checks and falling back to AT-based checks [1556654159.032782] Starting AT-based registration checks [1556654159.032841] Couldn't refresh signal quality: 'No AT port available to run command' [1556654159.032887] EVDO registration: 0 [1556654159.032899] CDMA1x registration: 1 [1556654159.032911] Fallback access tech: 0x0400 [1556654159.032927] Fallback access technology: 0x0400 [1556654159.032977] No CDMA service found [1556654159.032991] All CDMA registration state checks done [1556654159.033076] Connected bearer not registered in CDMA network [1556654159.033172] Periodic signal quality checks scheduled in 30s [1556654161.006911] Connection monitoring is unsupported by the device [1556654174.016444] Forcing bearer disconnection, not registered in CDMA network [1556654174.016472] Forcing disconnection of bearer '/org/freedesktop/ModemManager1/Bearer/0' [1556654174.016551] Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> disconnecting) ** Attachment added: "mm.log" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5260379/+files/mm.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
i am very happy to try any fixes helping to try different versions to see where the regression was introduced. thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** Description changed: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 + + [ Impact ] + + - GNOME Shell crashes in st_widget_get_theme_node + + + [ Test Case ] + + - No clear test case for this, monitoring errors.ubuntu.com is the only + feasible solution + + + [ Regression Potential ] + + Shell actors might have wrong theming. + The crash will be converted in error trackable through journalctl --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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/. -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 [ Impact ] - GNOME Shell crashes in st_widget_get_theme_node [ Test Case ] - No clear test case for this, monitoring errors.ubuntu.com is the only feasible solution [ Regression Potential ] Shell actors might have wrong theming. The crash will be converted in error trackable through journalctl --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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/1796606/+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 1827125] [NEW] /usr/bin/onboard:free(): invalid pointer
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding onboard. This problem was most recently seen with package version 1.4.1-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/703b782b156d2bf9296ce8b8723227c6d2eb1863 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: onboard (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic kylin-18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1827125 Title: /usr/bin/onboard:free(): invalid pointer Status in onboard package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding onboard. This problem was most recently seen with package version 1.4.1-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/703b782b156d2bf9296ce8b8723227c6d2eb1863 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/onboard/+bug/1827125/+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 1760569] Update Released
The verification of the Stable Release Update for glib2.0 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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1760569 Title: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved Status in glib2.0 package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in nautilus source package in Bionic: Invalid Bug description: [ Description ] A crasher when using nautilus. No clear reproducer. [ QA ] Under the GNOME MRE, believe all bugs that upstream says are fixed are really fixed without explicitly verifying them. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Make sure nautilus works, and that the error tracker buckets listed below at least don't increase more rapidly (but hopefully tail off with the new version) [ Regression potential ] It's GLib. A regression could break the whole desktop, or any part of it... Our QA should help us have confidence that the update is at least not that bad. [ Original description ] Happens when there's a "rename" to a file to its same value, no known reproducer though. Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AssertionMessage: munmap_chunk(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Mon Apr 2 09:04:45 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-03-31 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid pointer") at malloc.c:5350 munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846 __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117 g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus assert failure: munmap_chunk(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1816547] Update Released
The verification of the Stable Release Update for glib2.0 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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1816547 Title: SRU 2.56.4 to bionic Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Bug description: [ Description ] New upstream bug fix microrelease * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582) * Bug fixes: #1588 Moving a bookmark item to the same URI causes a crash #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56 Plus fix for LP: #1760569 [ QA ] Under the GNOME MRE, believe all bugs that upstream says are fixed are really fixed without explicitly verifying them. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Test various parts of the desktop. - Logging in - Shutting down - Starting a variety of apps and checking that they work + rhythmbox (play a song using gstreamer) + cheese (look at yourself with your webcam using gstreamer) + network-manager + epiphany (web stuff works) Monitor the error tracker for any increases. [ Regression potential ] It's GLib. A regression could break the whole desktop, or any part of it... Our QA should help us have confidence that the update is at least not that bad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 [ Impact ] - GNOME Shell crashes in st_widget_get_theme_node [ Test Case ] - No clear test case for this, monitoring errors.ubuntu.com is the only feasible solution [ Regression Potential ] Shell actors might have wrong theming. The crash will be converted in error trackable through journalctl --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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/1796606/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved
This bug was fixed in the package glib2.0 - 2.56.4-0ubuntu0.18.04.2 --- glib2.0 (2.56.4-0ubuntu0.18.04.2) bionic; urgency=medium * Backport upstream patches to fix GVariant alignment tests d/p/gvariant-test-Also-force-alignment-for-tuple-test-data.patch, d/p/tests-Allocate-gvariant-data-from-the-heap-to-guarantee-a.patch: Cherry-pick. glib2.0 (2.56.4-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1816547) + Various buffer overflow fixes in GMarkup/GVariant/GDBus + Fix "Moving a bookmark item to the same URI causes a crash" (LP: #1760569) * debian/libglib2.0-0.symbols: New symbols -- Iain Lane Fri, 22 Mar 2019 12:17:34 + ** Changed in: glib2.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1760569 Title: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved Status in glib2.0 package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in nautilus source package in Bionic: Invalid Bug description: [ Description ] A crasher when using nautilus. No clear reproducer. [ QA ] Under the GNOME MRE, believe all bugs that upstream says are fixed are really fixed without explicitly verifying them. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Make sure nautilus works, and that the error tracker buckets listed below at least don't increase more rapidly (but hopefully tail off with the new version) [ Regression potential ] It's GLib. A regression could break the whole desktop, or any part of it... Our QA should help us have confidence that the update is at least not that bad. [ Original description ] Happens when there's a "rename" to a file to its same value, no known reproducer though. Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AssertionMessage: munmap_chunk(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Mon Apr 2 09:04:45 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-03-31 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid pointer") at malloc.c:5350 munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846 __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117 g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus assert failure: munmap_chunk(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1816547] Re: SRU 2.56.4 to bionic
This bug was fixed in the package glib2.0 - 2.56.4-0ubuntu0.18.04.2 --- glib2.0 (2.56.4-0ubuntu0.18.04.2) bionic; urgency=medium * Backport upstream patches to fix GVariant alignment tests d/p/gvariant-test-Also-force-alignment-for-tuple-test-data.patch, d/p/tests-Allocate-gvariant-data-from-the-heap-to-guarantee-a.patch: Cherry-pick. glib2.0 (2.56.4-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1816547) + Various buffer overflow fixes in GMarkup/GVariant/GDBus + Fix "Moving a bookmark item to the same URI causes a crash" (LP: #1760569) * debian/libglib2.0-0.symbols: New symbols -- Iain Lane Fri, 22 Mar 2019 12:17:34 + ** Changed in: glib2.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1816547 Title: SRU 2.56.4 to bionic Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Bug description: [ Description ] New upstream bug fix microrelease * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582) * Bug fixes: #1588 Moving a bookmark item to the same URI causes a crash #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56 Plus fix for LP: #1760569 [ QA ] Under the GNOME MRE, believe all bugs that upstream says are fixed are really fixed without explicitly verifying them. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Test various parts of the desktop. - Logging in - Shutting down - Starting a variety of apps and checking that they work + rhythmbox (play a song using gstreamer) + cheese (look at yourself with your webcam using gstreamer) + network-manager + epiphany (web stuff works) Monitor the error tracker for any increases. [ Regression potential ] It's GLib. A regression could break the whole desktop, or any part of it... Our QA should help us have confidence that the update is at least not that bad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1827029] Re: Extended characters in OSK don't get entered
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/366676 -- 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/1827029 Title: Extended characters in OSK don't get entered Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Fix Released Bug description: [Impact] This bug affects any of the "extended characters" clicked on from the long-press popup in the Screen Keyboard. [Test Case] 1. Open GNOME Settings > Universal Access 2. Enable the Screen Keyboard. (Optionally, turn on Always Show Universal Access Menu to make turning the Screen Keyboard on and off easier.) 3. Open Text Editor 4. Click the u button on the Screen Keyboard 5. Long-press the u button on the Screen Keyboard for a few seconds. 6. On the popup, click the ü character. What Happens In Step 4, u is entered in the Text Editor document. Nothing is entered in Step 5. [Regression Potential] The code to be backported only affects OSK. Check that normal OSK keys (e.g. a,b,c,...) normally works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827029/+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 1817020] Re: Touching and dragging an icon on the dock blocks input to other apps
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 -- 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/1817020 Title: Touching and dragging an icon on the dock blocks input to other apps Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Bug description: Steps to reproduce In GNOME Shell, make sure the Ubuntu dock is visible Using a finger drag, for example, a LibreOffice icon up and down the dock and then drop it on Nautilus. Notice that (sometimes?) the icon will continue to float above the dock and that the mouse will keep the clicky-finger icon. Notice that you can still open Activities and launch an application Notice however, that you can't actually interact with the application you have just launched = What I expected to happen = When releasing the drag the icon would land back on the dock and I could continue to use the desktop as usual. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817020/+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 1772811] Re: [SRU] different behaviors for switch display mode between xenial and bionic
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 -- 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/1772811 Title: [SRU] different behaviors for switch display mode between xenial and bionic Status in Mutter: Fix Released Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in mutter source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Status in mutter source package in Disco: Fix Released Bug description: * Impact Need this SUR so that use OEM laptop hotkey won't be uesless. * Test case 1. Install the new mutter and gnome-shell on the target machine. 2. connect an external display. 3. Press either the monitor switch HOT key (each note book have different one), or the generic hot key (Meta-P) 4. Make sure the display mode is switch to next mode, not the first mode. * Regression potential very low, because it's merged upstream and also tested in oem platforms. -- When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1772811/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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-shell/+bug/1796606/+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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
** Merge proposal unlinked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 -- 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/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55
[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
Brian, do you have some link (bug report, ...) to this failure? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
What's going on with the network-manager arm64 autopkgtest failure with the new modem-manager? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)
This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu3 --- gtk+3.0 (3.22.30-1ubuntu3) bionic; urgency=medium [ Sebastien Bacher ] * d/p/Check-for-NULL-priv-popup_window-in-gtk_combo_box_popdown.patch: - Check for NULL priv->popup_window in gtk_combo_box_popdown() (lp: #1816032) [ Andrea Azzarone ] * d/p/restore_filechooser_typeaheadfind.patch: - Disable typeahead if in search mode (LP: #1592177) -- Sebastien Bacher Tue, 02 Apr 2019 17:30:09 +0200 ** Changed in: gtk+3.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1592177 Title: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour) Status in GTK+: Expired Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Released Status in gtk+3.0 source package in Cosmic: Fix Released Status in gtk+3.0 source package in Disco: Fix Released Bug description: * Impact The focus gets removed from the search entry widget in the fileselector while typing which makes it difficult to use * Test case Steps: 1. Open Gedit 2. Choose Open -> Other Documents... to open a GtkFileChooserDialog 3. Press on the search button next to Open 4. Type what you are searching for Expected behaviour: Focus remains in the search input until I finish typing then results come up What happens instead: Searching stops after I enter the first characters because focus is lost from the search input * Regression potential The change is desactivating/reactivating typeahead in the gtk fileselector, check that this feature keeps working as it should (keyboard navigate by typing the first chars of a file/folder, that should move the focus to the first matching item and allows to navigate by hitting enter) I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 that the built-in search functionality is almost impossible to use in the GTK file chooser (though it is the same one that allows you to save files as well as choose them). So if one types something into the search, after they have typed the first letter it will immediately select the top search result meaning one has to re-select the search box, this happens for every letter so searching for a long string becomes very annoying. If one carries on typing once it has selected the top result and unselected the search box it will start searching in the other search which only looks at results. Upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/1572 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk-3-0 3.22.30-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1592177/+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 1816032] Re: gtk_widget_destroy reports error
This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu3 --- gtk+3.0 (3.22.30-1ubuntu3) bionic; urgency=medium [ Sebastien Bacher ] * d/p/Check-for-NULL-priv-popup_window-in-gtk_combo_box_popdown.patch: - Check for NULL priv->popup_window in gtk_combo_box_popdown() (lp: #1816032) [ Andrea Azzarone ] * d/p/restore_filechooser_typeaheadfind.patch: - Disable typeahead if in search mode (LP: #1592177) -- Sebastien Bacher Tue, 02 Apr 2019 17:30:09 +0200 ** Changed in: gtk+3.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Released Bug description: * Impact Buggy warnings are displayed in some cases, which can confuses users/coders * Test case Build and use the small program attached in the comments, it should display no warning * Regression potential The change is a simple null check in the combo widget code, the regression potential is low but make sure combos work in a few softwares just in case -- I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1816032/+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 1547024] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem
Same problem on ux501vw, Ubuntu 18.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1547024 Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm not sure what's happening, my sound works great, there's just a static noise in the background that can get very annoying. Let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.5.0-040500rc4-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zkanda 1519 F pulseaudio CurrentDesktop: MATE Date: Thu Feb 18 21:34:15 2016 InstallationDate: Installed on 2016-02-16 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.204:bd11/12/2015:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1547024/+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 1825497] Re: flash player does not work in chromium
@ruiromo: this is incorrect, only 19.04 and 19.10 are affected at this point, because they have glibc 2.29. Chromium in 18.04 is not affected, I just successfully tested it. Note that you need the pepperflashplugin- nonfree package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1825497 Title: flash player does not work in chromium Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Invalid Bug description: after you allow it to run it doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 73.0.3683.103-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU= modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Fri Apr 19 04:29:19 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2017-04-20 (729 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 1.18 Load-Processes-Running-Percent: 0.4% Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) dmi.bios.date: 02/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4202 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1825497/+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 1827118] [NEW] Boot black screen
Public bug reported: At several times boot stops and each time no boot menu (Grub) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 20:53:28 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21dd] InstallationDate: Installed on 2019-04-29 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 7829A71 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=4f77cbd0-dae8-4ab6-a7bb-2af4093855de ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 7829A71 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn7829A71:pvrThinkPadL420:rvnLENOVO:rn7829A71:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L420 dmi.product.name: 7829A71 dmi.product.version: ThinkPad L420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco 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/1827118 Title: Boot black screen Status in xorg package in Ubuntu: New Bug description: At several times boot stops and each time no boot menu (Grub) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 20:53:28 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21dd] InstallationDate: Installed on 2019-04-29 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 7829A71 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=4f77cbd0-dae8-4ab6-a7bb-2af4093855de ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 7829A71 dmi.board.vendor: LENOVO dmi.board.version: Not Available
[Desktop-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)
This bug was fixed in the package gtk+3.0 - 3.24.4-0ubuntu1.1 --- gtk+3.0 (3.24.4-0ubuntu1.1) cosmic; urgency=medium [ Andrea Azzarone ] * d/p/restore_filechooser_typeaheadfind.patch: - Disable typeahead if in search mode (LP: #1592177) -- Sebastien Bacher Fri, 15 Mar 2019 21:26:23 +0100 ** Changed in: gtk+3.0 (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1592177 Title: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour) Status in GTK+: Expired Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Committed Status in gtk+3.0 source package in Cosmic: Fix Released Status in gtk+3.0 source package in Disco: Fix Released Bug description: * Impact The focus gets removed from the search entry widget in the fileselector while typing which makes it difficult to use * Test case Steps: 1. Open Gedit 2. Choose Open -> Other Documents... to open a GtkFileChooserDialog 3. Press on the search button next to Open 4. Type what you are searching for Expected behaviour: Focus remains in the search input until I finish typing then results come up What happens instead: Searching stops after I enter the first characters because focus is lost from the search input * Regression potential The change is desactivating/reactivating typeahead in the gtk fileselector, check that this feature keeps working as it should (keyboard navigate by typing the first chars of a file/folder, that should move the focus to the first matching item and allows to navigate by hitting enter) I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 that the built-in search functionality is almost impossible to use in the GTK file chooser (though it is the same one that allows you to save files as well as choose them). So if one types something into the search, after they have typed the first letter it will immediately select the top search result meaning one has to re-select the search box, this happens for every letter so searching for a long string becomes very annoying. If one carries on typing once it has selected the top result and unselected the search box it will start searching in the other search which only looks at results. Upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/1572 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk-3-0 3.22.30-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1592177/+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 1809788] Re: bionic - TBT authentication message will be cut from the dialog box
Yeah, disco isn't fixed either here. ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Triaged -- 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/1809788 Title: bionic - TBT authentication message will be cut from the dialog box Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Bug description: When plugging in a Thunderbolt device, under certain conditions, there could be a pop-up window asking for authentication from the user. In the dialog box, the prompt text is truncated. Please refer to attached screen shot for more details. The issue can be found in the gnome-control-center package for bionic: 1:3.28.2-0ubuntu0.18.04.2 1:3.28.1-0ubuntu1 However, the issue is confirmed to be gone in latest such package for Cosmic: 1:3.30.2-1ubuntu0.18.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1809788/+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 1809788] Re: bionic - TBT authentication message will be cut from the dialog box
Ok, this is somewhat theme related. See: https://imgur.com/a/SSsYBfO So adding yaru. ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** No longer affects: yaru-theme (Ubuntu Bionic) ** Changed in: yaru-theme (Ubuntu) Status: New => Triaged ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => High ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Carlo Lobrano (c-lobrano) -- 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/1809788 Title: bionic - TBT authentication message will be cut from the dialog box Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Bug description: When plugging in a Thunderbolt device, under certain conditions, there could be a pop-up window asking for authentication from the user. In the dialog box, the prompt text is truncated. Please refer to attached screen shot for more details. The issue can be found in the gnome-control-center package for bionic: 1:3.28.2-0ubuntu0.18.04.2 1:3.28.1-0ubuntu1 However, the issue is confirmed to be gone in latest such package for Cosmic: 1:3.30.2-1ubuntu0.18.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1809788/+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 1827110] [NEW] nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.1.0-1.1
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/n/nvidia-graphics-drivers-340/20190429_130458_3a112@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/n/nvidia-graphics-drivers-340/20190429_125012_3a112@/log.gz ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1827110 Title: nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.1.0-1.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/n/nvidia-graphics-drivers-340/20190429_130458_3a112@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/n/nvidia-graphics-drivers-340/20190429_125012_3a112@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1827110/+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 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
Still, or again, appearing in 0.7.19
duplicity --version
duplicity 0.7.19
deja-dup --version
deja-dup 37.0
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename: bionic
Traceback (innermost last):
File "/usr/bin/duplicity", line 1581, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1567, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1419, in main
do_backup(action)
File "/usr/bin/duplicity", line 1537, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 577, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 459, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 458, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 347, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
Status in Duplicity:
Fix Committed
Status in duplicity package in Ubuntu:
Fix Released
Bug description:
backup worked under Ubuntu 17.10
It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
my drive is encrypted
this is the error message in the error frame
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 09:55:00 2018
InstallationDate: Installed on 2018-05-01 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1792537] Re: /usr/bin/appstreamcli:5:g_variant_new_parsed_va:g_variant_builder_add_parsed:as_content_rating_to_variant:as_component_to_variant:as_cache_file_save
Hi, I'm trying to go from bionic to cosmic and I'm receiving the appstream error. I've checked my version of appstream and its 0.12.0-3. Is there anything else I can try ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1792537 Title: /usr/bin/appstreamcli:5:g_variant_new_parsed_va:g_variant_builder_add_parsed:as_content_rating_to_variant:as_component_to_variant:as_cache_file_save Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Bionic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding appstream. This problem was most recently seen with package version 0.12.2-2, the problem page at https://errors.ubuntu.com/problem/fca706c9b229ddb2bae3fa59877eee4f98f69366 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/. This crash happens when trying to upgrade a fully up-to-date bionic machine to cosmic. appstreamcli crashes with the following error, thus aborting the upgrade process: E:Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi', E:Sub-process retrened an error code [Impact] * As of today, users upgrading from bionic to cosmic will see the upgrade process abort early on because of this crash. This is most likely caused by malformed appstream metadata, so the issue might go away if that metadata is fixed at some point. In the meantime, this completely prevents bionic→cosmic upgrades. * The fix is upstream (https://github.com/ximion/appstream/commit/734e9da66bf12fcaa94c10465db2dcf8bb2b94cb) and in the cosmic version of appstream [Test Case] 1. On a fresh bionic installation, change bionic to cosmic in sources.list 2. Run apt update This use case happens when the user does a release upgrade. [Regression potential] This patch affects the way appstream metadata is parsed to build a representation in memory. Potential regressions may happen if the parser is fed invalid/malformed metadata with unexpected types. That's actually the cause of the crash itself, so we cannot assume that it won't happen again with differently malformed metadata. There doesn't appear to be specific tests associated to that crash in the upstream commit that fixes it, so there's no guarantee it won't regress in the future. [Other Info] According to errors.ubuntu.com the crash still happens in cosmic with appstream 0.12.2-2, which would imply that the patch does not fix all occurrences of the problem. However according to Laney this data is not always accurate, sometimes crashes which happen around an upgrade are reported against the new version mistakenly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1792537/+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 1827099] Re: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1827099 Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned Status in shared-mime-info package in Ubuntu: New Bug description: Crash at the end of upgrade to 19.04 ProblemType: Package DistroRelease: Ubuntu 19.04 Package: shared-mime-info 1.10-1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue Apr 30 21:07:35 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-10-28 (1280 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.0 SourcePackage: shared-mime-info Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1827099/+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 1827099] [NEW] package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Crash at the end of upgrade to 19.04 ProblemType: Package DistroRelease: Ubuntu 19.04 Package: shared-mime-info 1.10-1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue Apr 30 21:07:35 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-10-28 (1280 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.0 SourcePackage: shared-mime-info Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1827099 Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned Status in shared-mime-info package in Ubuntu: New Bug description: Crash at the end of upgrade to 19.04 ProblemType: Package DistroRelease: Ubuntu 19.04 Package: shared-mime-info 1.10-1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue Apr 30 21:07:35 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-10-28 (1280 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.0 SourcePackage: shared-mime-info Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1827099/+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 823155] Re: [Upstream] Impress Custom Animation Sound Effect not audible in Slide Show
Launchpad has imported 2 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=123836. 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-03-04T12:18:19+00:00 Beluga wrote: 1. Open Impress 2. Select a shape/box 3. Sidebar - Animation - Add: Random Effects 4. Options - Sound (select a sound) 5. Start slideshow or preview Already in 3.3.0 on Win 10 (tested 4.3.0 as well). Bogdan found this issue. Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: d559c28e9e65f3be415ec2e36ee90aa147e65b84 CPU threads: 8; OS: Linux 4.20; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 1 March 2019 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/823155/comments/114 On 2019-03-04T19:51:59+00:00 julien2412 wrote: On pc Debian x86-64 with master sources updated today, I could reproduce this. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/823155/comments/117 ** Changed in: df-libreoffice Status: Unknown => Confirmed ** Changed in: df-libreoffice Importance: Unknown => Low -- 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/823155 Title: [Upstream] Impress Custom Animation Sound Effect not audible in Slide Show Status in LibreOffice: Confirmed Status in OpenOffice: Unknown Status in libreoffice package in Ubuntu: Triaged Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a new Impress document via the Terminal: loimpress --nologo New Impress file -> click the rectangle containing "Click to add text" -> Under Tasks Custom Animation -> button Add... -> Entrance tab highlight Random Effects -> OK button -> right of Property ... button -> Effect tab -> change Sound dropdown apert -> OK button -> Slide Show and it plays the apert sound. 4) What happens instead is no sound is played during the slide show. Original Reporter Comments: I am using Ubuntu 11.04 Natty. I have tested this in Ubuntu 10.10 with OpenOffice.org presentation (Impress), same problem too. All in all I have tried this on 3 different computers. 2 on 11.04 and 1 on 10.10 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 Architecture: i386 Date: Tue Aug 9 16:59:45 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/823155/+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 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1825623 Title: [AppIndicatorSupport-FATAL] unable to update overlay icon Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: After startup or login, An error occurs that just states cancel or report... but does not open a detail dialog Error messages in the syslog: ... Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon ... It seems that the update notifier cannot register its icon in the top bar. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 10:49:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (354 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825623/+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 1826560] Re: [SRU] libreoffice 6.2.3 for disco
** Changed in: libreoffice (Ubuntu Disco) Status: Triaged => In Progress ** Changed in: libreoffice-l10n (Ubuntu Disco) Status: Triaged => In Progress -- 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/1826560 Title: [SRU] libreoffice 6.2.3 for disco Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Disco: In Progress Status in libreoffice-l10n source package in Disco: In Progress Bug description: [Impact] * LibreOffice 6.2.3 is in its third bugfix release of the 6.2 line. Version 6.2.3 is currently in eoan. For a list of fixed bugs compared to 6.2.2 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.2.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.2.3/RC2#List_of_fixed_bugs (that's a total of 92 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 92 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826560/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** Changed in: gnome-shell (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Disco) Importance: Undecided => Medium -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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-shell/+bug/1796606/+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 1826182] Re: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor
** Changed in: mutter (Ubuntu Disco) Status: Triaged => In Progress -- 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/1826182 Title: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor Status in Mutter: Fix Released Status in mutter package in Ubuntu: In Progress Status in mutter source package in Disco: In Progress Status in mutter source package in Eoan: In Progress Bug description: Ubuntu 19.04 DisplayLink properietary driver installed. Log in to GNOME desktop in Wayland mode. Hotplug a DisplayLink USB dock with one monitor connected. What happens: The desktop session shuts down and throws me back into the login screen, where Wayland sessions are no longer available. What I would expect: the new monitor is taken into use and the desktop session continues normally. Installed: libmutter-4-0 3.32.0+git20190410-1ubuntu1 This issue is already fixed upstream: https://gitlab.gnome.org/GNOME/mutter/merge_requests/521 The fix has been released as part of mutter 3.32.1. I would hope the mutter package would be updated to the new upstream point release. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1826182/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I confirm the issue in 19.04. I just upgraded from 16.04. I used to get in fine on eduroam not anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1826944] Re: green bars in ubuntu videos
Hi, I fixed the my problem with this command: sudo apt-get remove gstreamer1.0-vaapi. On Mon, Apr 29, 2019 at 10:25 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Please: > > 1. Attach a screenshot or photo of the problem. > > 2. Tell us which video player apps are affected. > > 3. Try this: > >sudo apt install mpv > >and then use 'mpv VIDEOFILE.mp4'. Does it have the same problem? > > 4. Run: > >vainfo > vainfo.txt > >and send us the resulting file 'vainfo.txt'. > > > ** Package changed: xorg (Ubuntu) => totem (Ubuntu) > > ** Changed in: totem (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1826944 > > Title: > green bars in ubuntu videos > > Status in totem package in Ubuntu: > Incomplete > > Bug description: > When I try to play a .mp4 video in Ubuntu Video, I get a screen with > green bars all over. The problem does not occur when I switch to my > nvidia graphics card. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 > Uname: Linux 5.0.0-13-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Apr 29 19:02:44 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] > Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] > [1043:1590] > InstallationDate: Installed on 2019-04-28 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > MachineType: ASUSTeK COMPUTER INC. GL753VE > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic > root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/16/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: GL753VE.307 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: GL753VE > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ROG > dmi.product.name: GL753VE > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20180925-2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1826944/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1826944 Title: green bars in ubuntu videos Status in totem package in Ubuntu: Incomplete Bug description: When I try to play a .mp4 video in Ubuntu Video, I get a screen with green bars all over. The problem does not occur when I switch to my nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:02:44 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti
