[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
On my end, I haven't been able to reproduce this so far with Ubuntu Appindicators disabled. It's very stable for me now. I am not 100% sure this is the fix for me, time will tell. But it's definitely more stable and possibly even fixed now. -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
@Daniel, I understand that you want to reproduce it. However, if you aren't experiencing this bug, then that tells me you don't have a hardware configuration that is affected by it. If you're affected, reproducing it is very easy - simply use the keyboard shortcut designated for switching up or down to another workspace. Every time I do this, I have a one in five chance of GNOME crashing. It's so common that I have no chance of NOT reproducing it. As for apps, if it matters, I only have Firefox, Thunderbird, and gnome- terminal open at any one time. -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
@Daniel, this bug has absolutely nothing to do with using an Android Emulator. I literally get this crash every five minutes, and I've never used emulation or virtualization of any kind on either of my machines. I think the Android Emulator was just a red herring. -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
Attached. ** Attachment added: "dump.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812527/+attachment/5242850/+files/dump.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787], often when running Androi
I think we need to completely remove Android Emulation from the title and description. I never use that, nor have I ever, and I see this crash constantly. It's EXTREMELY frustrating. What do you guys need from us in order to help us track this issue? I want to do what I can to help get this fixed. -- 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/1812527 Title: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787], often when running Android emulator (QEMU) Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] when running Android emula
Disabling animations seemed to resolve it for me too. But now switching workspaces just feels very odd without it. Since this is a regression (the bug was definitely not present at the time of initial release) I really hope this gets fixed. I have two systems with this problem. -- 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/1812527 Title: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] when running Android emulator (QEMU) Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812527] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] when running Android emula
I'm seeing this same problem, and on my end I am not using the Android emulator. The only apps I use on a regular basis that are always open are the following: firefox gnome-terminal thunderbird -- 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/1812527 Title: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] when running Android emulator (QEMU) Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732474] Re: Closing lid with external monitor plugged in sends system to sleep
Same issue here, on a Galago Pro laptop with an external monitor connected via HDMI. -- 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/1732474 Title: Closing lid with external monitor plugged in sends system to sleep Status in gnome-shell package in Ubuntu: Confirmed Bug description: On 17.04 I could close my laptop lid with an external monitor plugged in and the system would not sleep. After upgrading to 17.10 the system sleeps on lid close. If I boot with an external monitor attached, I can keep the lid closed and the system does not sleep, but if I disconnect and reconnect the monitor, the lid-close-suspend behaviour ensues. This is not a problem with the 'Suspend on lid close' option - if I disable this option, then regardless of whether an external monitor is plugged in or not, the system does not suspend. Furthermore, the gsettings options "org.gnome.settings-daemon.plugins.power lid-close- suspend-with-external-monitor" and "org.gnome.settings- daemon.plugins.power lid-close-ac-action" are "false" and "nothing" respectively. This seems to be related to the closed bug #1716160. My gnome- settings-daemon version is 3.26.1-0ubuntu5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718729] [NEW] Black screen with a few white pixels on Virtualbox VM
Public bug reported: I installed Ubuntu 17.04 from a daily image downloaded yesterday in a Virtualbox VM (Host Ubuntu version is 17.04). The installation works fine and without any issues. However, when I install all the updates and reboot, I am no longer able to log in. GDM doesn't start. Instead, I see a completely black screen with a few (one or two) white pixels. I am still able to SSH into the installation after this. Steps to reproduce: * Create a Virtualbox VM * Install Ubuntu 17.10 from daily image (I downloaded mine on 9/20/2017 @ 12:49pm Eastern) * Install all updates (sudo apt-get update && sudo apt-get dist-upgrade) * Reboot ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Sep 21 12:11:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=17aae2c8-ba3d-4c56-92cc-ab06d2c85d68 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful corruption regression reproducible 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/1718729 Title: Black screen with a few white pixels on Virtualbox VM Status in xorg package in Ubuntu: New Bug description: I installed Ubuntu 17.04 from a daily image downloaded yesterday in a Virtualbox VM (Host Ubuntu version is 17.04). The installation works fine and without any issues. However, when I install all the updates and reboot, I am no longer able to log in. GDM doesn't start. Instead, I see a completely black screen with a few (one or two) white pixels. I am still able to SSH into the installation after this. Steps to reproduce: * Create a Virtualbox VM * Install Ubuntu 17.10 from daily image (I downloaded mine on 9/20/2017 @ 12:49pm Eastern) * Install all updates (sudo apt-get update && sudo apt-get dist-upgrade) * Reboot ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Sep 21 12:11:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=17aae2c8-ba3d-4c56-92cc-ab06d2c85d68 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No
[Desktop-packages] [Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable
In my case, I am also using keepassxc. But I'm using the AppImage version rather than the Snap package. (The Snap version doesn't seem to be able to display a status/tray icon, while the AppImage version does). It's possible keepassxc is related, or it's a coincidence. -- 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/1508146 Title: alt + left/right arrows switch between tty consoles, cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable
I run into this problem every now and then. I am not sure what causes it. At the moment, this is not happening. I press ALT+Left/Right with no issue. But at some point this bug seems to appear. It's frustrating because ALT+Left in Firefox, for example, is a keyboard shortcut I use to go back a page. -- 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/1508146 Title: alt + left/right arrows switch between tty consoles, cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1627808] Re: Please enable e10s (multi-core CPU processing) support
@est31, that's great news. That means if Canonical doesn't disable this addon by default, Mozilla will. Should I submit a patch somewhere to remove this addon as a dependency? It seems to me that there's no value here, all it really does at this point is slow down the browser. I don't see any logical reason to include an addon by default that will only make people's experiences worse. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1627808 Title: Please enable e10s (multi-core CPU processing) support Status in Ubufox Extension: Confirmed Status in Ubuntu: Confirmed Status in ubufox package in Ubuntu: Confirmed Bug description: Would it be possible to determine whether this add-on is compatible with the e10s "electrolysis" feature of Firefox[1]? If it is, the manifest should say so: [2] This link may help when determining support: [3] Compatibility of this addon with e10s is required to enable the e10s feature, which brings many speedups and enhancements, on default configured ubuntu installations. Thank you! [1]: https://wiki.mozilla.org/Electrolysis [2]: https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#multiprocessCompatible [3]: https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubufox/+bug/1627808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Network Manager is the culprit, not anyone's routers. This is evident by the fact that earlier versions of Ubuntu didn't experience this issue, this issue happens regardless of which router we're connecting to, it happens regardless of which location we are at, and the underlying issue is that Network Manager cannot see ANY access points, not just the one we normally connect to. There is literally no scenario in which it is someone's router that is causing this. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Why do that? This is a bug with Network Manager, not our routers. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Again, you shouldn't need to restart network manager or the applet. You can simply rescan your wireless networks manually. sudo iwlist scan The applet should be doing this as soon as the machine wakes up, but it's clearly not. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
I still run into this problem from time to time. On my end, I resolve it by running the following command: sudo iwlist [wifi interface] scan Once I did that, it immediately connected. I'm under the impression that when resuming from suspend, Network Manager isn't automatically scanning for access points. -- 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/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
This is working for me now. When I import into Network Manager, it
literally tells me which line is the problem now, and whatever line that
is, I comment it out and it works. Before, it would just tell me that
there was an issue importing but it wasn't specific. But at least now,
Network Manager helps me figure out the issue. I recently switched to
Ubuntu GNOME, so I'm not sure if there's something specific with the
GNOME implementation that displays specific errors, or if Network
Manager has changed. At least it's working for me now, albeit with
manual intervention being required.
In my opinion, the real issue at this point is that even though
commenting out some lines helps, each line is valid and should be
accepted. If I export an .ovpn file and use it via the command line, it
works without issue (even without commenting out anything). In my view,
if the config file is valid enough for OpenVPN itself, it should surely
be valid for Network Manager. Perhaps the OpenVPN spec has updated and
Network Manager hasn't been updated to match?
--
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/606365
Title:
unable to import config with inlined ca, cert, key or tls-auth
Status in NetworkManager-OpenVPN:
Fix Released
Status in network-manager-openvpn package in Ubuntu:
Confirmed
Bug description:
Binary package hint: network-manager-openvpn-gnome
So a client of mine runs an OpenVPN setup. It exported a client.ovpn
file but it fails to completely import this file using the network-
manager (gnome) on Ubuntu 10.04.
When I import the file, it gives me the name ("client") and gateway
("vpn.example.org") on the initial screen. No other fields are
populated even though the client.ovpn file also includes a user
certificate, server certifikate and a private key.
When I go to advanced, some (most) of the settings obviously seem to
import correct, others not at all. E.g. none of the TLS settings (key
and key direction) are imported.
From what I understand I should be able to use this without any
additional settings.
The following software is installed through aptitude:
* openvpn (2.1.0)
* openvpn-blacklist
* network-manager-openvpn
* network-manager-openvpn-gnome
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638983] Re: Boot splash with luks password prompt broken after nvidia upgrade to 367
I am also facing this issue. I will either get the results mentioned here, or I'll see a password prompt, but keyboard support isn't accepted. For me, it also happened when installing the latest nvidia driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1638983 Title: Boot splash with luks password prompt broken after nvidia upgrade to 367 Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: Just got the nvidia driver update from 361 to 367. Upon reboot, the boot splash (plymouth?) with the password prompt for the encrypted root is missing. The screen flashes dark purple and the switches to black with a blinking cursor echoing anything typed. Ctrl-alt-del reboots. Booting with kernel options "quiet splash" removed results in a text-mode boot process where the password prompt is present, proceeding normally. Wasn't sure if this was plymouth or nvidia issue, I'm guessing nvidia because that's what upgraded and broke functionality. Tried redoing update-grub and update-initramfs, didn't help. Found I had both nvidia-361 and nvidia-367 installed (why didn't -361 uninstall?), but manually removing -361 (and redoing initramfs just in case) didn't change anything. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-367 367.57-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 3 17:45:14 2016 InstallationDate: Installed on 2016-07-23 (103 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nvidia-graphics-drivers-367 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1638983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Running 'sudo iw dev wlan0 scan' does work around the issue for me. I have this issue on two computers, they have the following wireless cards from Intel: Intel Wireless 7260 (rev bb) Intel Wireless 7260 (rev 73) Just to be clear, should I be creating a new bug for each of these two cards? Would this be the 'linux' package, or 'iwlwifi'? -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
Same problem here, all current updates. -- 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Confirmed Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Confirmed Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [SRU for Ubuntu 16.04] Package (yakkety): xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 Current (xenial): xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Debian Changelog (since 2:2.99.917+git20160325-1ubuntu1)] xserver-xorg-video-intel (2:2.99.917+git20160706-1ubuntu1) yakkety; urgency=medium * Merge from Debian. xserver-xorg-video-intel (2:2.99.917+git20160706-1) unstable; urgency=medium * New upstream snapshot. * fix-fd-leak-when-intel-scrn-create-fails.diff, sna-let-modesetting- handle-gen9+.diff: Dropped as the fallback to modesetting will be fully handled in the xserver. * .docs: Include a minimal xorg.conf. xserver-xorg-video-intel (2:2.99.917+git20160522-1ubuntu1) yakkety; urgency=medium * Merge from Debian. * install-dri3info.diff: Install dri3info with the driver, add libxcomposite-dev to build-depends. xserver-xorg-video-intel (2:2.99.917+git20160522-1) unstable; urgency=medium * New upstream snapshot. (Closes: #823116) * fix-fd-leak-when-intel-scrn-create-fails.diff: Fix a failure falling back on another driver when scrn create fails. [Regression Potential] Regression potential here seems minimal. However, as seen in the above Debian changelog, we have a new snapshot which includes several changes since March 25. === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1522922] Re: Screen flickering in Intel i915 driver
I found something interesting that may or may not be valuable. From what I can gather so far, we're dealing with two flicker issues. One affects only Ubuntu MATE, the other affects regular Ubuntu as well. For me, I've been able to work around the problem in Ubuntu MATE by disabling tlp.service and rebooting. After I do this, I no longer deal with any flickering at all whatsoever. This work around won't work for everyone, but if you are hitting the bug in Ubuntu MATE (since Ubuntu MATE features tlp.service by default) this may work for you. Even though disabling tlp.service fixes it for me, this is still a kernel bug, because I can also fix this issue by side-loading an unsupported kernel without disabling tlp.service and that fixes it too. For whatever reason, tlp.service is triggering something in the kernel causing a flicker. -- 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/1522922 Title: Screen flickering in Intel i915 driver Status in Nouveau Xorg driver: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Triaged Bug description: There's an upstream bug reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393 that causes screen flickering when using the Intel i915 builtin driver (at resolutions lower than the maximal one). I think that it will be fixed in newer kernel versions, but for the time being, as reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393#c25 (and as personally tested) reverting those two commits fixes the problem. Would that be possible to release a fixed version for the 4.2.0 stream? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bettini1378 F pulseaudio /dev/snd/controlC1: bettini1378 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 4 19:01:00 2015 HibernationDevice: RESUME=UUID=7ddbc972-3ad6-40de-9313-2bb9395145f9 InstallationDate: Installed on 2015-05-08 (210 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=dd2c7064-53b9-4720-96ab-5e8a3f2db3ea ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-07 (26 days ago) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1522922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
I'm unsubscribing from this bug. This is ridiculous. This bug will NEVER be solved because everyone assumes that each type of crash is a different bug, refusing to believe the possibility that one single bug can affect different chipsets/hardware in different ways (completely freezing some, but not others). Until this bug gets high-level Canonical attention, the only hope anyone has is for an upstream fix to magically come down in the updates and solve it, assuming of course this isn't Ubuntu-specific. Good luck everyone. -- 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/993187 Title: ubuntu 12.04 completely freezes frequently. Status in “linux” package in Ubuntu: Won't Fix Status in “xserver-xorg-video-intel” package in Ubuntu: Won't Fix Status in “linux” source package in Precise: Won't Fix Status in “xserver-xorg-video-intel” source package in Precise: Won't Fix Bug description: Update: 6/12/2012 This bug is about a complete system lock-up. No other TTYs can be started. Mouse doesn't move. Keyboard doesn't react. The only solution is hard reset. Seems to happen on a variety of configurations, including nVidia, ATI and Intel graphics. If you are still able to TTY or SSH into other sessions, move the mouse or use the keyboard, file another bug. Thx. Joris V. (brains). Update: 5/21/2012 Updating the kernel to 3.3.6 as suggested by Michael in #91, the system seems stable, no freezes yet in 5-6 hrs of using and watching videos for couple of hrs. Original description: I recently installed newly released ubuntu 12.04 LTS 64 bit version on my desktop. And it is frequently freezing, for the first few hours it ran smoothly and when I started watching videos it started freezing randomly. I have to use hard restart every time. Initially it was only during videos but now even during normal browsing it is freezing. I am using on board graphics and do not have any graphics card installed. Can someone please help me here, I really love the new looks of 12.04 and it bugs me not being able to use :( Below is my hardware configuration: Processor: Intel CORE i3 processor (2nd generation) Board: Intel® Desktop Board DH67BL Ram: 4GB Graphics: On board HDD: 500 GB Please let me know if you need more information, or any specific logs I can capture (and how). Thanks, Ketan Patil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063969] Re: NVIDIA does not work with framebuffer drivers
I think the biggest issue with this bug is that without the splash screen, I see errors and ugly all over the screen. It doesn't bother me personally, because my system works fine. But to a new or inexperienced user, this may make them think something is wrong. At the very least, this error text needs to be hidden. Users should NEVER see such things unless they press tab or escape to show boot messages. I don't care if it's just a blank screen for now, but at least hide the messages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1063969 Title: NVIDIA does not work with framebuffer drivers Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Quantal: Won't Fix Bug description: On my Latitude E6420 running Kubuntu 12.10 (64-bit) with all updates, there is no splash screen. Instead, I just see text. This laptop has Nvidia graphics, though Optimus is disabled so that is not the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plymouth 0.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 13:57:54 2012 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1063969/+subscriptions -- Mailing list: https://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 1063969] Re: NVIDIA does not work with framebuffer drivers
@Tim, I wish that were the case for me. On 11/23/2012 06:50 PM, Tim wrote: Jeremy, you should actually be getting a text-based splash screen, when plymouth can't access a framebuffer. -- Jay LaCroix A+, Network+, Server+, Linux+, Novell CLA, LPIC-1 (P) 248.520.4062 (E) j...@jaylacroix.com http://www.jaylacroix.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1063969 Title: NVIDIA does not work with framebuffer drivers Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Quantal: Won't Fix Bug description: On my Latitude E6420 running Kubuntu 12.10 (64-bit) with all updates, there is no splash screen. Instead, I just see text. This laptop has Nvidia graphics, though Optimus is disabled so that is not the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plymouth 0.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 13:57:54 2012 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1063969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063969] Re: NVIDIA does not work with framebuffer drivers
@Tim, I just checked and it appears to be shut down that shows errors, the errors in startup go by so fast I cannot read them. Is that a known issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1063969 Title: NVIDIA does not work with framebuffer drivers Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Quantal: Won't Fix Bug description: On my Latitude E6420 running Kubuntu 12.10 (64-bit) with all updates, there is no splash screen. Instead, I just see text. This laptop has Nvidia graphics, though Optimus is disabled so that is not the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plymouth 0.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 13:57:54 2012 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1063969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063969] Re: No Plymouth Splash on Latitude E6420
As for me, I don't see it during boot or shutting down. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1063969 Title: No Plymouth Splash on Latitude E6420 Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Quantal: Triaged Bug description: On my Latitude E6420 running Kubuntu 12.10 (64-bit) with all updates, there is no splash screen. Instead, I just see text. This laptop has Nvidia graphics, though Optimus is disabled so that is not the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: plymouth 0.8.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 13:57:54 2012 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1063969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062377] [NEW] Grammatical Errors in Jockey-KDE
Public bug reported: When I was in the process of installing a proprietary driver, I saw some grammatical errors (missing spaces) in the explanation text. See screenshot. Examples include modulerequired, ofthe, and accelerationfor. Possibly others. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: jockey-kde 0.9.7-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:34:09 2012 InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1062377 Title: Grammatical Errors in Jockey-KDE Status in “jockey” package in Ubuntu: New Bug description: When I was in the process of installing a proprietary driver, I saw some grammatical errors (missing spaces) in the explanation text. See screenshot. Examples include modulerequired, ofthe, and accelerationfor. Possibly others. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: jockey-kde 0.9.7-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:34:09 2012 InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1062377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062377] Re: Grammatical Errors in Jockey-KDE
** Attachment added: snapshot1.png https://bugs.launchpad.net/bugs/1062377/+attachment/3376362/+files/snapshot1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1062377 Title: Grammatical Errors in Jockey-KDE Status in “jockey” package in Ubuntu: New Bug description: When I was in the process of installing a proprietary driver, I saw some grammatical errors (missing spaces) in the explanation text. See screenshot. Examples include modulerequired, ofthe, and accelerationfor. Possibly others. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: jockey-kde 0.9.7-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:34:09 2012 InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Beta amd64 (20121004) MachineType: Dell Inc. Latitude E6420 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=20af3c8e-df88-479d-bc6f-da96a47b5fdf ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0PH12P dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0PH12P:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1062377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
