[Desktop-packages] [Bug 1884437] Re: Windows are resized and reordered upon resume from lock or suspend
It's still doing it with the same process ID. I switched DP cables-- perhaps it's a bad port on the board or display... I'll look into it further. Thanks for your assistance! -- 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/1884437 Title: Windows are resized and reordered upon resume from lock or suspend Status in gnome-shell package in Ubuntu: Incomplete Bug description: After a resume from a lock/suspend, windows sizes are changed, fonts are incorrect sizes (until mouse over), and windows have moved from the secondary monitor to the primary monitor. This happens every time the displays have been off (from a suspend or lock screen). AMD graphics with dual 4K displays. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 07:46:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: asus-wmi-sensors, b6c25d2, 5.4.0-21-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-33-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-37-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1462:3680] InstallationDate: Installed on 2020-03-07 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xbqp91@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_xbqp91 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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+git20200226-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/gnome-shell/+bug/1884437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884437] [NEW] Windows are resized and reordered upon resume from lock or suspend
Public bug reported: After a resume from a lock/suspend, windows sizes are changed, fonts are incorrect sizes (until mouse over), and windows have moved from the secondary monitor to the primary monitor. This happens every time the displays have been off (from a suspend or lock screen). AMD graphics with dual 4K displays. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 07:46:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: asus-wmi-sensors, b6c25d2, 5.4.0-21-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-33-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-37-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1462:3680] InstallationDate: Installed on 2020-03-07 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xbqp91@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_xbqp91 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884437 Title: Windows are resized and reordered upon resume from lock or suspend Status in xorg package in Ubuntu: New Bug description: After a resume from a lock/suspend, windows sizes are changed, fonts are incorrect sizes (until mouse over), and windows have moved from the secondary monitor to the primary monitor. This happens every time the displays have been off (from a suspend or lock screen). AMD graphics with dual 4K displays. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 07:46:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: asus-wmi-sensors, b6c25d2, 5.4.0-21-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-33-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-37-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1)
[Desktop-packages] [Bug 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen
This happens to me as well. I too have two monitors, and sometimes the menu is even on the wrong monitor. Oddly enough, if I click off then right-click again (right away), the menu appears correctly. It's almost as if it is triggered by not being invoked after x amount of time. -- 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/1780790 Title: Menus, tooltips and dropdowns are often misplaced on screen Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: I've noticed a few problems with misplaced elements in firefox UI that I am not sure are all the same bug: - In what appears to be random chance tooltips and menus are often misplaced on screen. It's common but not fully reproducible. What I see is right-clicking an element on a page or hovering over a link and having the menu/tooltip show up somewhere different on the page. Doing it again immediately after often results in it appearing in the right place the second time. - When using an external screen placed on top of the internal one with firefox maximized on the internal screen the URL bar's dropdown would consistently appear on the external screen, completely outside the firefox window, instead of the normal location Let me know what extra information is needed do diagnose this. I'm running gnome-shell and have used both Xorg and Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr2259 F pulseaudio BuildID: 20180703115938 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 15:00:50 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 600 169.254.0.0/16 dev tun0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623 PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1780790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868896] Re: Minimized windows reappear when closing the overview
Thanks for your quick response on this! So awesome! -- 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/1868896 Title: Minimized windows reappear when closing the overview Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I just ran all of the updates for 20.04 on two machines, and both machines experience the same issue. Items do not appear to stay "minimized". For instance, you can minimize Thunderbird, and it appears to re-maximize itself. However, you cannot click on anything in the maximized window, but you can re- minimize it (that button does work), then click the dock to bring it back out and it functions properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 18:11:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-03-11 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311) MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.6 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-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/gnome-shell/+bug/1868896/+subscriptions -- Mailing list: https://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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f
Mine does EVERYTHING EXACTLY as you just mentioned. Sent from my iPhone > On Jan 4, 2019, at 3:25 AM, Benjamin Schmid <1748...@bugs.launchpad.net> > wrote: > > @vanvugt Seeing this VERY regularly in cosmic, too. Just came back here > to re-check the status of this long-term annoying issue. > > The fact is, that gnome shell provides me a VERY poor UX experience: > > Logged out for the session more than 10mins? Type your password and go > get take a coffee, because it literally takes 1-2 minutes until the > session finally crashes and restarts. Before my PC it literally > unusable. Sometimes I also switch to the login screen and re-login into > my running session to somehow provoke the crash to get it usable. > > Ah – and by the way: On some occassions lockscreen does not work and > expose the clickable (!) left sidebar. In this case I only can unlock > via the login-screen way to crash the session. > > Also commonly in normal operation the left sidebar looks strangely > sized. Then I need to type "r" to restart the shell to resume normal > operation. > > Feels really like an old, nearly dying device … > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1755163). > https://bugs.launchpad.net/bugs/1748450 > > Title: > gnome-shell crashed with SIGTRAP in _g_log_abort() from > g_log_default_handler() from default_log_handler(message="Connection > to xwayland lost") from g_logv() from g_log() from > > Status in gnome-shell package in Ubuntu: > Invalid > Status in mutter package in Ubuntu: > Fix Released > Status in gnome-shell source package in Bionic: > Invalid > Status in mutter source package in Bionic: > Fix Released > > Bug description: > [Impact] > > * Xwayland is failing frequently (not crashing), which triggers a > crash in gnome-shell because gnome-shell doesn't know how to survive > after Xwayland has reset itself. > > * The frequent gnome-shell crashes create frequent problem reports and > annoying dialogs for users, after they log in to an apparently working > gnome-shell. > > * This affects Xorg sessions too, because the gdm login screen itself > is a Wayland session. And Xorg users will see the problem dialog after > they have logged into a Xorg session. > > * The fix simply converts the crash into a silent exit (as decided by > Gnome upstream). This avoids the mountain of crash reports and > annoying error dialogs at least. It does not fix the root causes that > remain in Xwayland, but this is considered acceptable because there > really isn't a bug in gnome-shell here other than it doesn't know how > to survive without a connection to Xwayland. > > * For users of Xorg sessions, like bionic default, this is a full fix > as Xorg users will never get an Xwayland instance after logging in. > And hence the Xwayland bugs are irrelevant. > > [Test Case] > > * Just install bionic, use it lightly and reboot a few times. > > * Observe crash files are left in /var/crash and problem report > dialogs after logging in. > > [Regression Potential] > > Medium. The fix does not really change the structure of the existing > error handling, only changes it from a core dump into a silent exit. > For Xorg users this should be invisible as the affected login screen > restarts automatically. > > [Other Info] > > This is a whole class of gnome-shell crash which includes bug 1505409, bug > 1748450 and bug 1556601. All three should be considered the same crash for > the sake of this SRU. Just don't mark them as duplicates of each other > because they are all still collecting duplicates of their own. > > - > > *** This is a duplicate of bug 1505409, but is being kept separate so > as to automatically collect duplicate reports since the stacktrace > signature has changed recently. Any resolution and discussion should > occur in bug 1505409. *** > > See also: > https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 > > ProblemType: Crash > DistroRelease: Ubuntu 18.04 > Package: gnome-shell 3.26.2-0ubuntu2 > ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 > Uname: Linux 4.13.0-33-generic x86_64 > ApportVersion: 2.20.8-0ubuntu8 > Architecture: amd64 > CurrentDesktop: GNOME-Greeter:GNOME > Date: Thu Feb 8 23:50:23 2018 > DisplayManager: gdm3 > ExecutablePath: /usr/bin/gnome-shell > GsettingsChanges: > > InstallationDate: Installed on 2016-03-21 (690 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) > ProcCmdline: /usr/bin/gnome-shell > ProcEnviron: > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/false > Signal: 5 > SourcePackage: gnome-shell > StacktraceTop: > () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 > _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 > _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 > XPending () at
Re: [Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I didn’t need to remove GDM3, but installing LightDM (and switching to it) fixed it for me. Well, I should say it was a workaround, anyway... > On Oct 24, 2018, at 11:56 PM, ccdisle wrote: > > Uncommenting "WaylandEnable=false " worked. > > Removing gdm3 did not work, I just got redirected to a tty3 login shell. > > Thanks again > > -- > You received this bug notification because you are subscribed to the bug > report. > 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 -- 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 1752053] Re: nvidia-390 fails to boot graphical display
I upgraded from 17.10 to 18.04. It wouldn't log in, but through ssh I purged the nvidia drivers, installed 396 through the PPA, rebooted, and it came up and worked. It is a tower with GTX 1060. -- 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 1752053] Re: nvidia-390 fails to boot graphical display
I hear Pop!_OS 18.04 doesn't have this issue. I'm unfortunately about to give up on Ubuntu and give that a try. Some word of reassurance from the Ubuntu team here would be nice. Where they marked this as fixed, I'm not hopeful of a fix--at least anytime soon. If anyone has found a true and simple workaround, please let us know! Otherwise, I think my hardware will require me to look somewhere else... -- 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 1752053] Re: nvidia-390 fails to boot graphical display
At the top of this page it says "Fix Released". Does anyone know to to get them to change the status to an open bug and re-evaluate it? It's clearly not fixed. -- 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 1752053] Re: nvidia-390 fails to boot graphical display
Hopeful this bug was fixed (as it improperly states above), I did a fresh install on my machine with an Nvidia 1060. It will boot, then go to a black screen on login, etc. I tried what people mentioned above, but was not able to get a stable working system. I went back to 17.10 and have not had any issues since. -- 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
