[Desktop-packages] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
@sbeattie I tested the package you built for 22.04 and it fixes the problem for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xwayland package in Ubuntu: Triaged Bug description: I just upgraded xserver-xorg-core and xserver-common to 2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate EAP (downloaded from JerBrains website) Xorg server crashes with segfault: X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 #0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr 4 20:28:35 UTC x86_64 Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 6 15:28:18 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" malloc(): unaligned tcache chunk detected (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc] (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7ec01c429d90] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7ec01c429e40] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605] (EE) (EE) Fatal server error: (EE) Caught signal 6 (Aborted). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like security backports were done incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2060354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
@sbeattie It's broken in mantic too. In xwayland, the window dies. in xorg, the session crashes, badly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: I just upgraded xserver-xorg-core and xserver-common to 2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate EAP (downloaded from JerBrains website) Xorg server crashes with segfault: X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 #0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr 4 20:28:35 UTC x86_64 Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 6 15:28:18 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" malloc(): unaligned tcache chunk detected (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc] (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7ec01c429d90] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7ec01c429e40] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605] (EE) (EE) Fatal server error: (EE) Caught signal 6 (Aborted). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like security backports were done incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2060354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
Yeah, for me it crashed 100% of the time with no changes, and removing a configuration file (which among other things removed my non-default preference for grayscale antialias) completely stopped the crashing. This is in a kvm/qemu VM. So from my perspective, and from a few others users, it looks like the cause and a good workaround. But other people in the set of JetBrains tickets report intermittent, unpredictable crashing that doesn't benefit from such a settings change. I think think upstream is talking about race conditions. So far in the bug report (the Ubuntu one) I don't understand what the proposed course of action is. I think this is the upstream bug report: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659 ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1659 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c Status in xorg-server package in Ubuntu: Confirmed Bug description: I just upgraded xserver-xorg-core and xserver-common to 2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate EAP (downloaded from JerBrains website) Xorg server crashes with segfault: X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 #0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr 4 20:28:35 UTC x86_64 Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 6 15:28:18 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" malloc(): unaligned tcache chunk detected (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc] (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7ec01c429d90] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7ec01c429e40] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605] (EE) (EE) Fatal server error: (EE) Caught signal 6 (Aborted). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like security backports were done incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
for what it's worth, JetBrains bug reports find that the problem is triggered by requesting grayscale anti-aliasing. https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c Status in xorg-server package in Ubuntu: Confirmed Bug description: I just upgraded xserver-xorg-core and xserver-common to 2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate EAP (downloaded from JerBrains website) Xorg server crashes with segfault: X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 #0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr 4 20:28:35 UTC x86_64 Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 6 15:28:18 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" malloc(): unaligned tcache chunk detected (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc] (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7ec01c429d90] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7ec01c429e40] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605] (EE) (EE) Fatal server error: (EE) Caught signal 6 (Aborted). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like security backports were done incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
I use the wayland session. I sort of have this bug. The screens do power off, but then the backlights resume. It is still a blank screen -- 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/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://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 2045820] Re: firefox snap .desktop missing StartupWMClass
Where is the source code for the snap packaging for firefox? How can patches be submitted? On Fri, 8 Dec 2023 at 01:10, Maximiliano Bertacchini < 2045...@bugs.launchpad.net> wrote: > I can confirm adding `StartupWMClass=firefox-beta` in the .desktop file > fixes the firefox snap icon in the KDE/Plasma task manager. Thanks! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2045820 > > Title: > firefox snap .desktop missing StartupWMClass > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions > > -- Tim Richardson -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2045820 Title: firefox snap .desktop missing StartupWMClass Status in firefox package in Ubuntu: Confirmed Bug description: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser (installed with snap) does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this line to the snap .destkop file, near the top, fixed it: StartupWMClass=firefox-beta Therefore my suggestion is that the .desktop file have a channel- dependent StartupWMClass value set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045820] Re: firefox snap .desktop missing StartupWMClass
screenshot 2, chatgpt suggestion which contained the fix ** Attachment added: "firefox_bug_2.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+attachment/5726921/+files/firefox_bug_2.png ** Description changed: - I have the mozilla stable version installed using the mozilla binary - method, and snap for the beta channel. The icon is broken, both in the - menu entry and in the panel. That is, there is no icon in menu, and the - generic cog icon in the panel. + this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- + firefox-desktop-file-missing-startupwmclass/37400 + + + I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser does not show a dot, even though I have two windows from it open. image - image Fix? From chatgpt help, I see this: image - Add this this line to the .destkop file, near the top, fixed it: StartupWMClass=firefox-beta -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2045820 Title: firefox snap .desktop missing StartupWMClass Status in firefox package in Ubuntu: New Bug description: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser (installed with snap) does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this line to the snap .destkop file, near the top, fixed it: StartupWMClass=firefox-beta Therefore my suggestion is that the .desktop file have a channel- dependent StartupWMClass value set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045820] Re: firefox snap .desktop missing StartupWMClass
screen shot of icon problem ** Attachment added: "firefox_bug_0.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+attachment/5726922/+files/firefox_bug_0.png ** Description changed: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 - - I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. + I have the mozilla stable version installed using the mozilla binary + method, and snap for the beta channel. The icon is broken, both in the + menu entry and in the panel. That is, there is no icon in menu, and the + generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser does not show a dot, even though I have two windows from it open. - image + image: see attachment firefox_bug_0.png - image + image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: - image + image: see attachment firefox_bug_3.png Add this this line to the .destkop file, near the top, fixed it: StartupWMClass=firefox-beta ** Description changed: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary - method, and snap for the beta channel. The icon is broken, both in the - menu entry and in the panel. That is, there is no icon in menu, and the - generic cog icon in the panel. + method, and snap for the beta channel. The snap icon is broken, both in + the menu entry and in the panel. That is, there is no icon in menu, and + the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this this line to the .destkop file, near the top, fixed it: StartupWMClass=firefox-beta ** Description changed: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context
[Desktop-packages] [Bug 2045820] [NEW] firefox snap .desktop missing StartupWMClass
Public bug reported: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser (installed with snap) does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? >From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this line to the snap .destkop file, near the top, fixed it: StartupWMClass=firefox-beta Therefore my suggestion is that the .desktop file have a channel- dependent StartupWMClass value set. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot 1" https://bugs.launchpad.net/bugs/2045820/+attachment/5726920/+files/firefox_bug_1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2045820 Title: firefox snap .desktop missing StartupWMClass Status in firefox package in Ubuntu: New Bug description: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser (installed with snap) does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this line to the snap .destkop file, near the top, fixed it: StartupWMClass=firefox-beta Therefore my suggestion is that the .desktop file have a channel- dependent StartupWMClass value set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995406] Re: User not added to group sambashare: "You do not have permission to create a usershare."
This is happening in lunar beta 23.04,. I install nautilus-share. Turned on sharing in Gnome preference (both options) When attempting to share a folder: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Permission denied You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/995406 Title: User not added to group sambashare: "You do not have permission to create a usershare." Status in nautilus-share package in Ubuntu: Confirmed Bug description: I tried to share a folder and was prompted to install samba, which I accepted. I did not install pam-smbpass as I don't need it. I was prompted to log out and in again, which I did. Now I get this when creating a share: --- 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Permission denied You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share. --- It looks like the user was not added to the group sambashare at all (which script is supposed to do this? Where is the log file?). Manually running # sudo usermod -a -G sambashare jakob fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus-share 0.7.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun May 6 11:37:08 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) SourcePackage: nautilus-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/995406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
see also https://bugzilla.redhat.com/show_bug.cgi?id=2072070 for lengthy discussion. ** Bug watch added: Red Hat Bugzilla #2072070 https://bugzilla.redhat.com/show_bug.cgi?id=2072070 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
Ubuntu 22.04. I still have this problem intel-media-va-driver 22.3.0 tigerlake laptop $ apt-cache show intel-media-va-driver Package: intel-media-va-driver Architecture: amd64 Version: 22.3.0+dfsg1-1 tim@ochre:~$ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit tim@ochre:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
[Desktop-packages] [Bug 1952107] Re: Google Contacts API Deprecated
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Committed Status in evolution-data-server source package in Impish: Fix Committed Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952107] Re: Google Contacts API Deprecated
(... Ubuntu 21.10) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Committed Status in evolution-data-server source package in Impish: Fix Committed Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952107] Re: Google Contacts API Deprecated
I used proposed-updates today to get the latest evolution, and contact sync works again. So 3.40.4-1ubuntu2 works. (amd64 arch) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Committed Status in evolution-data-server source package in Impish: Fix Committed Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927767] Re: All apps crashed in my X11 session, then terminal console crashed, reboot failed
No data available from (1) or (2) and the problem has not reoccurred. I have commented line 23 of crashdb.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1927767 Title: All apps crashed in my X11 session, then terminal console crashed, reboot failed Status in xorg-server package in Ubuntu: Incomplete Bug description: The reboot failed with many services that could not stop. I think there may have been a crash in the network stack. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim4093 F pulseaudio /dev/snd/controlC2: tim4093 F pulseaudio /dev/snd/controlC0: tim4093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 8 03:07:12 2021 InstallationDate: Installed on 2020-11-22 (166 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax mitigations=off crashkernel=192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: Upgraded to hirsute on 2021-04-23 (14 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33g dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITEWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITEWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1927767/+subscriptions -- Mailing list: https://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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Google has not removed API access. They have stopped a google key from working. It works fine, as far as I can tell. But you need to get your own key. The well known PPA with VAAPI, https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev, has always worked like this. I use Fedora on another machine, and with my own keys, Chromium works exactly as before. On Sat, 6 Mar 2021 at 03:00, Michel-Ekimia <1816...@bugs.launchpad.net> wrote: > Sorry to use this bug report as a forum but IMO it is useless to spend > more time on chromium. > > Ubuntu & users should define a Blink-based open source browser like > Brave that could be supported nicely upstream unlike whats google is > doing by removing sync API access with google services > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816497 > > Title: > [snap] vaapi chromium no video hardware decoding > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions > -- Tim Richardson -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound
I just installed Ubuntu 20.10 on a machine that was running Pop!os 20.04 and 20.10 (a fairly new AMD Ryzen desktop system, different to the machine I had the problem on earlier, which was a laptop). Not 24 hours later, this problem again. I thought there was something wrong with Team app ('bloody microsoft') but then my next meeting in Google Meet had the same problem. And YouTube. Then I remembered this. This time I just removed speech-dispatcher. Maybe it is not installed by default on pop, not sure. An ugly papercut. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: So, a brand new computer running Ubuntu 16.04.3 LTS. In hardinfo summary, my audio adapters are • HDA-Intel - HDA Intel HDMI • HDA-Intel - HDA Intel PCH • HDA-Intel - HDA NVidia In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Memory 16kb (non-prefetchable), snd_hda_intel As soon as I load a website in Firefox that utilizes speech-dispatcher (fimfiction.net) all sounds get distorted, whether I click a paragraph for TTS reading or not. The problem seems to go away if I don't use the site after a while. When I close down Firefox the problem still lingers a bit, but maybe not as long. One thing I did which seemed faster was close down everything, then load what I wanted to listen to (Skype, Discord), and if it still persisted I would go into "Sound Settings" and after a few blinks in that window the sound is normal again. While the site is open, according to "Sound Settings" (from the speaker icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies of this package. Muting them did not help the problem, but moving one of them, and a very specific one, from the "Built-in Audio Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be a workaround. Just so you know, I do not use the HDMI cable for sound, but instead use the "headphones" jack. If you need any more details, I'll try to provide them. /Edward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound
My sound control panel reports three speech-dispatcher entries in Volume Levels. I don't know why. My session is about two days old and I haven't had any instance of distortion, so the workaround referred to in my previous comment, a config change, may be a good idea for package maintainers to implement. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: So, a brand new computer running Ubuntu 16.04.3 LTS. In hardinfo summary, my audio adapters are • HDA-Intel - HDA Intel HDMI • HDA-Intel - HDA Intel PCH • HDA-Intel - HDA NVidia In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Memory 16kb (non-prefetchable), snd_hda_intel As soon as I load a website in Firefox that utilizes speech-dispatcher (fimfiction.net) all sounds get distorted, whether I click a paragraph for TTS reading or not. The problem seems to go away if I don't use the site after a while. When I close down Firefox the problem still lingers a bit, but maybe not as long. One thing I did which seemed faster was close down everything, then load what I wanted to listen to (Skype, Discord), and if it still persisted I would go into "Sound Settings" and after a few blinks in that window the sound is normal again. While the site is open, according to "Sound Settings" (from the speaker icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies of this package. Muting them did not help the problem, but moving one of them, and a very specific one, from the "Built-in Audio Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be a workaround. Just so you know, I do not use the HDMI cable for sound, but instead use the "headphones" jack. If you need any more details, I'll try to provide them. /Edward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
If you want to test this, force YouTube to serve H264, which your card supports judging by the vainfo results. A 4k 60fps YouTube video won't be in a codec your hardware can handle, I guess. There are 'h264ify' extensions for Chromium. -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound
I will try this workaround/config change: https://github.com/brailcom/speechd/issues/198#issuecomment-619605269 ** Bug watch added: github.com/brailcom/speechd/issues #198 https://github.com/brailcom/speechd/issues/198 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: So, a brand new computer running Ubuntu 16.04.3 LTS. In hardinfo summary, my audio adapters are • HDA-Intel - HDA Intel HDMI • HDA-Intel - HDA Intel PCH • HDA-Intel - HDA NVidia In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Memory 16kb (non-prefetchable), snd_hda_intel As soon as I load a website in Firefox that utilizes speech-dispatcher (fimfiction.net) all sounds get distorted, whether I click a paragraph for TTS reading or not. The problem seems to go away if I don't use the site after a while. When I close down Firefox the problem still lingers a bit, but maybe not as long. One thing I did which seemed faster was close down everything, then load what I wanted to listen to (Skype, Discord), and if it still persisted I would go into "Sound Settings" and after a few blinks in that window the sound is normal again. While the site is open, according to "Sound Settings" (from the speaker icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies of this package. Muting them did not help the problem, but moving one of them, and a very specific one, from the "Built-in Audio Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be a workaround. Just so you know, I do not use the HDMI cable for sound, but instead use the "headphones" jack. If you need any more details, I'll try to provide them. /Edward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound
This bug started affecting me in the past week although I've been on 20.04 since launch. I have removed the packages including orca. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: So, a brand new computer running Ubuntu 16.04.3 LTS. In hardinfo summary, my audio adapters are • HDA-Intel - HDA Intel HDMI • HDA-Intel - HDA Intel PCH • HDA-Intel - HDA NVidia In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Memory 16kb (non-prefetchable), snd_hda_intel As soon as I load a website in Firefox that utilizes speech-dispatcher (fimfiction.net) all sounds get distorted, whether I click a paragraph for TTS reading or not. The problem seems to go away if I don't use the site after a while. When I close down Firefox the problem still lingers a bit, but maybe not as long. One thing I did which seemed faster was close down everything, then load what I wanted to listen to (Skype, Discord), and if it still persisted I would go into "Sound Settings" and after a few blinks in that window the sound is normal again. While the site is open, according to "Sound Settings" (from the speaker icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies of this package. Muting them did not help the problem, but moving one of them, and a very specific one, from the "Built-in Audio Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be a workaround. Just so you know, I do not use the HDMI cable for sound, but instead use the "headphones" jack. If you need any more details, I'll try to provide them. /Edward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
@vasyl: thanks, good comment. It pays to RTFM, apparently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox
For me in 20.04, bug is definitely still present. I have earlyoom active, and 32 gb a few seconds of "freeze" (which is not really a freeze) earlyoom activates and nukes a few things, including Firefox, which brings back interactive response. It also killed Chrome and Remmina, which was irritating, but that's what earlyoom is there to do; better than minutes of no keyboard response. Alt F2 seem to work after a few seconds too, which allows restart of the gnome shell. I will comment on the upstream 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/1749779 Title: System freeze when going back and forth fullscreen mode with Firefox Status in Mozilla Firefox: Confirmed Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/71 --- Use Ubuntu 17.10 Open a Wayland session Start Firefox Press F11 repeatedly --> The System freezes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 20:09:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1749779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
I have been investigating other bug reports. I can't find anything that helps my very much, but I did note references to timing. It is very puzzling why I don't have problems when booting from the installation to an external drive. That drive is actually a USB stick (ext4 formatted). My internal ssd uses lvm, the stick not, but the stick is also much slower, just in case that is relevant. -- 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/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. In recovery mood, I can log in. With no external monitors attached, it works. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
I have been trying to work out how to log a failed session with plymouth debug messages. I finally succeeded, it is attached. Note that at the end of log file, it goes into suspend. That was me trying to power off the machine, and not holding the button long enough. It actually suspends and resume right back to the stuck plymouth display, but I don't know any way out except to force the machine off. ** Attachment added: "Boot log including plymouth trace messages" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5353608/+files/plymouth_fail.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/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. In recovery mood, I can log in. With no external monitors attached, it works. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
I installed 20.04 beta on a usb drive on the same machine, and reinstalled packages to resemble my main install as closely as possible. The bug does not occur when booting from the usb drive. The most significant difference I can think of is that the main install is on an lvm partition (unencrypted). -- 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/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. In recovery mood, I can log in. With no external monitors attached, it works. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
** Attachment added: "boot messages with plymouth debugging messages" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.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/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. In recovery mood, I can log in. With no external monitors attached, it works. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
** Summary changed: - booting with splash hangs when external monitors are connected (pure intel laptop) + booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) ** Description changed: + I think this is a problem with the splash boot loader. This problem is + not reproduced if using nosplash. - I think this is a problem with the splash boot loader. + I have installed 20.04 to this laptop. Thinkpad T480, i7, intel + graphics. - I have installed 20.04 to this laptop. Clean install, not an upgrade. + Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. - I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. + I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. + In recovery mood, I can log in. - I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. + + With no external monitors attached, it works. + + I am used to having such problems with Nvidia graphics is involved, but + this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed - tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed + tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo UHD Graphics 620 [17aa:225d] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel laptop)
** Summary changed: - booting with splash hangs when external monitors are connected + booting with splash hangs when external monitors are connected (pure intel laptop) -- 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/1872159 Title: booting with splash hangs when external monitors are connected (pure intel laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Attachment added: "journalctl -b-1 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.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/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Attachment added: "journalctl -b0 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.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/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New -- 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/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works.
@Alberto, couldn't prime-select do this when going into hybrid or Optimus mode? Only users with nvidia hybrid graphics would go down this logic path, and they are only ones who need the fix (but only if they are using gdm3, sddm and lightdm continue to be unaffected by this) The set of users who "need" this fix are gdm3 users with hybrid Nvidia graphics (where "need" = want tear-free graphics on their laptop panel if Optimus, or on all displays if it's something like a T-series Thinkpad where the nvidia card has no direct access to any display). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
This bug persists in 20.04 daily. The one-line Pop!OS solution (https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26) works, just logout and login. Pop!OS has used this for several releases now, just saying. ** Summary changed: - nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg + nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765888] Re: Please revert to debian-alternatives based prime-select
** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765888 Title: Please revert to debian-alternatives based prime-select Status in nvidia-prime package in Ubuntu: Fix Released Bug description: The new prime-select has some problems. It is very slow to switch, since it does initramfs -u each time It leaves my two optimus laptops without graphics if you leave it in prime-select intel but boot with discrete nvidia. Previously this would load nvidia drivers. These are both two bad 'regressions' in the user experience, the first for everyone, the second for those how have a hardware mux. I know there is bug in logind meaning that a restart is required to poweroff the nvidia card. But this is not new, right? What has happened between 17.10 and 18.04 that has required this dramatic change? Is it now broken to use debian alternatives? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:25:58 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847144] Re: network-manager-openvpn config import ignores tls-crypt section
You are correct. Thanks. I was so puzzled by this. I am using KDE. Possibly the network manager interface is different. This is what I did. Imported the openvpn config file into networkmanger. It makes a connection, it times out, and no amount of debugging gives any more hint. I edit the openvpn file, and extract the key block into a file. It is the key block in between and so my text file looks like this: -BEGIN OpenVPN Static key V1- 92e2de5ae6437298634a0ebe952 . . . cc05zxzxczczxxczxzxczxce902b498a5 -END OpenVPN Static key V1- I save it as blabla.key Then I opened the openvpn connection imported into nm, choose Advanced... on the VPM (openvpn) tab,Choose TLS Settings, and change only two things Mode is TLS-Crypt and Key File i give the path of the key file created just before. And immediately, the connection worked ** Attachment added: "2019-11-28_21-32.png" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1847144/+attachment/5308442/+files/2019-11-28_21-32.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1847144 Title: network-manager-openvpn config import ignores tls-crypt section Status in network-manager-openvpn package in Ubuntu: New Bug description: I setup a vpn on raspberry pi with pivpn. It creates ovpn files with a tls-crypt section # # 2048 bit OpenVPN static key # -BEGIN OpenVPN Static key V1- -END OpenVPN Static key V1- network-manager fails to extract this key and setup the advanced tls- crypt section when one imports the ovpn file and vpn cannot connect (logs only show a timeout). on the other hand openvpn --config ovpn-file works fine. extracting the tls-crypt key and setting the tls settings to tls-crypt with this extracted key, enables the vpn to work. additionally, it doesn't extract the config to verify the name as the ovpn file also requests it do (again, cant set this manually) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager-openvpn 1.8.10-1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 7 23:30:49 2019 InstallationDate: Installed on 2019-01-06 (274 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to disco on 2019-04-18 (172 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1847144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
I haven't had this problem for several releases, so it is only triggered under some circumstances. I suspected the hangouts extension (which I no longer use) -- 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/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open Status in gnome-session package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy gnome-session-bin gnome-session-bin: Installed: 3.18.1.2-1ubuntu1.16.04.1 Candidate: 3.18.1.2-1ubuntu1.16.04.1 Version table: *** 3.18.1.2-1ubuntu1.16.04.1 500 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.18.1.2-1ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages I'm using gnome-session-flashback What happens: The screen doesn't lock when having certain pages in Chrome tabs Expected: The screen should lock after the configured timeout in settings. I've been having this issue sice before 14.04, which I recently upgraded (fresh install) to 16.04. After fresh install, the screen would turn down and lock the computer after 10 minutes (or whatever time I setup). At one point it stopped working. The screen never shuts down unless I manually lock the session with CTRL-ALT-L. I've followed the steps in https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure The culprit seems to be that Chrome issues some suspend inhibitions through dbus when doing certain operations. Many people find this problem when using Yahoo Mail. I can reproduce it with Odoo. I'm pretty sure that Chrome is doing something else of what i've found out. 1) Gnome screen saver works correctly. I can trigger it manually with: $ gnome-screensaver-command -a 2) Gnome screen saver never receives the "session idle" status callback. 3) When Chrome is not running, I can manually inhibit the idle status: $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" --inhibit-only --inhibit idle:suspend Inhibiting until Ctrl+C is pressed... 4) I can query the inhibitors: $ dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 reply_serial=2 array [ object path "/org/gnome/SessionManager/Inhibitor1686" ] $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetAppId ('test',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetReason ('manual idle inhibit',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetFlags (uint32 12,) 12=4(suspend) + 8(idle) 5) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1 minute). After these 70 seconds pass, the screen locks. 6) Regarding Chrome, this is the information I get when querying the inhibitor: GetAppId: ('/usr/bin/google-chrome-stable',) GetReason: ('Uploading data to 10.200.0.163',) GetFlags: (uint32 4,) The flags just inhibits suspend, not locking or entering powersaving mode. This inhibitor seems to stay for 10-15 seconds, then goes away for another 30-60 seconds. The screen NEVER locks when this tab is open. No matter the inhibitor is present or not. I'm not sure where to go on. If it's a Chrome bug it must be using other mechanisms to prevent the idle timeout. Any ideas on what to look for? Julian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers
A very similar thing just happened to me, with the 435 drivers via ppa. Reverting to 430 solved it. Ubuntu 19.04, P50. USB mouse works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1826597 Title: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or trackpoint), does not respond to any input after installing ubuntu 19.04. The same machine has been working fine with ubuntu 16.04 and 18.10. To be more correct it is still working in 16.04 hwe which I'm dual booting. If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and replace with noveau drivers it works just fine (by the way there seems to be no other issues with the nvidia driver as of yet). I have also the nvidia-driver-390 also suggested in the graphical software updates tool, to no avail. I will attach relevant logs. Please let me know if there is more I should supply. And thanks for all your hard (and brilliant) work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 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 BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 20:36:18 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2019-04-26 (0 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 003: ID 04f2:b596 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20EQS0PQ00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash synaptic_intertouch=0 vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS0PQ00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EQS0PQ00 dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 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/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions -- Mailing list: https://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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I think his point was to isolate the problem as being gdm3's wayland code. If you need modeset=1 for wayland, then why is there any effort to support nvidia and wayland under gnome, since it won't work (or are only optimus systems affected by this?) my point was that you marked this as invalid, but the only way to avoid this bug is to avoid using gdm3. You don't have to change anything else. So it looks like a gdm3 bug. On Fri, 21 Jun 2019 at 11:50, Daniel van Vugt wrote: > Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind > of pointless. It's pointless because the most common reason for using > nvidia-drm.modeset=1 is to get Wayland support. I know there are other > reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in > PRIME setups. But mostly if people use modeset=1 it is to get Wayland > support. > > If we can't get a fix from Nvidia then some kind of workaround that runs > Xorg as root (like comment #26) is probably the next best option. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > nvidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
"gdm3 compile without wayland", I meant -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
What we know about this bug is that gdm3, nvidia and modeset=1 is broken under configurations which are not broken when sddm and lightdm are used. we know that gdm3 sessions with external monitors work with root permissions. we know that gdm3 compiled with wayland also works (according to the gentoo user generix). And neither gnome developers nor nvidia acknowledge a bug. If you make a venn diagram of all of this, gdm3 is the intersection of every observation. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I posted here: https://devtalk.nvidia.com/default/topic/1055528/linux/nvidia-driver-in- modeset-1-requires-root-permissions-daniel-van-vugt-canonical-concludes- it-is-an-nvidia-bug/?offset=3#5351122 -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
User generix reports that when gdm3 is compiled without wayland support, this bug is not seen. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I will post your findings to the nvidia developers forum. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Hi Daniel, thanks for not forgetting about this, unlike everyone else :) Have you communicated this observation to Nvidia at all? -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
This works. Thanks. What does gdm3 do that requires this? -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Still present in 19.04, although as a workaround, the nvidia drivers have reverted to installing without modeset=1, so external monitors work, and Optimus users get dreadful tearing on their laptop's internal screen. With modeset=1 (which in my case was a setting preserved during the update to 19.04): At the login prompt (using gdm3) external monitors are powered on and display a background graphic. During session start, they are lost. External monitors work with lightdm or sddm3, both supported display managers in Ubuntu, so this remains the workaround. So odd that Fedora doesn't care about this. It's a dreadful welcome to Linux moment. Using gdm3 as the default display manager seems insane given this bug. -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820543] Re: [snap] libreoffice can not see mounted volume under /opt1
Thanks Olivier, I changed my mount point (under /media) and it's working fine now. -- 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/1820543 Title: [snap] libreoffice can not see mounted volume under /opt1 Status in libreoffice package in Ubuntu: Won't Fix Bug description: I have a encrypted luks volume which is under lvm management. I mount it manually from a script. It's mounted to /opt1 the libreoffice snap does not see this mounted directory; it is not part of the filesystem known to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1820543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820543] [NEW] libreoffice snap can not see mounted volume
Public bug reported: I have a encrypted luks volume which is under lvm management. I mount it manually from a script. It's mounted to /opt1 the libreoffice snap does not see this mounted directory; it is not part of the filesystem known to the snap. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1820543 Title: libreoffice snap can not see mounted volume Status in libreoffice package in Ubuntu: New Bug description: I have a encrypted luks volume which is under lvm management. I mount it manually from a script. It's mounted to /opt1 the libreoffice snap does not see this mounted directory; it is not part of the filesystem known to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1820543/+subscriptions -- Mailing list: https://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 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Personally, I have not encountered that when using ubuntu or fedora and simply swapping gdm3 for lightdm but it's good that the other bug report has a fix. It looks like a hidpi bug; none of my monitors are hidpi. On Thu, 21 Feb 2019 at 12:50, Stefano <1716...@bugs.launchpad.net> wrote: > The problem with the lightdm workaround is that many had this cursor > issue: > > https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1770948 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > gdm3, hybrid nvidia with modeset=1, no external monitors detected > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://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 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
There are two workarounds mentioned: swap to lightdm and manipulate gdm3 start. I think you refer to the gdm3 startup changes when you say it causes problems with suspend/resume (which I didn't try). The other workaround is changing display manager to lightdm (or sddm, the KDE display manager). swapping to lightdm has not caused any suspend/resume problems for me on the two Optimus laptops I used, so I think the lightdm workaround is ok. It was the default display manager of ubuntu for a long time and is still the default for xubuntu. On Thu, 21 Feb 2019 at 08:45, Stefano <1716...@bugs.launchpad.net> wrote: > Yes but this workaround is going to create others issue for suspend and > resume. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > gdm3, hybrid nvidia with modeset=1, no external monitors detected > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
I switched to KDE to have a look at it, by installing KDE Neon from the PPAs. Otherwise the same environment. The slow suspend doesn't happen in plasma, it suspends in five seconds, while still suspending properly (including open VMWare virtual machines). So it's not simply Chrome, the bug needs gnome as well. -- 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/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open Status in gnome-session package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy gnome-session-bin gnome-session-bin: Installed: 3.18.1.2-1ubuntu1.16.04.1 Candidate: 3.18.1.2-1ubuntu1.16.04.1 Version table: *** 3.18.1.2-1ubuntu1.16.04.1 500 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.18.1.2-1ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages I'm using gnome-session-flashback What happens: The screen doesn't lock when having certain pages in Chrome tabs Expected: The screen should lock after the configured timeout in settings. I've been having this issue sice before 14.04, which I recently upgraded (fresh install) to 16.04. After fresh install, the screen would turn down and lock the computer after 10 minutes (or whatever time I setup). At one point it stopped working. The screen never shuts down unless I manually lock the session with CTRL-ALT-L. I've followed the steps in https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure The culprit seems to be that Chrome issues some suspend inhibitions through dbus when doing certain operations. Many people find this problem when using Yahoo Mail. I can reproduce it with Odoo. I'm pretty sure that Chrome is doing something else of what i've found out. 1) Gnome screen saver works correctly. I can trigger it manually with: $ gnome-screensaver-command -a 2) Gnome screen saver never receives the "session idle" status callback. 3) When Chrome is not running, I can manually inhibit the idle status: $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" --inhibit-only --inhibit idle:suspend Inhibiting until Ctrl+C is pressed... 4) I can query the inhibitors: $ dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 reply_serial=2 array [ object path "/org/gnome/SessionManager/Inhibitor1686" ] $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetAppId ('test',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetReason ('manual idle inhibit',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetFlags (uint32 12,) 12=4(suspend) + 8(idle) 5) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1 minute). After these 70 seconds pass, the screen locks. 6) Regarding Chrome, this is the information I get when querying the inhibitor: GetAppId: ('/usr/bin/google-chrome-stable',) GetReason: ('Uploading data to 10.200.0.163',) GetFlags: (uint32 4,) The flags just inhibits suspend, not locking or entering powersaving mode. This inhibitor seems to stay for 10-15 seconds, then goes away for another 30-60 seconds. The screen NEVER locks when this tab is open. No matter the inhibitor is present or not. I'm not sure where to go on. If it's a Chrome bug it must be using other mechanisms to prevent the idle timeout. Any ideas on what to look for? Julian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
sddm works too: I just put kde plasma on my ThinkPad P50 with ubuntu 18.10, it works well. -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://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 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
If you have this bug, what is the result of opening a terminal, and running systemctl suspend and waiting for a minute? On Fri, 14 Dec 2018 at 08:24, Jeremy Walker <1600...@bugs.launchpad.net> wrote: > The importance on this ticket is incorrect: it should not be marked > "low". According to https://dev.launchpad.net/BugTriage#importance) > "Low" is defined as "legitimate but that is not scheduled for Canonical > staff to fix in the next 6 months." > > This is a MAJOR issue. As W-barath-hotmail noted it can cause some > extremely serious side effects for anyone who relies on power > management. As such, this ticket should have an importance of "High" > ("we believe we will work on in the next six months"). To ignore it for > six or more months would be to deliberately cause serious user damage. > > Also, this bug is difficult for users to track down. It's not like > problematic tabs flash red or something, so each user has to figure out > on their own that not only is Chrome the source of the problem, but a > specific tab within Chrome. As a result, the number of users affected by > this bug is undoubtedly much higher than what's reflected on this page, > as many affected users just aren't able to track the problem to this > page. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1600622 > > Title: > Screen doesn't lock or go to sleep when certain Chrome tabs are open > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions > -- Tim Richardson -- 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/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open Status in gnome-session package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy gnome-session-bin gnome-session-bin: Installed: 3.18.1.2-1ubuntu1.16.04.1 Candidate: 3.18.1.2-1ubuntu1.16.04.1 Version table: *** 3.18.1.2-1ubuntu1.16.04.1 500 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.18.1.2-1ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages I'm using gnome-session-flashback What happens: The screen doesn't lock when having certain pages in Chrome tabs Expected: The screen should lock after the configured timeout in settings. I've been having this issue sice before 14.04, which I recently upgraded (fresh install) to 16.04. After fresh install, the screen would turn down and lock the computer after 10 minutes (or whatever time I setup). At one point it stopped working. The screen never shuts down unless I manually lock the session with CTRL-ALT-L. I've followed the steps in https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure The culprit seems to be that Chrome issues some suspend inhibitions through dbus when doing certain operations. Many people find this problem when using Yahoo Mail. I can reproduce it with Odoo. I'm pretty sure that Chrome is doing something else of what i've found out. 1) Gnome screen saver works correctly. I can trigger it manually with: $ gnome-screensaver-command -a 2) Gnome screen saver never receives the "session idle" status callback. 3) When Chrome is not running, I can manually inhibit the idle status: $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" --inhibit-only --inhibit idle:suspend Inhibiting until Ctrl+C is pressed... 4) I can query the inhibitors: $ dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 reply_serial=2 array [ object path "/org/gnome/SessionManager/Inhibitor1686" ] $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetAppId ('test',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetReason ('manual idle inhibit',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetFlags (uint32 12,) 12=4(suspend) + 8(idle) 5) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1 minute). After t
Re: [Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
I have noticed that a) systemctl suspend does actually suspend, but it takes about 30 seconds. I'm on 18.04.1 with kernel 4.18.0-13-generic from the proposed PPA This is quite surprising, but good news. I don't know why this is working now. It works with either Chromium or Chrome open, with hangouts running. Because gnome uses systemctl suspend, this means that manual suspend from gnome shell is also working. I just suspended right now with a hangouts conversation in progress and a Zoom meeting started, and it succeeded. Maybe the more recent kernel fixes it? b) pkexec systemctl -i suspend (run with root privileges) always works, but this is less suprising, since -i means ignore inhibitors. On Thu, 13 Dec 2018 at 12:16, ethanbrown wrote: > I agree with W-barath-hotmail that this is a serious problem that needs > to be addressed. I believe on some occasions suspend fails even after > I've killed Chrome. > > Please increase the Importance ranking of this bug. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1600622 > > Title: > Screen doesn't lock or go to sleep when certain Chrome tabs are open > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions > -- Tim Richardson -- 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/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open Status in gnome-session package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy gnome-session-bin gnome-session-bin: Installed: 3.18.1.2-1ubuntu1.16.04.1 Candidate: 3.18.1.2-1ubuntu1.16.04.1 Version table: *** 3.18.1.2-1ubuntu1.16.04.1 500 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.18.1.2-1ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages I'm using gnome-session-flashback What happens: The screen doesn't lock when having certain pages in Chrome tabs Expected: The screen should lock after the configured timeout in settings. I've been having this issue sice before 14.04, which I recently upgraded (fresh install) to 16.04. After fresh install, the screen would turn down and lock the computer after 10 minutes (or whatever time I setup). At one point it stopped working. The screen never shuts down unless I manually lock the session with CTRL-ALT-L. I've followed the steps in https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure The culprit seems to be that Chrome issues some suspend inhibitions through dbus when doing certain operations. Many people find this problem when using Yahoo Mail. I can reproduce it with Odoo. I'm pretty sure that Chrome is doing something else of what i've found out. 1) Gnome screen saver works correctly. I can trigger it manually with: $ gnome-screensaver-command -a 2) Gnome screen saver never receives the "session idle" status callback. 3) When Chrome is not running, I can manually inhibit the idle status: $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" --inhibit-only --inhibit idle:suspend Inhibiting until Ctrl+C is pressed... 4) I can query the inhibitors: $ dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 reply_serial=2 array [ object path "/org/gnome/SessionManager/Inhibitor1686" ] $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetAppId ('test',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetReason ('manual idle inhibit',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetFlags (uint32 12,) 12=4(suspend) + 8(idle) 5) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1 minute). After these 70 seconds pass, the screen locks. 6) Regarding Chrome, this is the information I get when querying the inhibitor: GetAppId: ('/usr/bin/google-chrome-stable',) GetReason: ('Uploading data to 10.200.0.163',) GetFlags: (uint32 4,) The flags just inhibits suspend, not locking or entering powersaving mode. This inhibitor seems to stay for 10-15 se
[Desktop-packages] [Bug 1791848] [NEW] in cosmic, prime-select nvidia does not work if display manager is lightdm
Public bug reported: nvidia-prime 0.8.9 with display manager lightdm, choose the nvidia driver on my Optimus Thinkpad P50 does not work. the nvidia driver does not load. It works with gdm3, and so does prime-select intel (only tested in x.org session so far) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1791848 Title: in cosmic, prime-select nvidia does not work if display manager is lightdm Status in nvidia-prime package in Ubuntu: New Bug description: nvidia-prime 0.8.9 with display manager lightdm, choose the nvidia driver on my Optimus Thinkpad P50 does not work. the nvidia driver does not load. It works with gdm3, and so does prime-select intel (only tested in x.org session so far) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1791848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
Hi Ryan, my solution uses bbswitch to turn off the card, which is what Ubuntu used before 18.04. If it works for your hardware in 16.04 (up to and including 17.10) it will work in 18.04. Also if it was working and then stopped working, it must be something you did. If you'd like support with it, please post an issue on the github repo. Note that the readme has debugging steps. It doesn't actually do very much, so there is not much than can go wrong. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
uBlock fixes it for me and others ... But there should be some user control -- 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/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open Status in gnome-session package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy gnome-session-bin gnome-session-bin: Installed: 3.18.1.2-1ubuntu1.16.04.1 Candidate: 3.18.1.2-1ubuntu1.16.04.1 Version table: *** 3.18.1.2-1ubuntu1.16.04.1 500 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.18.1.2-1ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages I'm using gnome-session-flashback What happens: The screen doesn't lock when having certain pages in Chrome tabs Expected: The screen should lock after the configured timeout in settings. I've been having this issue sice before 14.04, which I recently upgraded (fresh install) to 16.04. After fresh install, the screen would turn down and lock the computer after 10 minutes (or whatever time I setup). At one point it stopped working. The screen never shuts down unless I manually lock the session with CTRL-ALT-L. I've followed the steps in https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure The culprit seems to be that Chrome issues some suspend inhibitions through dbus when doing certain operations. Many people find this problem when using Yahoo Mail. I can reproduce it with Odoo. I'm pretty sure that Chrome is doing something else of what i've found out. 1) Gnome screen saver works correctly. I can trigger it manually with: $ gnome-screensaver-command -a 2) Gnome screen saver never receives the "session idle" status callback. 3) When Chrome is not running, I can manually inhibit the idle status: $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" --inhibit-only --inhibit idle:suspend Inhibiting until Ctrl+C is pressed... 4) I can query the inhibitors: $ dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 reply_serial=2 array [ object path "/org/gnome/SessionManager/Inhibitor1686" ] $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetAppId ('test',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetReason ('manual idle inhibit',) $ gdbus call --session --dest org.gnome.SessionManager --object-path /org/gnome/SessionManager/Inhibitor1686 --method org.gnome.SessionManager.Inhibitor.GetFlags (uint32 12,) 12=4(suspend) + 8(idle) 5) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1 minute). After these 70 seconds pass, the screen locks. 6) Regarding Chrome, this is the information I get when querying the inhibitor: GetAppId: ('/usr/bin/google-chrome-stable',) GetReason: ('Uploading data to 10.200.0.163',) GetFlags: (uint32 4,) The flags just inhibits suspend, not locking or entering powersaving mode. This inhibitor seems to stay for 10-15 seconds, then goes away for another 30-60 seconds. The screen NEVER locks when this tab is open. No matter the inhibitor is present or not. I'm not sure where to go on. If it's a Chrome bug it must be using other mechanisms to prevent the idle timeout. Any ideas on what to look for? Julian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
I've made a few tweaks which you can see here https://github.com/timrichardson/Prime-Ubuntu-18.04 it now works between reboots. I should do a fresh install to make sure it works without action. For example, I've made a note that after install I did sudo systemctl enable prime-socket the problem I have is that I don't have any clue about what I'm doing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
Matthieu's code is the best solution I've seen, as long as you are ok with lightdm. The multi-dispatch aspects of the new module are a good simplification, Matthieu's approach looks like it's now easy to switch between intel and hybrid modes; he just blacklists modules. Dear maintainers, it seems a shame to stop using bbswitch, the cause of all the functional and user-experience regressions of the new package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765556] Re: nvidia-prime needs a reboot to switch between dGPU/hGPU
You should read the changelog. nvidia-prime doesn't use bbswitch anymore, I don't know why. The changelog doesn't say. It now uses the built-in kernel mechanism for turning off the nvidia card. Unfortunately, this method requires the nouveau driver and unfortunately you can't load the nouveau driver and the nvidia driver at the same time. Also, unfortunately the nvidia driver can't be unloaded without a reboot, due to a bug in logind, or at least without restarting logind. Somehow, this also means that the nvidia driver needs to be actually uninstalled, which means rebuilding initramfs to uninstall nvidia. And going back to nvidia (hybrid mode) now requires the nvidia driver to be reinstalled. It's a far cry from the old way. It's a bit of puzzle because bbswitch still works in the latest kernel and with the latest nvidia. But prime select is pretty complex, I haven't found another distribution where it has been ported, so there are probably good reasons for this. The dev says this approach is needed to work around gdm3 bugs, which I find ironic since I have never got gdm3 working with my nvidia laptops anyway (I use modeset=1 with the nvidia driver). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU Status in nvidia-prime package in Ubuntu: Confirmed Bug description: I previously used Ubuntu 16.04 and Nvidia 375 driver with a Nvidia Geforce 635M and Sandy Bridge i7. To switch between the 2 Optimus cards (Intel hybrid and Nvidia discrete), one had to go into nvidia- settings, switch, logoff, login back, and the change was applied. I now have a Nvidia Quadro M2000 and a Skylake Xeon which has some Sync/Mux feature (whatever does that mean) with the Nvidia 390 driver. First of all, installing nivida-prime doesn't install bbswitch-dkms. Then, once the GPU switch is made, it triggers update-initramfs, recompile the kernel modules, and one needs to reboot the system to get the GPU change. Even when we install bbswitch-dkms. So am I getting a wrong impression or is there something twisted here ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:20:01 2018 Dependencies: InstallationDate: Installed on 2018-04-08 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765887] Re: prime-select leaves system in strange state with nvidia enabled but blacklisted
I can not reproduce this. Have marked invalid. ** Changed in: nvidia-prime (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765887 Title: prime-select leaves system in strange state with nvidia enabled but blacklisted Status in nvidia-prime package in Ubuntu: Invalid Bug description: I don't know how to replicate this bug yet, I will update if I learn more. Several times as I test prime-select on my Thinkpad P50, I have ended up in situations where the laptop will not start graphics. This always happens if you leave the laptop in prime-select intel and then boot the machine with the BIOS settings Discrete (subject of another bug report). At the moment, I have this state prime-select query nvidia but present is /etc/modprobe.d/blacklist-nvidia.conf The machine has three screens (internal, hdmi and 4K via display port). only the display port is on, and it's in HD mode. The nvidia driver is not loaded. Apparently nouveau is not too. Is there any log file that may indicate how this happens? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:18:16 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
This is not a new problem, and it affects every gdm3-based distro that I have used. Long story short; if you want to use modeset=1 with nvidia to get rid of tearing (which would be every linux Optimus user on the planet), gdm3 doesn't work. No one seems to know why. Change your display manager to lightdm and enjoy life again. I have two Optimus laptops. sudo dpkg-reconfigure lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768003] Re: nvidia-prime is no longer able to turn off the discrete GPU
*** This bug is a duplicate of bug 1765363 *** https://bugs.launchpad.net/bugs/1765363 ** This bug has been marked a duplicate of bug 1765363 prime-select intel is not powering off the nvidia card -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1768003 Title: nvidia-prime is no longer able to turn off the discrete GPU Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Since updating to Ubuntu 18.04 from 17.10, the discrete GPU is no longer turned off. I see since https://bugs.launchpad.net/ubuntu/+source/nvidia- prime/+bug/1757180 the way to turn off the discrete GPU has been changed, I suppose that's what caused the regression. My laptop is a ThinkPad W541, with a NVIDIA Quadro K2100M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1768003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765888] [NEW] Please revert to debian-alternatives based prime-select
Public bug reported: The new prime-select has some problems. It is very slow to switch, since it does initramfs -u each time It leaves my two optimus laptops without graphics if you leave it in prime-select intel but boot with discrete nvidia. Previously this would load nvidia drivers. These are both two bad 'regressions' in the user experience, the first for everyone, the second for those how have a hardware mux. I know there is bug in logind meaning that a restart is required to poweroff the nvidia card. But this is not new, right? What has happened between 17.10 and 18.04 that has required this dramatic change? Is it now broken to use debian alternatives? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:25:58 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765888 Title: Please revert to debian-alternatives based prime-select Status in nvidia-prime package in Ubuntu: New Bug description: The new prime-select has some problems. It is very slow to switch, since it does initramfs -u each time It leaves my two optimus laptops without graphics if you leave it in prime-select intel but boot with discrete nvidia. Previously this would load nvidia drivers. These are both two bad 'regressions' in the user experience, the first for everyone, the second for those how have a hardware mux. I know there is bug in logind meaning that a restart is required to poweroff the nvidia card. But this is not new, right? What has happened between 17.10 and 18.04 that has required this dramatic change? Is it now broken to use debian alternatives? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:25:58 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765887] [NEW] prime-select leaves system in strange state with nvidia enabled but blacklisted
Public bug reported: I don't know how to replicate this bug yet, I will update if I learn more. Several times as I test prime-select on my Thinkpad P50, I have ended up in situations where the laptop will not start graphics. This always happens if you leave the laptop in prime-select intel and then boot the machine with the BIOS settings Discrete (subject of another bug report). At the moment, I have this state prime-select query nvidia but present is /etc/modprobe.d/blacklist-nvidia.conf The machine has three screens (internal, hdmi and 4K via display port). only the display port is on, and it's in HD mode. The nvidia driver is not loaded. Apparently nouveau is not too. Is there any log file that may indicate how this happens? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:18:16 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765887 Title: prime-select leaves system in strange state with nvidia enabled but blacklisted Status in nvidia-prime package in Ubuntu: New Bug description: I don't know how to replicate this bug yet, I will update if I learn more. Several times as I test prime-select on my Thinkpad P50, I have ended up in situations where the laptop will not start graphics. This always happens if you leave the laptop in prime-select intel and then boot the machine with the BIOS settings Discrete (subject of another bug report). At the moment, I have this state prime-select query nvidia but present is /etc/modprobe.d/blacklist-nvidia.conf The machine has three screens (internal, hdmi and 4K via display port). only the display port is on, and it's in HD mode. The nvidia driver is not loaded. Apparently nouveau is not too. Is there any log file that may indicate how this happens? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:18:16 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
However, I do not have this problem on my Thinkpad P50. The nvidia card is definitely turned off when in hybrid graphics after prime-select intel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: New Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] [NEW] prime-select intel is not powering off the nvidia card
Public bug reported: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: New Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765300] [NEW] nvidia-prime can't log in if boot in discrete mode on Thinkpad with hardware video mux
Public bug reported: 1) to save power, sudo prime-select intel and boot in hybrid graphics This is the only way I know to get the nvidia card off which is the only reason I boot like this This still works, although it is really slow. 2) to go back to multi-monitors, reboot, at bios turn on discrete graphics and it does not reach password entry. The greeter crashes/restarts/crashes/restarts In the 17.10 build of the driver, even 396.18 which is newer than the 18.04 driver, step 2 simply boots you with nvidia graphics. The current situation is really horrible. Overall, optimus experience is extremely degraded in 18.04. Since I have the very latest beta in 17.10, why has there been such a huge change which is even in the best case really slow, and the worse case result in boot failure? Why can't we keep the approach used since 16.04 or may be earlier? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 16:20:45 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765300 Title: nvidia-prime can't log in if boot in discrete mode on Thinkpad with hardware video mux Status in nvidia-prime package in Ubuntu: New Bug description: 1) to save power, sudo prime-select intel and boot in hybrid graphics This is the only way I know to get the nvidia card off which is the only reason I boot like this This still works, although it is really slow. 2) to go back to multi-monitors, reboot, at bios turn on discrete graphics and it does not reach password entry. The greeter crashes/restarts/crashes/restarts In the 17.10 build of the driver, even 396.18 which is newer than the 18.04 driver, step 2 simply boots you with nvidia graphics. The current situation is really horrible. Overall, optimus experience is extremely degraded in 18.04. Since I have the very latest beta in 17.10, why has there been such a huge change which is even in the best case really slow, and the worse case result in boot failure? Why can't we keep the approach used since 16.04 or may be earlier? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 16:20:45 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764089] Re: blank screen (no backlight) after login on both xubuntu and ubuntu desktops, Optimus laptop
attachment is generated by the nvidia-bug-reporting tool, which collects many logs ** Attachment added: "nvidia-gathered logs" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1764089/+attachment/5116362/+files/nvidia-bug-report.log.gz -- 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/1764089 Title: blank screen (no backlight) after login on both xubuntu and ubuntu desktops, Optimus laptop Status in lightdm package in Ubuntu: New Bug description: I have a Thinkpad W520. In Optimus mode, lightdm presents a blank screen after login. Virtual terminals work. On the same laptop, gdm3 allows me to log in to ubuntu desktop. In pure Nvidia mode, login works. The bug report tool told me that log files will be attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sun Apr 15 19:55:08 2018 InstallationDate: Installed on 2018-02-25 (49 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1764089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764089] [NEW] blank screen (no backlight) after login on both xubuntu and ubuntu desktops, Optimus laptop
Public bug reported: I have a Thinkpad W520. In Optimus mode, lightdm presents a blank screen after login. Virtual terminals work. On the same laptop, gdm3 allows me to log in to ubuntu desktop. In pure Nvidia mode, login works. The bug report tool told me that log files will be attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sun Apr 15 19:55:08 2018 InstallationDate: Installed on 2018-02-25 (49 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1764089 Title: blank screen (no backlight) after login on both xubuntu and ubuntu desktops, Optimus laptop Status in lightdm package in Ubuntu: New Bug description: I have a Thinkpad W520. In Optimus mode, lightdm presents a blank screen after login. Virtual terminals work. On the same laptop, gdm3 allows me to log in to ubuntu desktop. In pure Nvidia mode, login works. The bug report tool told me that log files will be attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sun Apr 15 19:55:08 2018 InstallationDate: Installed on 2018-02-25 (49 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1764089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
gdm3 and nvidia binary drivers don't work together yet. Maybe 18.04 although there's not much evidence that anyone who knows how to fix this problem is working on it. This problem has emerged since the default Ubuntu session now uses gdm3 (as of 17.10) but standard gnome users on all recent distribution have the same problem. The best solution is to replace gdm3 with lightdm. (sudo apt install lightdm) You can install both display managers and swap between them with dpkg-reconfigure lightdm (or dpkg-reconfigure gdm3) and obviously choose lightdm You don't seem to lose anything by using lightdm instead of gdm3. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Celebratory fireworks from me. It seems to work. For ubuntu the only difference is [Service] ExecStartPre=/usr/share/gdm/generate-config becomes [Service] ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config I have a proper ubuntu gnome session running with gdm, an external monitor and laptop panel, with prime sync on and no flickering, running 'ubuntu on xorg' *** FOR THE FIRST TIME EVER *** on my thinkpad W520 which is old but is a genuine Optimus laptop with Quadro graphics on the nvidia 387.34 binary driver in Optimus mode. -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gnome-shell package in Ubuntu: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
ubuntu user Hon Weng Chong has emailed me as he continues to investigate the problem. He believes he has proof that it is is GDM configuration issue and has provided the following fix Hey Tim, I figured out a hack solution to the GDM prime issue. If you replace /lib/systemd/system/gdm3.service with this file: https://gist.github.com/hwchong/b3634b387e91b38d355a0500ffecfc7d and /etc/X11/xorg.conf with this: https://gist.github.com/hwchong/28d7c70aafd62a0d3114c5746da7da36 You should be able to use Prime Sync with your Intel graphics card and have an external monitor connected to the Nvidia GPU without using LightDM. Cheers, Hon His proposed changes to xorg are probably not significant. He is proposing to add this to nvidia options, but this can be done via the GUI or command line. Option "metamodes" "nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}" The revised /lib/systemd/system/gdm3.service he proposes is is --> Compared to Fedora 27's config, changes seem to be the addition of ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config . . . RestartSec=1s ExecReload=/usr/share/gdm/generate-config [Unit] Description=GNOME Display Manager # replaces the getty Conflicts=getty@tty1.service After=getty@tty1.service # replaces plymouth-quit since it quits plymouth on its own Conflicts=plymouth-quit.service After=plymouth-quit.service # Needs all the dependencies of the services it's replacing # pulled from getty@.service and plymouth-quit.service # (except for plymouth-quit-wait.service since it waits until # plymouth is quit, which we do) After=rc-local.service plymouth-start.service systemd-user-sessions.service # GDM takes responsibility for stopping plymouth, so if it fails # for any reason, make sure plymouth still stops OnFailure=plymouth-quit.service [Service] ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config ExecStart=/usr/sbin/gdm3 KillMode=mixed Restart=always RestartSec=1s IgnoreSIGPIPE=no BusName=org.gnome.DisplayManager StandardOutput=syslog StandardError=inherit EnvironmentFile=-/etc/default/locale ExecReload=/usr/share/gdm/generate-config ExecReload=/bin/kill -SIGHUP $MAINPID -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gnome-shell package in Ubuntu: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes
#22 worked for me, after logout/login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes Status in gedit package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Expired Bug description: In a freshly booted and fully updated Ubuntu 16.10 the edit window of gedit is transparent using the *Classic* colour scheme. Other colour schemes seem to work as intended. The text of loaded files shows against the desktop wallpaper but when no files are loaded gedit displays its edit window or pane as it should do. To clarify this bug is only apparent when a file is loaded. I don't know when this started as I don't normally used gedit to edit files. I haven't found any other application affected by this problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gedit 3.20.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 6 21:01:35 2016 InstallationDate: Installed on 2016-03-11 (179 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
** Summary changed: - no gdm3 greeter with nvidia quadro and modeset=1 + no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) -- 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/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) Status in gnome-shell package in Ubuntu: New Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] [NEW] gdm3, hybrid nvidia with modeset=1, no external monitors detected
Public bug reported: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gdm3, hybrid nvidia in modeset, no external monitors detected + gdm3, hybrid nvidia with modeset=1, no external monitors detected -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gnome-shell package in Ubuntu: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
As of the latest updates to gdm3, I still can't boot with my laptop when it's in discrete mode (nvidia graphics only). Does not get to the greeter. syslog is full of countless repetitions of "Stopping NVIDIA persistence Daemon". CPU must be high because the fan comes on. I've reported this but it's going to be better if someone who knows what they are doing can reproduce it. (In hybrid mode, it boots, but no external displays are detected, which implies that nvidia isn't working properly) I have the latest 375 Nvidia driver. nvidia Modesetting is enabled. Still works fine with lightdm as the display manager. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714881/+attachment/4943940/+files/Error_syslog -- 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/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1 Status in gnome-shell package in Ubuntu: New Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714881] [NEW] no gdm3 greeter with nvidia quadro and modeset=1
Public bug reported: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA persistence daemon starting and stopping, as well as gdm messages. I mounted the filesystem after a crash, and I attach syslog. In the attached syslog, search for persistenced to see messages like this Sep 2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extension for GBM renderer: EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT Sep 2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create backend: Failed to create MetaRenderer Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog connection opened Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user ID 123 and group ID 131 Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence Daemon. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237) Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Sep 2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable failure in required component org.gnome.Shell. desktop Sep 2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: ignoring: lo Sep 2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence Daemon... Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15 Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed. Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Sep 2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1 Status in gnome-shell package in Ubuntu: New Bug description: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 10:46:21 UTC Created attachment 359016 [details] syslog reproduced on two Thinkpad laptops with bios set to Discrete graphics. In this mode, the integrated Intel graphics is bypassed by a hardware mux and the machines appears to have only Nvidia graphics. Environment is Ubuntu 17.10 development version, pre-release packages One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are supported by the latest Nvidia drivers. Nvidia driver 375 or 384 (as packaged by Ubuntu) /etc/modprobe.d/zz-nvidia.conf has options nvidia_384_drm modeset=1 and after that setting sudo update-initramfs -u This problem does not occur when lightdm is used in instead of gdm3 or modeset=1 is not deployed. The session attempted to launch is either gnome or the new "ubuntu" desktop session, which is gnome The boot process fails.Sometimes there is just black screen (and high CPU activity driving the fans) and sometimes there is a message about NVIDIA
[Desktop-packages] [Bug 1671799] Re: FFe: xserver 1.19.3
I've been testing 1.19.x in 17.04 pre-release for a few weeks, hoping to take advantage of the Nvidia PRIME synchronisation fix for laptops with Optimus hybrid graphics. As of 1.19.3, PRIME sync works (with a modprobe fix related to the nvidia driver). This is a huge improvement for nvidia Optimus users (i.e. most high-end laptops I suspect), since it means no more screen tearing on the laptop's LCD panel when hybrid graphics mode is activated. My testing has been on a Thinkpad P50. Really hope 1.19 gets into 17.04, and then into 16.04.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1671799 Title: FFe: xserver 1.19.3 Status in xorg-server package in Ubuntu: Confirmed Bug description: xserver 1.19 has been out for quite some time now. Debian Stretch will release with it, and xmir has been recently ported so we can push 1.19 to zesty now. It's currently being staged on a ppa: https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging The main features of this release are: - PRIME synchronization support, should reduce tearing on hybrid setups - GLAMOR (2D accel over OpenGL) improvements - threaded input This bugreport is also for gathering testing feedback. Tested to be working fine on: - Intel Kabylake - Intel Broadwell - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers) - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M]) - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M]) - Radeon SI (radeon & amdgpu drivers) - qemu (QXL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1674304] Re: PRIME synchronization not working with xserver-1.19.x
I have a ThinkPad P50 and Prime sync is now working for me. I don't know what change happened, sorry; it was two weeks since I did an update, and it could be an updated kernel or updated xserver packages from Timo's PPA. I have the 375 driver. And it works really well, it's marvellous to behold no tearing on the laptop panel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1674304 Title: PRIME synchronization not working with xserver-1.19.x Status in nvidia-prime package in Ubuntu: Confirmed Bug description: xserver-1.19.x is being proposed for 17.04, currently available in test ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 On 2 separate Optimus laptops there is no sign of it actually working, tearing while using nvidia drivers (375.x) is rampart. Testing with both current 4.10.0-13 & previous 4.9.0-11 kernels. Shows this in kern.log so support is enabled Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver supports precise vblank timestamp ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nvidia-prime 0.8.4 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 20 07:53:12 2017 InstallationDate: Installed on 2017-03-15 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1578962] Re: [SRU] nm-applet crash with assertion failed for some users
The bug is fixed. No more assertion, no more crash. A message informs me that the wired connection is now established. Then the next message says that the "ethernet" connection is disconnected. Despite that final message, the change from VPN to normal wired connection now works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1578962 Title: [SRU] nm-applet crash with assertion failed for some users Status in Network Manager Applet: Fix Released Status in network-manager-applet package in Ubuntu: Triaged Status in network-manager-applet source package in Xenial: Fix Committed Status in network-manager-applet source package in Yakkety: Triaged Status in network-manager-applet package in Debian: New Bug description: [Impact] nm-applet crashes for some users with assertion failed [Test case] After installing the update, errors.ubuntu.com should receive a much smaller number of assertion failed crash reports. [Regression Potential] The assert is removed by upstream and thus backported to archive package because it was believed most of the assertion triggered are false positives, hence the potential of regression is having mis- functionality but the chance is fair low. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1578962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1578962] Re: nm-applet crashed with SIGABRT in g_assertion_message()
It is not fixed for me. I have proposed-updates and the network-manager version is 1.2.0-0ubuntu0.16.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1578962 Title: nm-applet crashed with SIGABRT in g_assertion_message() Status in Network Manager Applet: Unknown Status in network-manager-applet package in Ubuntu: Fix Committed Status in network-manager-applet package in Debian: New Bug description: crashes every time using applet to switch from an openvpn connection back to wired connection ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri May 6 18:28:28 2016 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (34 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.0.0.138 dev eno1 proto static metric 100 10.0.0.0/24 dev eno1 proto kernel scope link src 10.0.0.61 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 IwConfig: eno1 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash RfKill: Signal: 6 SourcePackage: network-manager-applet StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nm-applet crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo wireshark nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 873b4698-101f-4f18-9d81-c10e6e1fda35 802-3-ethernet 1462523308 Fri 06 May 2016 18:28:28 AEST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/3 do.tim-richardson.net 57e9a26d-0ebd-4004-a599-df2a14d14344 vpn 1462523308 Fri 06 May 2016 18:28:28 AEST yes 0 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 873b4698-101f-4f18-9d81-c10e6e1fda35 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1578962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1578962] Re: nm-applet crashed with SIGABRT in g_assertion_message()
I hvae reported this bug here, where I am adding information in response to questions: https://bugzilla.gnome.org/show_bug.cgi?id=765830 ** Bug watch added: GNOME Bug Tracker #765830 https://bugzilla.gnome.org/show_bug.cgi?id=765830 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1578962 Title: nm-applet crashed with SIGABRT in g_assertion_message() Status in network-manager-applet package in Ubuntu: Triaged Status in network-manager-applet package in Debian: New Bug description: crashes every time using applet to switch from an openvpn connection back to wired connection ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri May 6 18:28:28 2016 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (34 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.0.0.138 dev eno1 proto static metric 100 10.0.0.0/24 dev eno1 proto kernel scope link src 10.0.0.61 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 IwConfig: eno1 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash RfKill: Signal: 6 SourcePackage: network-manager-applet StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nm-applet crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo wireshark nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 873b4698-101f-4f18-9d81-c10e6e1fda35 802-3-ethernet 1462523308 Fri 06 May 2016 18:28:28 AEST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/3 do.tim-richardson.net 57e9a26d-0ebd-4004-a599-df2a14d14344 vpn 1462523308 Fri 06 May 2016 18:28:28 AEST yes 0 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 873b4698-101f-4f18-9d81-c10e6e1fda35 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1578962/+subscriptions -- Mailing list: https://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 1576162] Re: network-manager crashes when exiting a vpn connection
Thanks. I tried that. But I seem to get no confirmation that any bug report has been submitted. On 30 April 2016 at 01:00, Sebastien Bacher <seb...@ubuntu.com> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. However, your crash report is either missing or > challenging to deal with as a ".crash" file. Please follow these > instructions to have apport report a new bug about your crash that can > be dealt with by the automatic retracer. > > If you are running the Ubuntu Stable Release you might need to enable > apport in /etc/default/apport and restart. > > Now open your file manager, navigate to your /var/crash directory and open > the crash report you wish to submit. > If this fails you will have to open a terminal and file your report with > 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash > is the crash you would like to report. If you get an error that you aren't > allowed to access this report you will have to file it with 'sudo > ubuntu-bug /var/crash/_my_crash_report.crash'. > > I'm closing this bug report since the process outlined above will > automatically open a new bug report which can then dealt with more > efficiently. Thanks in advance for your cooperation and understanding. > > ** Changed in: network-manager (Ubuntu) >Importance: Undecided => High > > ** Changed in: network-manager (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1576162 > > Title: > network-manager crashes when exiting a vpn connection > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576162/+subscriptions > -- Tim Richardson -- 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/1576162 Title: network-manager crashes when exiting a vpn connection Status in network-manager package in Ubuntu: Invalid Bug description: i have an openvpn connection configured. i use network manager to connect successfully. later i use nm to swap back to the wired connection. network-manager crashes, the icon is gone. however, the connection does change. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 28 21:11:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (26 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.0.0.138 dev eno1 proto static metric 100 10.0.0.0/24 dev eno1 proto kernel scope link src 10.0.0.61 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 IwConfig: eno1 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 2403ad62-b6bf-48d5-b00c-07f14220e73f 802-3-ethernet 1461841825 Thu 28 Apr 2016 21:10:25 AEST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/9 do.tim-richardson.net 57e9a26d-0ebd-4004-a599-df2a14d14344 vpn 1461841454 Thu 28 Apr 2016 21:04:14 AEST yes 0 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 2403ad62-b6bf-48d5-b00c-07f14220e73f /org/freedesktop/NetworkManager/ActiveConnection/9 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm']
[Desktop-packages] [Bug 1576162] [NEW] network-manager crashes when exiting a vpn connection
Public bug reported: i have an openvpn connection configured. i use network manager to connect successfully. later i use nm to swap back to the wired connection. network-manager crashes, the icon is gone. however, the connection does change. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 28 21:11:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (26 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.0.0.138 dev eno1 proto static metric 100 10.0.0.0/24 dev eno1 proto kernel scope link src 10.0.0.61 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 IwConfig: eno1 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 2403ad62-b6bf-48d5-b00c-07f14220e73f 802-3-ethernet 1461841825 Thu 28 Apr 2016 21:10:25 AEST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/9 do.tim-richardson.net 57e9a26d-0ebd-4004-a599-df2a14d14344 vpn 1461841454 Thu 28 Apr 2016 21:04:14 AEST yes 0 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 2403ad62-b6bf-48d5-b00c-07f14220e73f /org/freedesktop/NetworkManager/ActiveConnection/9 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "a crash file" https://bugs.launchpad.net/bugs/1576162/+attachment/4650037/+files/_usr_bin_nm-applet.1001.crash -- 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/1576162 Title: network-manager crashes when exiting a vpn connection Status in network-manager package in Ubuntu: New Bug description: i have an openvpn connection configured. i use network manager to connect successfully. later i use nm to swap back to the wired connection. network-manager crashes, the icon is gone. however, the connection does change. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 28 21:11:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (26 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.0.0.138 dev eno1 proto static metric 100 10.0.0.0/24 dev eno1 proto kernel scope link src 10.0.0.61 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 IwConfig: eno1 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 2403ad62-b6bf-48d5-b00c-07f14220e73f 802-3-ethernet
[Desktop-packages] [Bug 1564890] Re: additional user is created as disabled and there is no fix
Didn't know it was a button. This works. ** Changed in: unity-control-center (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1564890 Title: additional user is created as disabled and there is no fix Status in unity-control-center package in Ubuntu: Invalid Bug description: new install of 16.04 went to add a second admin user via the control center immediately after install the user can be created but password is not requested and the user is disabled. i could not progress via the control panel. i added a password from the shell. correct: new users should allow password setting and they should be enabled. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 1 23:44:07 2016 InstallationDate: Installed on 2016-04-01 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1564890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1564890] [NEW] additional user is created as disabled and there is no fix
Public bug reported: new install of 16.04 went to add a second admin user via the control center immediately after install the user can be created but password is not requested and the user is disabled. i could not progress via the control panel. i added a password from the shell. correct: new users should allow password setting and they should be enabled. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 1 23:44:07 2016 InstallationDate: Installed on 2016-04-01 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1564890 Title: additional user is created as disabled and there is no fix Status in unity-control-center package in Ubuntu: New Bug description: new install of 16.04 went to add a second admin user via the control center immediately after install the user can be created but password is not requested and the user is disabled. i could not progress via the control panel. i added a password from the shell. correct: new users should allow password setting and they should be enabled. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 1 23:44:07 2016 InstallationDate: Installed on 2016-04-01 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1564890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1385614] [NEW] network manager can not save imported openvpn configuration
Public bug reported: This is 14.04 32 bit intel. I have installed OpenVPN access server on another machine. It is configured with username and password security. By logging in to it, a configuration file can be downloaded. I want to set up a VPN network connection for this. So I go to the connections manager, choose to create a new VPN connection by importing a config file. The config file imports. But the the save button is disabled. A tooltip over the button asks me to authenticate, but there is no authentication dialog. A save button is often disabled if there is a required field missing. However, I need to choose password authentication which only requires a username (and a password). So all the fields I need are completed. But I can not save. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1385614 Title: network manager can not save imported openvpn configuration Status in “network-manager” package in Ubuntu: New Bug description: This is 14.04 32 bit intel. I have installed OpenVPN access server on another machine. It is configured with username and password security. By logging in to it, a configuration file can be downloaded. I want to set up a VPN network connection for this. So I go to the connections manager, choose to create a new VPN connection by importing a config file. The config file imports. But the the save button is disabled. A tooltip over the button asks me to authenticate, but there is no authentication dialog. A save button is often disabled if there is a required field missing. However, I need to choose password authentication which only requires a username (and a password). So all the fields I need are completed. But I can not save. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1385614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
this is a kernel bug. git bisect completed and reported on the upstream report https://bugs.freedesktop.org/show_bug.cgi?id=76520 -- 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/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux-meta” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
this is a kernel bug ** Package changed: lightdm (Ubuntu) = linux-meta (Ubuntu) -- 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/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux-meta” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
testing reveals that the bug is linked to lightdm It is not reproducible when lightdm is not running. When lightdm is running, a wide range of kernels show the resume fail. These kernels do not fail resume when lightdm is not running ** Description changed: does not resume (no backlight on LCD panel, for example) + seems to be caused by lightdm not by kernel; when + service lightdm stop + bug is not reproduced by pm-suspend + ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: katherine 1676 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: - TERM=linux - PATH=(custom, no user) + TERM=linux + PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-3.13.0-17-generic N/A - linux-backports-modules-3.13.0-17-generic N/A - linux-firmware 1.126 + linux-restricted-modules-3.13.0-17-generic N/A + linux-backports-modules-3.13.0-17-generic N/A + linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: - + dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA ** Package changed: linux (Ubuntu) = lightdm (Ubuntu) -- 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/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “lightdm” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure
Re: [Desktop-packages] [Bug 1287352] [NEW] screen does not wake after suspend always, intel
My bug message is bad. The bug reporting indicates that it is actually a kernel panic. Please close this bug. automatic bug reporting was fixed when I changed the login user to belong to group sudo. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290787 which are still marked incomplete although I have done what was asked and confirmed that various mainline kernels show the bug. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1287352 Title: screen does not wake after suspend always, intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1287352/+subscriptions -- 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/1287352 Title: screen does not wake after suspend always, intel Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: Hardware is *-display:0 description: VGA compatible controller product: Mobile GM965/GL960 Integrated Graphics Controller (primary) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 03 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 thi s is a problem after upgradeing from 13.10 to 14.04 beta. System has latest 14.04 updates After suspend, the screen does not resume. There is no backlighting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1287352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287352] [NEW] screen does not wake after suspend always, intel
Public bug reported: Hardware is *-display:0 description: VGA compatible controller product: Mobile GM965/GL960 Integrated Graphics Controller (primary) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 03 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 thi s is a problem after upgradeing from 13.10 to 14.04 beta. System has latest 14.04 updates After suspend, the screen does not resume. There is no backlighting. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- 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/1287352 Title: screen does not wake after suspend always, intel Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Hardware is *-display:0 description: VGA compatible controller product: Mobile GM965/GL960 Integrated Graphics Controller (primary) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 03 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 thi s is a problem after upgradeing from 13.10 to 14.04 beta. System has latest 14.04 updates After suspend, the screen does not resume. There is no backlighting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1287352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 782855] Re: missing pixels (horizontal lines) in font rendering
I have a Dell D420. The problem still exists in 12.10 although the fix from comment #24 has fixed the problem after I logged out and back in. tim@bach:~$ lspci -nn|grep -i vga 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) tim@bach:~$ -- 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/782855 Title: missing pixels (horizontal lines) in font rendering Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Fedora: New Bug description: Binary package hint: xserver-xorg-video-intel Since upgrading from Lucid to Natty, font rendering in firefox and some other apps is buggy. Certain letters in certain fonts will be missing pixels from horizontal lines through certain letters. For instance, in the screenshot I'm about to attach from this bug report, all the 'o' characters are missing a line through the center, and 'n' are missing a line a little below center. It's different every time: if I restart firefox, different letters will be affected. Graphics is Intel 915GM (on a Sony Vaio TX650). I don't know that it's the X driver at fault, but most people who see the problem seem to think that it's related to the video driver rather than the font rendering libraries. Changing my set of installed fonts or changing to a different default browser font can make the problem better or worse, but never makes it go away entirely. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1366x768 edid-base64: DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Sat May 14 18:16:31 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:81e2] Subsystem: Sony Corporation Device [104d:81e2] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) MachineType: Sony Corporation VGN-TX650P PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcKernelCmdLine: root=/dev/sda5 ro noplymouth Renderer: Unknown SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2005 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0031V1 dmi.chassis.type: 10 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0031V1:bd08/05/2005:svnSonyCorporation:pnVGN-TX650P:pvrJ0017EPV:cvn:ct10:cvr: dmi.product.name: VGN-TX650P dmi.product.version: J0017EPV dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 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/782855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 817013]
*** Bug 45416 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/817013 Title: [Upstream] bullet points change to rectangle glyphs after saving as docx and reopening Status in LibreOffice Productivity Suite: In Progress Status in “libreoffice” package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/817013/+attachment/2241146/+files/Bullet%20Bug.odt -O info.odt lowriter -nologo info.odt save as info.docx, close the file, and open info.docx and it looks as it does in info.odt. 4) What happens instead is the bullet points are replaced with rectangles in LO 3.3.2, and some other symbol in 3.3.3. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 Uname: Linux 2.6.38.3+ i686 Architecture: i386 Date: Wed Jul 27 10:24:48 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/817013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp