[Desktop-packages] [Bug 989588] Re: update-manager popup is shown on launcher and alt-tab list but window doesn't show up
Having this issue frequently also on trusty. I'm a single-session user, but my user session runs for weeks. 2 monitor setup if that matters. I have to close & manually reopen on nearly every instance. Annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/989588 Title: update-manager popup is shown on launcher and alt-tab list but window doesn't show up Status in compiz package in Ubuntu: Triaged Status in update-manager package in Ubuntu: Triaged Status in compiz source package in Precise: Triaged Status in update-manager source package in Precise: Triaged Bug description: Yesterday I got a "popup" from update-manager that shows on the launcher how many updated packages there are available, but left- clicking the icon didn't show the window. Alt-tabbing didn't help either, so I closed it from the right-click menu and the next time it showed I did get a proper popup window. Today this happened again, so filing a bug now. Steps to reproduce, hastily written: 0. (create another user account) 1. login to my main account 2. lock screen 3. switch user 4. update package lists 5. switch back to main user Update-manager window is shown in Launcher and Alt-Tab, but does not appear when selected, by either means. Closing update-manager from the quicklist, and restarting, makes a visible window, as we've said. Also, starting the upgrade from the quicklist worked, and the in-progress dialog appeared normally. BUT, when the upgrade was done, and should return to the main window, that window was still inaccessible. I don't know if the two-session scenario is the only way this bug shows up, currently. I used to have this problem, under Precise, with only one user session. But I haven't seen that behaviour in a while. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: compiz 1:0.9.7.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,compiztoolbox,imgpng,snap,unitymtgrabhandles,mousepoll,place,resize,regex,wall,move,grid,gnomecompat,session,animation,fade,expo,scale,workarounds,unityshell] CompositorRunning: compiz Date: Fri Apr 27 13:22:22 2012 DistUpgraded: 2012-01-14 13:59:33,902 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2210] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: Intel Corporation SandyBridge Platform PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=921d8d6a-73e4-4693-8a6a-10cbceb5b51c ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to precise on 2012-01-14 (103 days ago) dmi.bios.date: 01/13/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASNBCPT1.86C.0061.P00.1101131110 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: LosLunas CRB dmi.board.vendor: Intel Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASNBCPT1.86C.0061.P00.1101131110:bd01/13/2011:svnIntelCorporation:pnSandyBridgePlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLosLunasCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SandyBridge Platform dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu35 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/989588/+subscriptions -- Mailing list: https:/
[Desktop-packages] [Bug 842194] Re: greeter doesn't start "failed to load session file"
** Tags added: quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/842194 Title: greeter doesn't start "failed to load session file" Status in “lightdm” package in Ubuntu: Triaged Bug description: As of today, lightdm on oneiric doesn't show a login screen. I have verified the greeters are installed so this is different to bug 816646. The most likely lines in the log seem to be Failed to load session file /usr/share/xgreeters/.desktop: No such file or directory Failed to start greeter Stopping display I'm just left at a text screen with various stair-stepped log messages. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.3-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 Date: Tue Sep 6 08:32:54 2011 EcryptfsInUse: Yes ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/zsh SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-08-23 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/842194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 842194] Re: greeter doesn't start "failed to load session file"
Same issue here with on upgraded quantal from precise lubuntu-core install. Suddenly stopped working. Reinstall of lightdm-gtk-greeter or webkit-greeter does not help. I resorted myself into installing gdm as an addon replacement for lightdm as I was unable to spot root source of this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/842194 Title: greeter doesn't start "failed to load session file" Status in “lightdm” package in Ubuntu: Triaged Bug description: As of today, lightdm on oneiric doesn't show a login screen. I have verified the greeters are installed so this is different to bug 816646. The most likely lines in the log seem to be Failed to load session file /usr/share/xgreeters/.desktop: No such file or directory Failed to start greeter Stopping display I'm just left at a text screen with various stair-stepped log messages. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.3-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 Date: Tue Sep 6 08:32:54 2011 EcryptfsInUse: Yes ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/zsh SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-08-23 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/842194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 947632] Re: gwibber crashed with SIGSEGV in g_bookmark_file_init()
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/947632 Title: gwibber crashed with SIGSEGV in g_bookmark_file_init() Status in “gwibber” package in Ubuntu: New Bug description: After logon I immediately called the gwibber app using the notification tray menu. Gwibber opened successfully and showed new tweets. At some point without no user interaction gwibber sigsev'd maybe due to the gwibber daemon starting to poll for new tweets parallely? ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gwibber 3.3.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic i686 NonfreeKernelModules: fglrx ApportVersion: 1.94-0ubuntu1 Architecture: i386 Date: Tue Mar 6 01:33:25 2012 ExecutablePath: /usr/bin/gwibber ProcCmdline: gwibber -s messages SegvAnalysis: Segfault happened at: 0x94ccec : lock bts %ecx,(%eax) PC (0x0094ccec) ok source "%ecx" ok destination "(%eax)" (0x0010) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gwibber StacktraceTop: g_bit_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_variant_n_children () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_variant_iter_init () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libgwibber.so.2 Title: gwibber crashed with SIGSEGV in g_bit_lock() UpgradeStatus: Upgraded to precise on 2012-03-02 (3 days ago) UserGroups: adm admin audio cdrom floppy fuse kvm lpadmin netdev plugdev tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/947632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 559894] Re: German spellchecking does not work
As discussed in gnome-bugs #86 this is not a problem not in Empathy,
but either in the spell checking library enchant or the dictionary
provided with Ubuntu:
The same effect appears i.e in gedit and traces down as follows:
If you select "Deutsch" as language option (only available option in Empathy)
it fails. This equals to locale "de". If you choose "Deutsch (Deutschland)"
("de-DE") spell checking works. In Empathy you have no option to choose "de-DE"
as workaround.
Traces down to the following test:
~/dev$ enchant -d de-DE test.txt
~/dev$ enchant -d de test.txt
error: line 1: missing or bad word count in the dic file
Hash Manager Error : 4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/559894
Title:
German spellchecking does not work
Status in Chat app, and Telepathy user interface:
New
Status in “empathy” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: empathy
I activated both "German" and "English" in the spell checker
configuration dialog but every non-english word is underlined in red.
Ubuntu says the language support is fully installed.
I'm using
Description: Ubuntu lucid (development branch)
Release: 10.04
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Sat Apr 10 11:17:05 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=de_DE.utf8
SourcePackage: empathy
To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/559894/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 559894] Re: German spellchecking does not work
New upstream bug in enchant http://bugzilla.abisource.com/show_bug.cgi?id=13252 ** Bug watch added: AbiSource bug tracker #13252 http://bugzilla.abisource.com/show_bug.cgi?id=13252 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/559894 Title: German spellchecking does not work Status in Chat app, and Telepathy user interface: New Status in “empathy” package in Ubuntu: Confirmed Bug description: Binary package hint: empathy I activated both "German" and "English" in the spell checker configuration dialog but every non-english word is underlined in red. Ubuntu says the language support is fully installed. I'm using Description: Ubuntu lucid (development branch) Release: 10.04 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: empathy 2.30.0.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 Architecture: amd64 Date: Sat Apr 10 11:17:05 2010 EcryptfsInUse: Yes ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=de_DE.utf8 SourcePackage: empathy To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/559894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 892022] Re: Errors in german spell-checker
*** This bug is a duplicate of bug 559894 *** https://bugs.launchpad.net/bugs/559894 I share the reportes opinion, that it doesn't necessarily seem to be a duplicate of of bug #559894. @Michael: Can you check using a textfile with some german text and the commands as described in https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/559894/comments/24 that you problem is _not_ related to the locale "de" vs. "de-DE". If you are able to reproduce your problem with enchant itself, it would probably help if you open a separate bug in the enchant Issue tracker for your issue and link to there. Thanks & Grüße! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/892022 Title: Errors in german spell-checker Status in “empathy” package in Ubuntu: Invalid Bug description: Spell checking works (unlike #559894), but makes some mistakes. They seem to relate mostly to the letter ‘ß’, possibly introduced wrongly while trying to adapt to the spelling reform a few years back. In particular, the following words are underlined: ==> Maß Spaß heißt Kloß Fuß They are all quite correct. I’m sure there are dozens more. It is not a problem with ‘ß’ in general, as ‘weiß’ is correctly identified as spelled correctly. Sorry for the repetitiveness. PS: This is most certainly not an empathy bug, but I don’t know which package is responsible for spell checking here. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Nov 18 13:15:12 2011 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928) ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/892022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 559894] Re: German spellchecking does not work
Thanks Muhammad. I provided a full description of the bug and its reproduction based on the input provided here esp. by Thomas. The bug is also reproduceable in the newer Empathy 3.3.1-0ubuntu2~ppa11.10+1 availble in the telepathy PPA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/559894 Title: German spellchecking does not work Status in Chat app, and Telepathy user interface: New Status in “empathy” package in Ubuntu: Confirmed Bug description: Binary package hint: empathy I activated both "German" and "English" in the spell checker configuration dialog but every non-english word is underlined in red. Ubuntu says the language support is fully installed. I'm using Description: Ubuntu lucid (development branch) Release: 10.04 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: empathy 2.30.0.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 Architecture: amd64 Date: Sat Apr 10 11:17:05 2010 EcryptfsInUse: Yes ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=de_DE.utf8 SourcePackage: empathy To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/559894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874973] [NEW] New, never-ending chromium.launcher process on every chromium start since [Focal 20.04/Snap] due to check_current_symlink()
Public bug reported: Since my upgrade from 19.10 to 20.04 on every start a _new_ /snap/chromium/[digit]/bin/chromium.launcher instance is launched and never-ending. It spawns a "sleep 60" child process. Five time starting (and stopping!) chromium = 5 processes 2823981 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832707 ?S 0:00 | \_ sleep 60 2824647 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831803 ?S 0:00 | \_ sleep 60 2825134 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831953 ?S 0:00 | \_ sleep 60 2825521 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832057 ?S 0:00 | \_ sleep 60 2832767 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832771 ?S 0:00 \_ sleep 60 The sleep 60 clearly indicates a problem in the check_current_symlink() function. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: focal packaging ** Description changed: Since my upgrade from 19.10 to 20.04 on every start a _new_ /snap/chromium/[digit]/bin/chromium.launcher instance is launched and never-ending. It spawns a "sleep 60" child process. - Five time starting chromium = 5 processes + Five time starting (and stopping!) chromium = 5 processes 2823981 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832707 ?S 0:00 | \_ sleep 60 2824647 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831803 ?S 0:00 | \_ sleep 60 2825134 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831953 ?S 0:00 | \_ sleep 60 2825521 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832057 ?S 0:00 | \_ sleep 60 2832767 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832771 ?S 0:00 \_ sleep 60 The sleep 60 clearly indicates a problem in the check_current_symlink() function. -- 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/1874973 Title: New, never-ending chromium.launcher process on every chromium start since [Focal 20.04/Snap] due to check_current_symlink() Status in chromium-browser package in Ubuntu: New Bug description: Since my upgrade from 19.10 to 20.04 on every start a _new_ /snap/chromium/[digit]/bin/chromium.launcher instance is launched and never-ending. It spawns a "sleep 60" child process. Five time starting (and stopping!) chromium = 5 processes 2823981 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832707 ?S 0:00 | \_ sleep 60 2824647 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831803 ?S 0:00 | \_ sleep 60 2825134 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831953 ?S 0:00 | \_ sleep 60 2825521 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832057 ?S 0:00 | \_ sleep 60 2832767 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832771 ?S 0:00 \_ sleep 60 The sleep 60 clearly indicates a problem in the check_current_symlink() function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
This feature caused me leaking processes. See Bug: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874973 -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Committed Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874973] Re: New, never-ending chromium.launcher process on every chromium start since [Focal 20.04/Snap] due to check_current_symlink()
Obviously caused by: https://launchpad.net/bugs/1864901 -- 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/1874973 Title: New, never-ending chromium.launcher process on every chromium start since [Focal 20.04/Snap] due to check_current_symlink() Status in chromium-browser package in Ubuntu: New Bug description: Since my upgrade from 19.10 to 20.04 on every start a _new_ /snap/chromium/[digit]/bin/chromium.launcher instance is launched and never-ending. It spawns a "sleep 60" child process. Five time starting (and stopping!) chromium = 5 processes 2823981 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832707 ?S 0:00 | \_ sleep 60 2824647 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831803 ?S 0:00 | \_ sleep 60 2825134 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831953 ?S 0:00 | \_ sleep 60 2825521 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832057 ?S 0:00 | \_ sleep 60 2832767 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832771 ?S 0:00 \_ sleep 60 The sleep 60 clearly indicates a problem in the check_current_symlink() function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from
@vanvugt Seeing this VERY regularly in cosmic, too. Just came back here to re-check the status of this long-term annoying issue. The fact is, that gnome shell provides me a VERY poor UX experience: Logged out for the session more than 10mins? Type your password and go get take a coffee, because it literally takes 1-2 minutes until the session finally crashes and restarts. Before my PC it literally unusable. Sometimes I also switch to the login screen and re-login into my running session to somehow provoke the crash to get it usable. Ah – and by the way: On some occassions lockscreen does not work and expose the clickable (!) left sidebar. In this case I only can unlock via the login-screen way to crash the session. Also commonly in normal operation the left sidebar looks strangely sized. Then I need to type "r" to restart the shell to resume normal operation. Feels really like an old, nearly dying device … -- 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/1748450 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in mutter source package in Bionic: Fix Released Bug description: [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive after Xwayland has reset itself. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence the Xwayland bugs are irrelevant. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. Just don't mark them as duplicates of each other because they are all still collecting duplicates of their own. - *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions --
[Desktop-packages] [Bug 1773308] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Saw this new stacktrace at g_cancellable_make_pollfd() right now, too. For me this occurred while I was hammering quickly in the lockscreen until it chocked, locked and finally crashed. -- 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/1773308 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Crash when I log in after resume from suspend. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri May 25 08:02:52 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-07-15 (1409 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_cancellable_make_pollfd () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_condition_timed_wait () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_input_stream_read () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to cosmic on 2018-03-24 (61 days ago) UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1618839] Re: Regression: WiFi connection reconnects, but dead, after waking from standby
Same issue here after upgrading from xenial 16.04 to yakkety 16.10: After standby I can ping valid IP addresses, but DNS fails. Restarting the network manager via ` sudo /etc/init.d/network-manager restart` does mend the situation. In this SO post https://askubuntu.com/q/837575/94728 people report the same issue. A answer proposes to disable dnsmasq in network manager by commenting out `dns=dnsmasq` in `/etc/NetworkManager/NetworkManager.conf`as workaround. -- 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/1618839 Title: Regression: WiFi connection reconnects, but dead, after waking from standby Status in network-manager package in Ubuntu: Confirmed Bug description: Bug introduced somewhere between Ubuntu 14.04.3 and 16.04.1 If my Thinkpad T420s awakes from standby, very often the last connected WiFi network is reconnected immediately, but the connection is dysfunctional. ifconfig shows a valid connection with an IPv4 address assigned for the wlp3s0 interface. But there is no traffic, no success on DNS queries on the connection. If I reconnect by clicking the connection in the nm-applet menu, all is fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1618839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1618839] Re: Regression: WiFi connection reconnects, but dead, after waking from standby
** Tags added: regression-update yakkety -- 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/1618839 Title: Regression: WiFi connection reconnects, but dead, after waking from standby Status in network-manager package in Ubuntu: Confirmed Bug description: Bug introduced somewhere between Ubuntu 14.04.3 and 16.04.1 If my Thinkpad T420s awakes from standby, very often the last connected WiFi network is reconnected immediately, but the connection is dysfunctional. ifconfig shows a valid connection with an IPv4 address assigned for the wlp3s0 interface. But there is no traffic, no success on DNS queries on the connection. If I reconnect by clicking the connection in the nm-applet menu, all is fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1618839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351772] Re: "disable touchpad while typing" doesn't work
The quickest one-time workaround is to execute pkill syndaemon ; syndaemon -i 1 -KRd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1351772 Title: "disable touchpad while typing" doesn't work Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: When selecting "disable while typing" under the touchpad section of the "Mouse & Touchpad" preferences, nothing changes, the touchpad stays active while typing. I can rapidly type multiple characters with my left hand and continue to move the cursor with the touchpad with my right hand. I can see from my processlist that syndaemon is running with the following options: 2185 ?S 1:31 | \_ syndaemon -i 1.0 -t -K -R First, the -t option isn't what's expected with this setting, it should disable the touchpad entirely. Also, it doesn't seem to even do that correctly, as I can definitely click the touchpad while typing as well as moving the cursor. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 Uname: Linux 3.14.0-997-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 2 17:20:22 2014 InstallationDate: Installed on 2014-04-22 (102 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1351772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783795] [NEW] After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, …
Public bug reported: I upgraded from xenial to bionic and now experience issues with illegible, distorted textfields / textareas or scrollareas in a set of specific applications. For example: * The change log field on prompting for security updated or the list of software sources in the update-manager application * The textfield for entering the equations in gnome-calculator I'm not having any problems i.e. with Firefox et. al. I'm using a NVIDIA 750GTX with the officially bundled nvidia-driver-390. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 26 17:30:41 2018 DistUpgraded: 2018-07-22 13:27:24,064 ERROR Cache can not be locked (E:Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource ist zur Zeit nicht verfügbar), E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-29-generic, x86_64: installed nvidia, 390.48, 4.15.0-29-generic, x86_64: installed spl, 0.7.5, 4.15.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] InstallationDate: Installed on 2014-07-06 (1481 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=ZFS=rpool/ROOT ro boot=zfs SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-07-22 (4 days ago) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd03/08/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu ** Attachment added: "Screenshot distorted gnome-calculator" https://bugs.launchpad.net/bugs/1783795/+attachment/5168176/+files/corrupted-calc.png -- 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/1783795 Title: After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, … Status in xorg package in Ubuntu: New Bug description: I upgraded from xenial to bionic and now experience issues with illegible, distorted textfields / textareas or scrollareas in a set of specific applications. For example: * The change log field on prompting for security updated or the list of software sources in the update-manager application * The text
[Desktop-packages] [Bug 1783795] Re: After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, …
** Attachment added: "Corrupted update-mamager screen" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1783795/+attachment/5168198/+files/corrupted-update-manager.png ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1783795/+attachment/5168181/+files/DpkgLog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1783795/+attachment/5168191/+files/UdevDb.txt ** Attachment removed: "LightdmGreeterLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1783795/+attachment/5168182/+files/LightdmGreeterLogOld.txt -- 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/1783795 Title: After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, … Status in xorg package in Ubuntu: New Bug description: I upgraded from xenial to bionic and now experience issues with illegible, distorted textfields / textareas or scrollareas in a set of specific applications. For example: * The change log field on prompting for security updated or the list of software sources in the update-manager application * The textfield for entering the equations in gnome-calculator I'm not having any problems i.e. with Firefox et. al. I'm using a NVIDIA 750GTX with the officially bundled nvidia- driver-390. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 26 17:30:41 2018 DistUpgraded: 2018-07-22 13:27:24,064 ERROR Cache can not be locked (E:Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource ist zur Zeit nicht verfügbar), E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-29-generic, x86_64: installed nvidia, 390.48, 4.15.0-29-generic, x86_64: installed spl, 0.7.5, 4.15.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] InstallationDate: Installed on 2014-07-06 (1481 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=ZFS=rpool/ROOT ro boot=zfs SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-07-22 (4 days ago) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd03/08/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xs
