[Desktop-packages] [Bug 2060350] Re: all windows under gnome shell lack the close, minimize and maximize buttons
I seem to have fixed this, the gnome-session package was missing on my machine (uninstalled by the dependency issue that ensued due to the archive rebuild) -- 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/2060350 Title: all windows under gnome shell lack the close, minimize and maximize buttons Status in gnome-shell package in Ubuntu: New Bug description: Using gnome-shell 46 on noble, no window seems to be rendering the close, maximize and minimize buttons. Trying to click in the top right corner to look for buttons that are transparent yielded no result. The buttons seem to not be present at all. I have tried to reinstall gnome-shell-common since a forum post indicates that it contains the assets required to draw those buttons, but it was all in vain. As a workaround I am riht clicking on the window title/headerbars to reveal the context menu with which I can close the window successfully. This seems to be related to the issue where gdm3 is not drawing the login widgets at all (switched to sddm to workaround). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu3.1 Uname: Linux 6.8.4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu Date: Sat Apr 6 11:22:19 2024 DisplayManager: sddm InstallationDate: Installed on 2016-02-19 (2969 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-03-29 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060350/+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 2060349] [NEW] gdm3 launches without any login widgets
Public bug reported: When the "login screen" it is just a black screen with the top bar (all parts of it work). The user choser and the widgets for typing in the password are completely missing. I have reinstalled the gnome-shell-common package (indicated in a forum post) to no avail. For now I have resorted to using sddm (with breeze) to have a functional login greeter, but doing this I have lost the gdm3 to gnome-shell integration such as smooth screen locking etc. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 Uname: Linux 6.8.4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu Date: Sat Apr 6 11:16:00 2024 InstallationDate: Installed on 2016-02-19 (2969 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-03-29 (8 days ago) mtime.conffile..etc.gdm3.custom.conf: 2023-05-14T10:31:50.512916 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2060349 Title: gdm3 launches without any login widgets Status in gdm3 package in Ubuntu: New Bug description: When the "login screen" it is just a black screen with the top bar (all parts of it work). The user choser and the widgets for typing in the password are completely missing. I have reinstalled the gnome-shell-common package (indicated in a forum post) to no avail. For now I have resorted to using sddm (with breeze) to have a functional login greeter, but doing this I have lost the gdm3 to gnome-shell integration such as smooth screen locking etc. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 Uname: Linux 6.8.4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu Date: Sat Apr 6 11:16:00 2024 InstallationDate: Installed on 2016-02-19 (2969 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-03-29 (8 days ago) mtime.conffile..etc.gdm3.custom.conf: 2023-05-14T10:31:50.512916 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060349/+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 2060350] [NEW] all windows under gnome shell lack the close, minimize and maximize buttons
Public bug reported: Using gnome-shell 46 on noble, no window seems to be rendering the close, maximize and minimize buttons. Trying to click in the top right corner to look for buttons that are transparent yielded no result. The buttons seem to not be present at all. I have tried to reinstall gnome-shell-common since a forum post indicates that it contains the assets required to draw those buttons, but it was all in vain. As a workaround I am riht clicking on the window title/headerbars to reveal the context menu with which I can close the window successfully. This seems to be related to the issue where gdm3 is not drawing the login widgets at all (switched to sddm to workaround). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu3.1 Uname: Linux 6.8.4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu Date: Sat Apr 6 11:22:19 2024 DisplayManager: sddm InstallationDate: Installed on 2016-02-19 (2969 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-03-29 (8 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages -- 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/2060350 Title: all windows under gnome shell lack the close, minimize and maximize buttons Status in gnome-shell package in Ubuntu: New Bug description: Using gnome-shell 46 on noble, no window seems to be rendering the close, maximize and minimize buttons. Trying to click in the top right corner to look for buttons that are transparent yielded no result. The buttons seem to not be present at all. I have tried to reinstall gnome-shell-common since a forum post indicates that it contains the assets required to draw those buttons, but it was all in vain. As a workaround I am riht clicking on the window title/headerbars to reveal the context menu with which I can close the window successfully. This seems to be related to the issue where gdm3 is not drawing the login widgets at all (switched to sddm to workaround). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu3.1 Uname: Linux 6.8.4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu Date: Sat Apr 6 11:22:19 2024 DisplayManager: sddm InstallationDate: Installed on 2016-02-19 (2969 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-03-29 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060350/+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 2017677] Re: Unable to drag window by title bar
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 If you toggle maximised state with Super+Up or move left or right with Super+Left or Super+Right the window gets focused and dragging works again until you click inside a window again. -- 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/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+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 2017677] Re: Unable to drag window by title bar
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 I had been using 23.04 for over a month since the beta. This only started happening on my PC today. What happened? This is incredibly annoying :/ -- 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/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+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 1967628] [NEW] Compression dialog not large enough, it truncates the popover for archive type when opened
Public bug reported: When trying to change the archive type in the nautilus compression dialog I noticed that the popover that pops up is huge and gets truncated by the small dialog window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 Uname: Linux 5.17.1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 21:00:10 2022 InstallationDate: Installed on 2016-02-19 (2233 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-30 (3 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "screenshot showing the truncation" https://bugs.launchpad.net/bugs/1967628/+attachment/5576236/+files/truncated%20compress.png ** Description changed: When trying to change the archive type in the nautilus compression - dialog I noticed that the combo box that pops up is huge and gets + dialog I noticed that the popover that pops up is huge and gets truncated by the small dialog window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 Uname: Linux 5.17.1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 21:00:10 2022 InstallationDate: Installed on 2016-02-19 (2233 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-30 (3 days ago) ** Summary changed: - Compression dialog not large enough, it truncates the drop down for archive type when opened + Compression dialog not large enough, it truncates the popover for archive type when opened -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1967628 Title: Compression dialog not large enough, it truncates the popover for archive type when opened Status in nautilus package in Ubuntu: New Bug description: When trying to change the archive type in the nautilus compression dialog I noticed that the popover that pops up is huge and gets truncated by the small dialog window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 Uname: Linux 5.17.1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 21:00:10 2022 InstallationDate: Installed on 2016-02-19 (2233 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-30 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967628/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
The issue happens if both Dash to Panel and Ubuntu Dock are enabled at teh same time. Having only one of them active does not trigger the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Invalid Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I actually use Dash to Panel instead of the Ubuntu Dock. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I use X11 with proprietary nvidia graphics. I will test with the other user accoutn on this machine which has way less setting changes than my account. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I think I found out the cause, I had Ubuntu Dock enabled while having Dash to Panel enabled. Ubuntu Dock may have been turned on during upgrade (as I had turned it off months ago). I'll keep testing and report back after going through a logout/login and a full reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I have uninstalled nautilus (purge option) and reinstalled. The issue persists on my machine. Is there anything I can give you to help out? Logs or settings files etc.? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
Should I try to "reinstall" nautilus? Remove it including settings and install it anew, and see if it triggers again? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
@seb128 Will this make it for the Beta builds due today? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
This fiddling solves the problem momentarily. Logging out and in again puts me back to square one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I keep adding and removing the "--new-window" parameter in the Exec line. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+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 1944412] [NEW] Nautilus keeps spawning new window when clicking on the launcher icon
Public bug reported: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. Thsi - shoudl only happen if I manually select the "new window" action. THe + shoudl only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are - isnatnces already running. Hovering on the launcher icon should also + instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right - behaviour back if I keep fiddlign with the nautilus .desktop file but + behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) ** Summary changed: - Nautilus keeps spawnign new window when clicking on the launcher icon + Nautilus keeps spawning new window when clicking on the launcher icon ** Description changed: When clicking on the launcher icon for nautilus, new instances keep - being started even when I had already launched an instance before. Thsi - shoudl only happen if I manually select the "new window" action. The + being started even when I had already launched an instance before. This + should only happen if I manually select the "new window" action. The past behaviour was to restore back the last window used if there are instances already running. Hovering on the launcher icon should also show running instances but this no longer works. I can get the right behaviour back if I keep fiddling with the nautilus .desktop file but the bad behavior returns again if I restart my session without changing the .desktop file again. Please look into this as it got old really fast after upgrade. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] Uname: Linux 5.14.6 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 09:42:49 2021 InstallationDate: Installed on 2016-02-19 (2040 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-09-18 (2 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon Status in nautilus package in Ubuntu: New Bug description: When clicking on the launcher icon for nautilus, new instances keep being started even when I had already launched an instance before. This should only happen if I manually select the "new window" a
[Desktop-packages] [Bug 1848138] [NEW] nvidia on-demand switching to llvmpipe
Public bug reported: On a zenbook-pro 2nd generation laptop (intel graphics w/ GTX1050TI) switching to on-demand mode (nvidia-435, 19.10) yields better battery life but using llvmpipe instead of intel graphics. Offloading to the nvidia driver does not work but instead yields an error. Using intel mode yields a non working GUI. ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848138 Title: nvidia on-demand switching to llvmpipe Status in nvidia-prime package in Ubuntu: New Bug description: On a zenbook-pro 2nd generation laptop (intel graphics w/ GTX1050TI) switching to on-demand mode (nvidia-435, 19.10) yields better battery life but using llvmpipe instead of intel graphics. Offloading to the nvidia driver does not work but instead yields an error. Using intel mode yields a non working GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848138/+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 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
So after upgrading, I cannot see any abnormal rise in memory consumption. I'm glad I risked it and upgraded. I do not use zsh and am using the latest stable kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/ and the latest available nvidia driver from https://launchpad.net/~graphics-drivers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 Status in mutter package in Ubuntu: Incomplete Bug description: Mutter is hanging for multiple seconds (5 or so) at random times, especially when your user session starts and you open new applications from the launcher: - the screen freeze (apps & Shell) completely - you have a second cursor that you can move and refresh during that period It seems that disabling drm nvidia support prevent the issue from happening so far. More update if it's not the case anymore. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 10:21:09 2019 InstallationDate: Installed on 2018-05-24 (315 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-01-08 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+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 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
Would I encounter this bug if I upgrade to disco? I have an nvidia GPU, nvidia_modeset module is shown in lsmod but I have not set "nvidia-drm.modeset=1" in the kernel command line. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 Status in mutter package in Ubuntu: New Bug description: Mutter is hanging for multiple seconds (5 or so) at random times, especially when your user session starts and you open new applications from the launcher: - the screen freeze (apps & Shell) completely - you have a second cursor that you can move and refresh during that period It seems that disabling drm nvidia support prevent the issue from happening so far. More update if it's not the case anymore. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 10:21:09 2019 InstallationDate: Installed on 2018-05-24 (315 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-01-08 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+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 1815550] Re: [nvidia] gnome-shell RSS grows without limit, general slowness
Is this only on disco or is it observed on prior versions? I was planning to upgrade and have two systems with nvidia GPUs. On cosmic I cannot see the resident memory grow as described above. -- 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/1815550 Title: [nvidia] gnome-shell RSS grows without limit, general slowness Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Disco: Confirmed Bug description: This *may* be an nvidia-specific problem, but the RSS of gnome-shell on my system grows without limit (over a couple of hours it's increased past 10G). At the same time, gnome-shell appears to become progressively less responsive. Restarting gnome-shell (via restart) drops shell RSS down to ~400MB and improves system responsiveness a bit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 4.20.0 Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 13:35:59 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1815550/+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 1788113] Re: After recent update, still cannot switch to intel mode
Due to bad interactions with gdm (namely gnome shell process under gdm user consuming a whole logical core), I had to move to lightdm. I will try with it and report back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: Fix Released Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+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 1763978] Re: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
I get the same thing with kernel 4.18.x. The current implementation of the service fails on muxless optimus. Also if one turns off the GPU using /sys/bus/pci, GDM will still not boot up even if the prime boot service would succeed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1763978 Title: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Since this week (i believe April 9th) Nvidia-prime isn't working for me. Running: Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic Nvidia-prime version: Nvidia-prime version: Installed: 0.8.7 Candidate: 0.8.7 Version table: *** 0.8.7 500 Error code: apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1763978/+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 1788113] Re: After recent update, still cannot switch to intel mode
After some research I found that vgaswitcheroo is not support on muxless optimus laptops. Can the ca;; to /sys/kernel/debug/cgaswitcheroo/switch be skipped when the patch does not exist? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: New Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+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 1788113] Re: After recent update, still cannot switch to intel mode
This looks like vgaswitcheroo is running a sript accessing a path that does not exist in sysfs. I am using vanilla kernels while testing this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: New Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+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 1788113] Re: After recent update, still cannot switch to intel mode
This is what I get when running "systemctl status nvidia-prime-boot.service": ● nvidia-prime-boot.service - dGPU off during boot Loaded: loaded (/lib/systemd/system/nvidia-prime-boot.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2018-08-26 09:41:25 CEST; 3min 12s ago Process: 831 ExecStart=/bin/sh -c echo OFF > /sys/kernel/debug/vgaswitcheroo/switch (code=exited, status=2) Main PID: 831 (code=exited, status=2) Aug 26 09:41:25 zenbook-pro systemd[1]: Starting dGPU off during boot... Aug 26 09:41:25 zenbook-pro sh[831]: /bin/sh: 1: cannot create /sys/kernel/debug/vgaswitcheroo/switch: Directory nonexistent Aug 26 09:41:25 zenbook-pro systemd[1]: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Aug 26 09:41:25 zenbook-pro systemd[1]: nvidia-prime-boot.service: Failed with result 'exit-code'. Aug 26 09:41:25 zenbook-pro systemd[1]: Failed to start dGPU off during boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: New Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+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 1788113] Re: After recent update, still cannot switch to intel mode
I did not manage to find a vgaswitcheroo directiory in /sys/kernel/debug. Is that supposed to be somewhere else? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: New Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+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 1788113] Re: After recent update, still cannot switch to intel mode
This is what systemd gives: Aug 21 08:56:37 zenbook-pro systemd[1]: Starting dGPU off during boot... Aug 21 08:56:37 zenbook-pro systemd[1]: Failed to start dGPU off during boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: New Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+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 1788113] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1788113/+attachment/5178447/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: New Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+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 1788113] [NEW] After recent update, still cannot switch to intel mode
Public bug reported: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Tags added: apport-collected bionic ** Description changed: - If I try to switch to intel mode on my Zenbook Pro UX550 and then - reboot, I end up without a graphical session. GDM does not start even if - it seems to be trying to for many times. I see a systemd message that - the dGPU could not be switched off. Also, I get a flickery screen on - TTYs until GDM gives up with the screen alternating between the TTY and - teh systemd textual log. Once that stops flashing I manage to prim-elect - nvidia and reboot cleanly. This is certianly better than before teh - update but it does not fix the situation fully. I am using bionic with - all updates applied. + If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and teh systemd textual log. Once that stops flashing I manage to prim-elect nvidia and reboot cleanly. This is certianly better than before teh update but it does not fix the situation fully. I am using bionic with all updates applied. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.3 + Architecture: amd64 + CurrentDesktop: GNOME + Dependencies: + + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-10-02 (322 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) + NonfreeKernelModules: nvidia_modeset nvidia + Package: nvidia-prime 0.8.8 + PackageArchitecture: all + Tags: bionic + Uname: Linux 4.18.3-041803-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: New Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+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.lau
[Desktop-packages] [Bug 1788113] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1788113/+attachment/5178448/+files/ProcEnviron.txt ** Description changed: - If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and teh systemd textual log. Once that stops flashing I manage to prim-elect nvidia and reboot cleanly. This is certianly better than before teh update but it does not fix the situation fully. I am using bionic with all updates applied. - --- + If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: - + DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788113 Title: After recent update, still cannot switch to intel mode Status in nvidia-prime package in Ubuntu: New Bug description: If I try to switch to intel mode on my Zenbook Pro UX550 and then reboot, I end up without a graphical session. GDM does not start even if it seems to be trying to for many times. I see a systemd message that the dGPU could not be switched off. Also, I get a flickery screen on TTYs until GDM gives up with the screen alternating between the TTY and the systemd textual log. Once that stops flashing I manage to prime-select nvidia and reboot cleanly. This is certianly better than before the update but it does not fix the situation fully. I am using bionic with all updates applied. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-02 (322 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-prime 0.8.8 PackageArchitecture: all Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-22 (120 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765888] Re: Please revert to debian-alternatives based prime-select
I think this is all a repercussion of using glvnd. I tried switching to intel mode and this results in a machine that cannot be logged in to. Also, the other framebuffer ttys are nt accessible. I recovered by going into friendly-recovery, getting a root shell, remounting my ssd as rw and executing prime-select nvidia then rebooting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765888 Title: Please revert to debian-alternatives based prime-select Status in nvidia-prime package in Ubuntu: Confirmed Bug description: The new prime-select has some problems. It is very slow to switch, since it does initramfs -u each time It leaves my two optimus laptops without graphics if you leave it in prime-select intel but boot with discrete nvidia. Previously this would load nvidia drivers. These are both two bad 'regressions' in the user experience, the first for everyone, the second for those how have a hardware mux. I know there is bug in logind meaning that a restart is required to poweroff the nvidia card. But this is not new, right? What has happened between 17.10 and 18.04 that has required this dramatic change? Is it now broken to use debian alternatives? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:25:58 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755986] Re: WiFi icon / settings gone from user menu
I get empty space isntead of them. -- 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/1755986 Title: WiFi icon / settings gone from user menu Status in gnome-shell package in Ubuntu: Confirmed Bug description: Recently, in the GNOME session, the WiFi icon vanished, and all that I get is the icon for connected network, which is odd. My other machine does not even seem to get that icon. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 06:59:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+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 1755986] Re: WiFi icon / settings gone from user menu
I have two bonded NICS, on 17.10 the menu used to show both NICs each with a connection name. In 18.04 the labels and respective icons are gone. -- 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/1755986 Title: WiFi icon / settings gone from user menu Status in gnome-shell package in Ubuntu: Confirmed Bug description: Recently, in the GNOME session, the WiFi icon vanished, and all that I get is the icon for connected network, which is odd. My other machine does not even seem to get that icon. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 06:59:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+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 1731872] Re: gnome shell crashed when searching for 're'
I managed to work around this by disabling the "Files" provider in gnome's search options. -- 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/1731872 Title: gnome shell crashed when searching for 're' Status in gnome-shell package in Ubuntu: Incomplete Bug description: When searching after pressing the super key, gnome shell restarts/hangs as soon as the search term becomes 're'. I can search for 'r' without issues. In this case I was trying to bring up remmina. The issues replicates in both nvidia and intel modes on Asus UX550VE. I will try on my PC later on, to see if I can reproduce it there as well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.14.0-041400-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 13 10:53:57 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731872/+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 1731872] [NEW] gnome shell crashed when searching for 're'
Public bug reported: When searching after pressing the super key, gnome shell restarts/hangs as soon as the search term becomes 're'. I can search for 'r' without issues. In this case I was trying to bring up remmina. The issues replicates in both nvidia and intel modes on Asus UX550VE. I will try on my PC later on, to see if I can reproduce it there as well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.14.0-041400-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 13 10:53:57 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- 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/1731872 Title: gnome shell crashed when searching for 're' Status in gnome-shell package in Ubuntu: New Bug description: When searching after pressing the super key, gnome shell restarts/hangs as soon as the search term becomes 're'. I can search for 'r' without issues. In this case I was trying to bring up remmina. The issues replicates in both nvidia and intel modes on Asus UX550VE. I will try on my PC later on, to see if I can reproduce it there as well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.14.0-041400-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 13 10:53:57 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731872/+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 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?)
I use dash to panel. -- 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/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?) Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Bug description: Saw some reports with the same title but they're all for previous versions. error report: https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 16:52:13 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-21 (135 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd97c8e7e5d : movzbl 0x16(%rax),%edx PC (0x7fd97c8e7e5d) ok source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714989/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
I found an alternate implementation of prime-select, and modified it slightly. With it, if I switch to intel mode , then reboot I manage to login with the integrated graphics getting used as expected. ** Attachment added: "prime-select" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+attachment/4968556/+files/prime-select -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
Looks like libGLX is only lodable in nvidia mode, some library paths may be missing in the intel prime profile -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
list of gl libraries loadable in nvidia mode ** Attachment added: "list of gl libraries loadable in nvidia mode" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+attachment/4968338/+files/nvidia-gl-detect.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
list of gl libraries loadable in intel mode ** Attachment added: "list of gl libraries loadable in intel mode" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+attachment/4968337/+files/intel-gl-detect.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
For referece, the bbswitch load log: [4.492602] bbswitch: version 0.8 [4.492606] bbswitch: Found integrated VGA device :00:02.0: \_SB_.PCI0.GFX0 [4.492611] bbswitch: Found discrete VGA device :01:00.0: \_SB_.PCI0.PEG0.PEGP [4.492699] bbswitch: detected an Optimus _DSM function [4.492708] bbswitch: Succesfully loaded. Discrete card :01:00.0 is on -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
Could it be that the mesa GL libraries are incorrectly installed or that some library is not in the search path when redirecting calls? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
That kernel boot parameter did not work for me. Also in teh non functional intel mode I am getting fans at maximum even with the recent nvidia drivers. Some GPU switching is really going wrong in intel mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
Looking at: https://github.com/Bumblebee-Project/bbswitch/issues/140 indicates that this has been broken since 4.8 when new power management code was enabled for PCIE ports. They suggest using pcie_port_pm=off in teh kernel command line. I will try that whenever I can and see where that leaves me. ** Bug watch added: github.com/Bumblebee-Project/bbswitch/issues #140 https://github.com/Bumblebee-Project/bbswitch/issues/140 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
None. I cannot even try 4.14 because of some GPL symbol issue which results in the DKMS build of the nvidia driver to fail. As of now, the latest kernel series that support teh binary driver is 4.13. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
I have seen it happen with both the 4.13.4 kernel currently in artful- proposed as well as the 4.13.5 upstream kernel. I am currently on the upstream kernel since 4.13.4 has an annoying shutdown hang and 4.13.5 does not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
With nvidia-375 from the PPA I get the same issue + the fans at max issue as with nvidia-381. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
I have used force version in synaptic to use the PPA version of the packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
nvidia-381 drove both my fans to max :/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
The version of nvidia-375 I am seeing points to nvidia-384. So I cannot install nvidia-375 without breaking my system (i.e. using a .run file that wouldn't work with nvidia-prime anyways) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
Is a version of 375 that supports 1050Ti available in the repos (ubuntu or graphics PPA)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
Coming to think of it I have not tried nvidia 381. Should I? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
** Description changed: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia- - prime. prime-select lists teh nvidia driver twice as the only available - alternatives. When switching to intel, the nvidia libraries are still - the used alterative but the nvidia GPU seems to get switched off - resulting in failed or hung logins. + prime. prime-select lists the nvidia driver as well as a prime variant + as the only available alternatives. When switching to intel and logging + out I get failed logins. If I reboot my screen freezes on login. It is + possible to do a hard reboot, switch back to nvidia mode in a TTY, + reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
Output when running prime-select: dylan@zenbook-pro:~$ sudo prime-select intel [sudo] password for dylan: Info: the current GL alternatives in use are: ['nvidia-387', 'nvidia-387'] Info: the current EGL alternatives in use are: ['nvidia-387', 'nvidia-387'] Info: selecting nvidia-387-prime for the intel profile update-alternatives: using /usr/lib/nvidia-387-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-387-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-387-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-387-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in manual mode dylan@zenbook-pro:~$ sudo prime-select nvidia Info: the current GL alternatives in use are: ['nvidia-387-prime', 'nvidia-387-prime'] Info: the current EGL alternatives in use are: ['nvidia-387-prime', 'nvidia-387-prime'] Info: selecting nvidia-387 for the nvidia profile update-alternatives: using /usr/lib/nvidia-387/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-387/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-387/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode update-alternatives: using /usr/lib/nvidia-387/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in manual mode ** Changed in: nvidia-prime (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists teh nvidia driver twice as the only available alternatives. When switching to intel, the nvidia libraries are still the used alterative but the nvidia GPU seems to get switched off resulting in failed or hung logins. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] Re: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
I am using X11 throughout. Wayland has not been used anywhere. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: Incomplete Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists teh nvidia driver twice as the only available alternatives. When switching to intel, the nvidia libraries are still the used alterative but the nvidia GPU seems to get switched off resulting in failed or hung logins. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1722039] [NEW] Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers
Public bug reported: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia- prime. prime-select lists teh nvidia driver twice as the only available alternatives. When switching to intel, the nvidia libraries are still the used alterative but the nvidia GPU seems to get switched off resulting in failed or hung logins. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1722039 Title: Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers Status in nvidia-prime package in Ubuntu: New Bug description: On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists teh nvidia driver twice as the only available alternatives. When switching to intel, the nvidia libraries are still the used alterative but the nvidia GPU seems to get switched off resulting in failed or hung logins. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 Uname: Linux 4.13.5-041305-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 8 09:42:05 2017 InstallationDate: Installed on 2017-10-02 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1722039/+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 1704781] Re: With gdm3 a restart is needed when switching prime profiles
When using newer nvidia drivers such as 387, switching back to intel fails to put the mesa libraries back into the LD path causing a machine freeze on login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1704781 Title: With gdm3 a restart is needed when switching prime profiles Status in gdm3 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Test case: Install nvidia drivers ,restart. Open nvidia-settings, switch prime profile. Will be prompted to log out/in, do so What happens: user goes into a log in loop To actually get back to the ubuntu-session one must restart. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 17 07:57:24 2017 InstallationDate: Installed on 2017-07-15 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170708) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1704781/+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 1720889] Re: Cannot isntall sysfsutils on artful
The hang of teh script happened while installing within a graphical session. I managed to install from within a framebuffer session i.e. a session accessed using Ctrl+Alt-F* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1720889 Title: Cannot isntall sysfsutils on artful Status in sysfsutils package in Ubuntu: New Bug description: After a brand new install of artful beta 2, I cannot install sysfsutils due to postinst script issues. The script hangs during the update-rc.d command. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sysfsutils (not installed) ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 2 23:58:36 2017 InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: sysfsutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysfsutils/+bug/1720889/+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 1720889] [NEW] Cannot isntall sysfsutils on artful
Public bug reported: After a brand new install of artful beta 2, I cannot install sysfsutils due to postinst script issues. The script hangs during the update-rc.d command. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sysfsutils (not installed) ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 2 23:58:36 2017 InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: sysfsutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sysfsutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1720889 Title: Cannot isntall sysfsutils on artful Status in sysfsutils package in Ubuntu: New Bug description: After a brand new install of artful beta 2, I cannot install sysfsutils due to postinst script issues. The script hangs during the update-rc.d command. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sysfsutils (not installed) ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 2 23:58:36 2017 InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: sysfsutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysfsutils/+bug/1720889/+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 1633824] Re: nautilus ignores trash on external drives
@cl-netbox : Did the update fix your variant of the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+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 1633824] Re: nautilus ignores trash on external drives
After updating, then logging out then back in; I confirm that this fixes the issue for USB drives making their trash folder be treated like that of internal drives. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+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 1633824] Re: nautilus ignores trash on external drives
Update-Manager just offered the update to me (I use proposed). I will test and report back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+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 1637854] [NEW] Totem does not allow changing the playback speed on subsequent files
Public bug reported: Totem has for as far as I remember, allowed the playback of subsequent files without closing and reopening the UI. One can simply double click the next file using nautilus and totem would switch files and start playback. However when the new UI for changing playback speed was introduced this has regressed. If I try to change teh playback speed on one of the subsequent media files, totem would freeze then crash. The only way to play a subsequent file and change its playback speed is to close then reopen totem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: totem 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 30 17:45:32 2016 InstallationDate: Installed on 2016-02-19 (253 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: totem UpgradeStatus: Upgraded to yakkety on 2016-10-13 (16 days ago) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1637854 Title: Totem does not allow changing the playback speed on subsequent files Status in totem package in Ubuntu: New Bug description: Totem has for as far as I remember, allowed the playback of subsequent files without closing and reopening the UI. One can simply double click the next file using nautilus and totem would switch files and start playback. However when the new UI for changing playback speed was introduced this has regressed. If I try to change teh playback speed on one of the subsequent media files, totem would freeze then crash. The only way to play a subsequent file and change its playback speed is to close then reopen totem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: totem 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 30 17:45:32 2016 InstallationDate: Installed on 2016-02-19 (253 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: totem UpgradeStatus: Upgraded to yakkety on 2016-10-13 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1637854/+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 1636095] Re: SNA acceleration causes black background and window issues on secondary display
This issue seems to be resolved when a nautilus update happened. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed => Fix Released -- 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/1636095 Title: SNA acceleration causes black background and window issues on secondary display Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: After upgrading my laptop to Ubuntu 16.10, I noticed that the secondary monitor I use at work was showing a black background instead of the background shown on my primary display. Also if windows were dragged to the secondary display I would see weird artifacts such as multiple stacked copies of the window being dragged. I believe that this is an SNA issue on multi-monitor setups. I managed to get the old correct behaviour back by switching the accelaration method to UXA by means of Xorg configuration file. My workaround involves putting: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection inside a file named /etc/X11/xorg.conf.d/20-intel.conf The information needed to assemble this file was found on the Arch Linux Wiki. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 24 08:46:43 2016 DistUpgraded: 2016-10-23 12:03:44,922 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] InstallationDate: Installed on 2016-08-04 (80 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550CA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed root=UUID=3df9651c-956b-4a87-92ed-ac0e4f4b605d ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to yakkety on 2016-10-23 (0 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Oct 24 08:43:49 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1636095/+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 1636095] Re: SNA acceleration causes black background and window issues on secondary display
Also for stuff to work, X must be started after the secondary display gets connected. The use of UXA is still needed. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Confirmed -- 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/1636095 Title: SNA acceleration causes black background and window issues on secondary display Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After upgrading my laptop to Ubuntu 16.10, I noticed that the secondary monitor I use at work was showing a black background instead of the background shown on my primary display. Also if windows were dragged to the secondary display I would see weird artifacts such as multiple stacked copies of the window being dragged. I believe that this is an SNA issue on multi-monitor setups. I managed to get the old correct behaviour back by switching the accelaration method to UXA by means of Xorg configuration file. My workaround involves putting: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection inside a file named /etc/X11/xorg.conf.d/20-intel.conf The information needed to assemble this file was found on the Arch Linux Wiki. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 24 08:46:43 2016 DistUpgraded: 2016-10-23 12:03:44,922 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] InstallationDate: Installed on 2016-08-04 (80 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550CA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed root=UUID=3df9651c-956b-4a87-92ed-ac0e4f4b605d ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to yakkety on 2016-10-23 (0 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Oct 24 08:43:49 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1636095/+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 1636095] [NEW] SNA acceleration causes black background and window issues on secondary display
Public bug reported: After upgrading my laptop to Ubuntu 16.10, I noticed that the secondary monitor I use at work was showing a black background instead of the background shown on my primary display. Also if windows were dragged to the secondary display I would see weird artifacts such as multiple stacked copies of the window being dragged. I believe that this is an SNA issue on multi-monitor setups. I managed to get the old correct behaviour back by switching the accelaration method to UXA by means of Xorg configuration file. My workaround involves putting: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection inside a file named /etc/X11/xorg.conf.d/20-intel.conf The information needed to assemble this file was found on the Arch Linux Wiki. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 24 08:46:43 2016 DistUpgraded: 2016-10-23 12:03:44,922 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] InstallationDate: Installed on 2016-08-04 (80 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X550CA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed root=UUID=3df9651c-956b-4a87-92ed-ac0e4f4b605d ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to yakkety on 2016-10-23 (0 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Oct 24 08:43:49 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety ** Summary changed: - SNA acceleration causes black background and window issues on secodnary display + SNA acceleration causes black background and window issues on secondary display ** Description changed: After upgrading my laptop to Ubuntu 16.10, I noticed that the secondary monitor I use at work was showing a black background instead of the background shown on my primary display. Also if windows were dragged to the secondary display I would see weird artifacts such as multiple stacked copies of the window being dragged. I believe that this is an SNA issue on multi-monitor setups. I managed to get the old correct - bahviour back by switching teh accelration method to UXA by means of + bahviour back by switching the accelaration method to UXA by means of Xorg configuration file. My workaround involves putting: Section "Device" -Identifier "Intel Graphics" -Driver "intel" -Option "AccelMethod" "uxa" + Identifier "Intel Graphics" + Driver
[Desktop-packages] [Bug 1633824] [NEW] nautilus ignores trash on external drives
Public bug reported: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in nautilus package in Ubuntu: New Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633824/+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 1426490] Re: cups 2.0.2-1 100% cpu usage
For me it happened when booting with systemd. I got 100% use of one of the cores by cupsd on boot. Turning the printer on seems to fix it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1426490 Title: cups 2.0.2-1 100% cpu usage Status in cups package in Ubuntu: Incomplete Bug description: upgraded from xubuntu 14.10 to 15.04 and now it uses cups 2.x after every print cupsd starts using 100% cpu and don't close. have to kill it every time with "sudo pkill cupsd" printing still works fine Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 cups: Installiert: 2.0.2-1ubuntu3 Installationskandidat: 2.0.2-1ubuntu3 Versionstabelle: *** 2.0.2-1ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1426490/+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 1382125] Re: firefox 33 on utopic crashes on page with css backgrounds
** Description changed: - My firefox 33 instance is crasheing on page with CSS3 backgrounds. In - some isntances teh divs are not getting teh background at all with + My firefox 33 instance is crashing on a page with CSS3 backgrounds. In + some instances the divs are not getting the background at all with firefox filling them with white or black instead. -- 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/1382125 Title: firefox 33 on utopic crashes on page with css backgrounds Status in “firefox” package in Ubuntu: New Bug description: My firefox 33 instance is crashing on a page with CSS3 backgrounds. In some instances the divs are not getting the background at all with firefox filling them with white or black instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1382125/+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 1382125] [NEW] firefox 33 on utopic crashes on page with css backgrounds
Public bug reported: My firefox 33 instance is crasheing on page with CSS3 backgrounds. In some isntances teh divs are not getting teh background at all with firefox filling them with white or black instead. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: utopic ** Tags added: utopic ** Tags removed: utopic ** Tags added: firefox-33 ** Tags removed: firefox-33 ** Tags added: utopic -- 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/1382125 Title: firefox 33 on utopic crashes on page with css backgrounds Status in “firefox” package in Ubuntu: New Bug description: My firefox 33 instance is crasheing on page with CSS3 backgrounds. In some isntances teh divs are not getting teh background at all with firefox filling them with white or black instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1382125/+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 1375191] [NEW] utopic: network-manager not started automatically on boot
Public bug reported: After upgrading to utopic (around the time of when the final beta was out), network manager caesed to auto start on boot. I can however start it manually using "sudo service network-manager start". When this happended iI also noticed the automatic addition of 2 mins waiting time for network interfaces on each boot. Please, can the auto start behaviour be restored? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: utopic ** Summary changed: - utopic: network-managaer not started automatically on boot + utopic: network-manager not started automatically on boot -- 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/1375191 Title: utopic: network-manager not started automatically on boot Status in “network-manager” package in Ubuntu: New Bug description: After upgrading to utopic (around the time of when the final beta was out), network manager caesed to auto start on boot. I can however start it manually using "sudo service network-manager start". When this happended iI also noticed the automatic addition of 2 mins waiting time for network interfaces on each boot. Please, can the auto start behaviour be restored? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1375191/+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 1221378] [NEW] package blt-dev 2.4z-5ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1
Public bug reported: apport showed up ProblemType: Package DistroRelease: Ubuntu 13.10 Package: blt-dev 2.4z-5ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-5.10-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 Date: Thu Sep 5 15:01:32 2013 DuplicateSignature: package:blt-dev:2.4z-5ubuntu2:trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1 ErrorMessage: trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1 InstallationDate: Installed on 2011-11-11 (664 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True SourcePackage: blt Title: package blt-dev 2.4z-5ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1 UpgradeStatus: Upgraded to saucy on 2013-08-04 (32 days ago) ** Affects: blt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-conflict saucy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to blt in Ubuntu. https://bugs.launchpad.net/bugs/1221378 Title: package blt-dev 2.4z-5ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1 Status in “blt” package in Ubuntu: New Bug description: apport showed up ProblemType: Package DistroRelease: Ubuntu 13.10 Package: blt-dev 2.4z-5ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-5.10-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 Date: Thu Sep 5 15:01:32 2013 DuplicateSignature: package:blt-dev:2.4z-5ubuntu2:trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1 ErrorMessage: trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1 InstallationDate: Installed on 2011-11-11 (664 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True SourcePackage: blt Title: package blt-dev 2.4z-5ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1 UpgradeStatus: Upgraded to saucy on 2013-08-04 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blt/+bug/1221378/+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 1220666] [NEW] [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
Public bug reported: apport showed saying a lockup had occurred ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 Chipset: sandybridge-gt1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 3 16:30:56 2013 DistUpgraded: 2013-08-04 14:50:50,172 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.11.0-4-generic, i686: installed virtualbox, 4.2.16, 3.11.0-rc4-custom, i686: installed virtualbox-guest, 4.2.16, 3.11.0-4-generic, i686: installed virtualbox-guest, 4.2.16, 3.11.0-rc4-custom, i686: installed DuplicateSignature: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:844d] InstallationDate: Installed on 2011-11-11 (663 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) InterpreterPath: /usr/bin/python3.3 MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=239a7bf6-c6d6-468d-90fb-5705e76c8def ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu3 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UpgradeStatus: Upgraded to saucy on 2013-08-04 (30 days ago) UserGroups: dmi.bios.date: 07/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-M:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Sep 4 13:56:41 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8954 vendor ACI xserver.version: 2:1.14.2.901-2ubuntu4 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash compiz-0.9 false-gpu-hang freeze i386 need-duplicate-check saucy ubuntu -- 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/1220666 Title: [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: apport showed saying a lockup had occurred ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 Chipset: sandybridge-gt1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 3 16:30:56 2013 DistUpg
[Desktop-packages] [Bug 1051559] Re: Build Firefox with GStreamer support
Gstreameer was enabled in firefox 23 by default in mozilla's builds. I have tested it in a private build and it worked fine. -- 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/1051559 Title: Build Firefox with GStreamer support Status in The Mozilla Firefox Browser: Fix Released Status in “firefox” package in Ubuntu: Triaged Status in “iceweasel” package in Debian: Confirmed Status in “firefox” package in Fedora: Unknown Bug description: Building Firefox with GStreamer support would provide support for a lot of websites that use h264. To build Firefox with GStreamer support you should use the "--enable-gstreamer" option. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1051559/+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 1106379] Re: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
*** This bug is a duplicate of bug 1041790 *** https://bugs.launchpad.net/bugs/1041790 yesterday I had 2 real hangs -- 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/1106379 Title: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: apport showed up because I had a hung system ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: i386 Chipset: sandybridge-gt1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 26 20:17:20 2013 DistUpgraded: 2013-01-24 11:41:26,852 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.22, 3.5.0-22-generic, i686: installed virtualbox, 4.1.22, 3.8.0-1-generic, i686: installed virtualbox, 4.1.22, 3.8.0-2-generic, i686: installed virtualbox-guest, 4.1.22, 3.5.0-22-generic, i686: installed DuplicateSignature: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:844d] InstallationDate: Installed on 2011-11-11 (442 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) InterpreterPath: /usr/bin/python3.3 MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=239a7bf6-c6d6-468d-90fb-5705e76c8def ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.41-0ubuntu1 xserver-xorg-video-intel 2:2.20.19-0ubuntu3 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UpgradeStatus: Upgraded to raring on 2013-01-24 (2 days ago) UserGroups: dmi.bios.date: 07/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-M:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Sat Jan 26 22:04:11 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.1.901-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1106379/+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 1106379] [NEW] [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
Public bug reported: apport showed up for no reason ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: i386 Chipset: sandybridge-gt1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 26 20:17:20 2013 DistUpgraded: 2013-01-24 11:41:26,852 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.22, 3.5.0-22-generic, i686: installed virtualbox, 4.1.22, 3.8.0-1-generic, i686: installed virtualbox, 4.1.22, 3.8.0-2-generic, i686: installed virtualbox-guest, 4.1.22, 3.5.0-22-generic, i686: installed DuplicateSignature: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:844d] InstallationDate: Installed on 2011-11-11 (442 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) InterpreterPath: /usr/bin/python3.3 MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=239a7bf6-c6d6-468d-90fb-5705e76c8def ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.41-0ubuntu1 xserver-xorg-video-intel 2:2.20.19-0ubuntu3 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UpgradeStatus: Upgraded to raring on 2013-01-24 (2 days ago) UserGroups: dmi.bios.date: 07/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-M:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Sat Jan 26 22:04:11 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.1.901-0ubuntu2 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash compiz-0.9 false-gpu-hang freeze i386 raring ubuntu -- 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/1106379 Title: [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: apport showed up for no reason ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: i386 Chipset: sandybridge-gt1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 26 20:17:20 2013 DistUpgraded: 2013-01-24 11:41:26,852 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.22, 3.5.0-22-generic, i686: installed virtualbox, 4.1.22, 3.8.0-1-generic, i686: installed virtualbox, 4.1.22, 3.8.0-2-generic, i686: installed virtualbox-guest, 4.1.22, 3.5.0-22-generic, i686: installed DuplicateSignature: [sandybri
[Desktop-packages] [Bug 967023] Re: nautilus global menu and local menu active
but tenporarily fixes wuth a nautilus -q -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/967023 Title: nautilus global menu and local menu active Status in “nautilus” package in Ubuntu: New Bug description: As of an update installed 2 days ago, nautilus now uses the global and local menu. This is (I hope) unexpected behavior? See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 07:10:04 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/967023/+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 967023] Re: nautilus global menu and local menu active
reappeared today in ubuntu precise... ** Changed in: nautilus (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/967023 Title: nautilus global menu and local menu active Status in “nautilus” package in Ubuntu: New Bug description: As of an update installed 2 days ago, nautilus now uses the global and local menu. This is (I hope) unexpected behavior? See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 07:10:04 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/967023/+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 780117] Re: Brasero finishes without error but unusable media [on-the-fly mode] (Ubuntu 11.04 ->12.04)
Hi thanks for all the work that you are doing, I used dconf to put libburn and libisofs priorities to -1. Is this good, before I make another unwanted coaster? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/780117 Title: Brasero finishes without error but unusable media [on-the-fly mode] (Ubuntu 11.04 ->12.04) Status in A disc burning application for gnome 2: New Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Triaged Status in “brasero” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Status in “brasero” package in Fedora: New Bug description: Binary package hint: brasero When I burn a DVD (4,7 and 8,5 GB) Brasero show the progressbar till about 30-40% (exact point is randomly) and than says, that it is finalizing the media. This finalizing messages is showing for the rest of the burning process (~10min @8x 8,5GB). After that, it ejects the media without any error. But when I insert the media again, nothing happens, except, that the DVD-Drive disappears from the "computer:///" location in nautilus. This problem only exists when burning On-The-Fly. Burning ISO Images or automatic creation of ISO Images before burning works without problems. The burning speed doesn't matter to this problem. I test 8x, 4x and 2x. All the same problem. On-The-Fly burning using K3B works quite well @8x speed. One thing I also notice is, that Brasero uses 100% CPU on one core, while K3B uses just about 5-15%. I attached the last Brasero log. I don't know, why it just says, that it was only at 49% and then says it's finished. The burning took about 28 minutes. The media was unusable on all my three devices (Linux/Windows). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: brasero 2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Mon May 9 22:10:24 2011 ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (brasero:2453): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `()' (brasero:2453): GLib-CRITICAL **: g_variant_get: assertion `valid_format_string (format_string, TRUE, value)' failed (:4557): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/780117/+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 998281] Re: Brasero in Precise burns coasters for data projects
I also confirm that burning on a CD results in the same behaviour. Gnomebaker was always better than brasero but it was axed. I want brasero fixed and stable for once. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/998281 Title: Brasero in Precise burns coasters for data projects Status in “brasero” package in Ubuntu: Confirmed Bug description: Brasero in precise 3.4.1-0ubuntu1 burns coasters on data dvd projects. It goes through the burn process but once the CD is ejected and reinserted , the CD fails to mount. The CD also fails to mount on 10.10. Burning the same files in Ubuntu 10.10 using Brasero (2.32) was successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/998281/+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 935328] Re: gnome-system-monitor crashes on startup
Apport is enabled as Im using precise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/935328 Title: gnome-system-monitor crashes on startup Status in “gnome-system-monitor” package in Ubuntu: Invalid Bug description: I try to start system-monitor and it crashes on startup i.e. no window is displayed. On the terminal a crash message is shown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 16:13:38 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to precise on 2012-02-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/935328/+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 935328] Re: gnome-system-monitor crashes on startup
This only happens on computer with more than 4 threads in the CPU. To fix set the cpu-colors variable to [(0, '#FF6E00'), (1, '#CB0C29'), (2, '#49A835'), (3, '#2D7DB3'), (4, '#FF6E00'), (5, '#CB0C29'), (6, '#49A835'), (7, '#2D7DB3')] in org->gnome->gnome-system-monitor by using dconf-editor. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-system-monitor (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/935328 Title: gnome-system-monitor crashes on startup Status in “gnome-system-monitor” package in Ubuntu: Confirmed Bug description: I try to start system-monitor and it crashes on startup i.e. no window is displayed. On the terminal a crash message is shown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 16:13:38 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to precise on 2012-02-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/935328/+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 935328] Re: gnome-system-monitor crashes on startup
No crash file is made in /var/crash so I cannot report a bug with it!! ** Changed in: gnome-system-monitor (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/935328 Title: gnome-system-monitor crashes on startup Status in “gnome-system-monitor” package in Ubuntu: New Bug description: I try to start system-monitor and it crashes on startup i.e. no window is displayed. On the terminal a crash message is shown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 16:13:38 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to precise on 2012-02-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/935328/+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 935328] Re: gnome-system-monitor crashes on startup
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/935328 Title: gnome-system-monitor crashes on startup Status in “gnome-system-monitor” package in Ubuntu: New Bug description: I try to start system-monitor and it crashes on startup i.e. no window is displayed. On the terminal a crash message is shown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 16:13:38 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to precise on 2012-02-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/935328/+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 935328] Re: gnome-system-monitor crashes on startup
dylan@ubuntu-server:~/Desktop$ gnome-system-monitor GLib-CRITICAL **: g_variant_get_child_value: assertion `index_ < g_variant_n_children (value)' failed GLib-CRITICAL **: g_variant_get_va: assertion `value != NULL' failed GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed *** glibc detected *** gnome-system-monitor: double free or corruption (fasttop): 0x085b4268 *** === Backtrace: = /lib/i386-linux-gnu/libc.so.6(+0x72ae2)[0xb6475ae2] /lib/i386-linux-gnu/libglib-2.0.so.0(+0x4cbeb)[0xb673ebeb] /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xb673ed60] gnome-system-monitor[0x805b372] gnome-system-monitor[0x805c869] gnome-system-monitor(main+0x24b)[0x805979b] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb641c4d3] gnome-system-monitor[0x805ae09] === Memory map: 08048000-0808a000 r-xp 08:02 5374472/usr/bin/gnome-system-monitor 0808a000-0808b000 r--p 00041000 08:02 5374472/usr/bin/gnome-system-monitor 0808b000-0808c000 rw-p 00042000 08:02 5374472/usr/bin/gnome-system-monitor 0808c000-0808d000 rw-p 00:00 0 084d4000-085f9000 rw-p 00:00 0 [heap] b470-b480 ---p 00:00 0 b48ff000-b490 ---p 00:00 0 b490-b510 rw-p 00:00 0 b510-b5121000 rw-p 00:00 0 b5121000-b520 ---p 00:00 0 b52d1000-b52d2000 ---p 00:00 0 b52d2000-b5ad2000 rw-p 00:00 0 b5ad2000-b5af9000 r--p 08:02 6424152 /usr/share/glib-2.0/schemas/gschemas.compiled b5af9000-b5afd000 r-xp 08:02 5385163 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so b5afd000-b5afe000 r--p 3000 08:02 5385163 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so b5afe000-b5aff000 rw-p 4000 08:02 5385163 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so b5aff000-b5b1f000 r--s 08:02 587/usr/share/mime/mime.cache b5b1f000-b5b2e000 r-xp 08:02 5374409 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so b5b2e000-b5b2f000 r--p e000 08:02 5374409 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so b5b2f000-b5b3 rw-p f000 08:02 5374409 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so b5b3-b5b3e000 r-xp 08:02 38015979 /lib/i386-linux-gnu/libudev.so.0.13.0 b5b3e000-b5b3f000 r--p e000 08:02 38015979 /lib/i386-linux-gnu/libudev.so.0.13.0 b5b3f000-b5b4 rw-p f000 08:02 38015979 /lib/i386-linux-gnu/libudev.so.0.13.0 b5b4-b5b87000 r-xp 08:02 38011837 /lib/i386-linux-gnu/libdbus-1.so.3.5.8 b5b87000-b5b88000 r--p 00046000 08:02 38011837 /lib/i386-linux-gnu/libdbus-1.so.3.5.8 b5b88000-b5b89000 rw-p 00047000 08:02 38011837 /lib/i386-linux-gnu/libdbus-1.so.3.5.8 b5b9-b5b91000 r--p 08:02 7216147 /usr/share/locale-langpack/en_GB/LC_MESSAGES/gdk-pixbuf.mo b5b9e000-b5b9f000 rw-p 00:00 0 b5b9f000-b5ba8000 r--p 08:02 57947479 /home/dylan/.config/dconf/user b5ba8000-b5ba9000 r--s 08:02 57947454 /home/dylan/.cache/dconf/user b5ba9000-b5bb r-xp 08:02 5377868 /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so b5bb-b5bb1000 r--p 6000 08:02 5377868 /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so b5bb1000-b5bb2000 rw-p 7000 08:02 5377868 /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so b5bb2000-b5bb5000 r--p 08:02 7216149 /usr/share/locale-langpack/en_GB/LC_MESSAGES/glib20.mo b5bb5000-b5bca000 r-xp 08:02 537 /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so b5bca000-b5bcb000 r--p 00014000 08:02 537 /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so b5bcb000-b5bcc000 rw-p 00015000 08:02 537 /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so b5bcc000-b5bd2000 r-xp 08:02 5379388 /usr/lib/i386-linux-gnu/libogg.so.0.7.1 b5bd2000-b5bd3000 r--p 5000 08:02 5379388 /usr/lib/i386-linux-gnu/libogg.so.0.7.1 b5bd3000-b5bd4000 rw-p 6000 08:02 5379388 /usr/lib/i386-linux-gnu/libogg.so.0.7.1 b5bd4000-b5bfd000 r-xp 08:02 5379470 /usr/lib/i386-linux-gnu/libvorbis.so.0.4.5 b5bfd000-b5bfe000 r--p 00028000 08:02 5379470 /usr/lib/i386-linux-gnu/libvorbis.so.0.4.5 b5bfe000-b5bff000 rw-p 00029000 08:02 5379470 /usr/lib/i386-linux-gnu/libvorbis.so.0.4.5 b5bff000-b5c07000 r-xp 08:02 5375012 /usr/lib/i386-linux-gnu/libltdl.so.7.3.0 b5c07000-b5c08000 r--p 8000 08:02 5375012 /usr/lib/i386-linux-gnu/libltdl.so.7.3.0 b5c08000-b5c09000 rw-p 9000 08:02 5375012 /usr/lib/i386-linux-gnu/libltdl.so.7.3.0 b5c09000-b5c1a000 r-xp 08:02 5380898 /usr/lib/i386-linux-gnu/libtdb.so.1.2.9 b5c1a000-b5c1b000 r--p 0001 08:02 5380898 /usr/lib/i386-linux-gnu/libtdb.so.1.2.9 b5c1b000-b5c1c000 rw-p 00011000 08:02 5380898 /usr/lib/i386-linux-gnu/libtdb.so.1.2.9 b5c1c000-b5c24000 r-xp 08:02 5379474
[Desktop-packages] [Bug 935328] [NEW] gnome-system-monitor crashes on startup
Public bug reported: I try to start system-monitor and it crashes on startup i.e. no window is displayed. On the terminal a crash message is shown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 16:13:38 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to precise on 2012-02-13 (5 days ago) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/935328 Title: gnome-system-monitor crashes on startup Status in “gnome-system-monitor” package in Ubuntu: New Bug description: I try to start system-monitor and it crashes on startup i.e. no window is displayed. On the terminal a crash message is shown. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-system-monitor 3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 16:13:38 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to precise on 2012-02-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/935328/+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
