[Desktop-packages] [Bug 2078511] [NEW] Unable to reduce column width for file NAME in nautilus
Public bug reported: In Nautilus, I'm unable to shrink the width of the Name column. I can increase it, but the default wide value is the minimum size. And it's really wide. And none of the filenames are long. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.2-0ubuntu0.2 Uname: Linux 6.10.6-061006-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 14:43:40 2024 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'date_modified', 'date_accessed', 'date_created', 'recency', 'detailed_type']" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2024-08-28 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Screenshot from 2024-08-30 14-46-30.png" https://bugs.launchpad.net/bugs/2078511/+attachment/5811194/+files/Screenshot%20from%202024-08-30%2014-46-30.png -- 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/2078511 Title: Unable to reduce column width for file NAME in nautilus Status in nautilus package in Ubuntu: New Bug description: In Nautilus, I'm unable to shrink the width of the Name column. I can increase it, but the default wide value is the minimum size. And it's really wide. And none of the filenames are long. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.2-0ubuntu0.2 Uname: Linux 6.10.6-061006-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 14:43:40 2024 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'date_modified', 'date_accessed', 'date_created', 'recency', 'detailed_type']" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2024-08-28 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2078511/+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 2077837] Re: unable to access fingerprint device after suspend/resume
Opened an upstream issue too. https://gitlab.gnome.org/GNOME/gnome- control-center/-/issues/3166 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #3166 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3166 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2077837 Title: unable to access fingerprint device after suspend/resume Status in ubuntu-settings package in Ubuntu: New Bug description: After suspending and then resuming during the fingerprint registration process, the finerprint device will be unable to be accessed. However, use fprint-enroll to register fingerprint on the command line, the fingerprint device can operate normally. I have to restart the system to register fingerprint from setting UI again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 26 11:35:45 2024 InstallationDate: Installed on 2022-11-23 (641 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077837/+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 2077837] [NEW] unable to access fingerprint device after suspend/resume
Public bug reported: After suspending and then resuming during the fingerprint registration process, the finerprint device will be unable to be accessed. However, use fprint-enroll to register fingerprint on the command line, the fingerprint device can operate normally. I have to restart the system to register fingerprint from setting UI again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 26 11:35:45 2024 InstallationDate: Installed on 2022-11-23 (641 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot from 2024-08-26 11-12-03.png" https://bugs.launchpad.net/bugs/2077837/+attachment/5809238/+files/Screenshot%20from%202024-08-26%2011-12-03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2077837 Title: unable to access fingerprint device after suspend/resume Status in ubuntu-settings package in Ubuntu: New Bug description: After suspending and then resuming during the fingerprint registration process, the finerprint device will be unable to be accessed. However, use fprint-enroll to register fingerprint on the command line, the fingerprint device can operate normally. I have to restart the system to register fingerprint from setting UI again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 26 11:35:45 2024 InstallationDate: Installed on 2022-11-23 (641 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077837/+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 2060331] [NEW] add-apt-repository --list not returning any deb822 repositories
Public bug reported: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060331 Title: add-apt-repository --list not returning any deb822 repositories Status in software-properties package in Ubuntu: New Bug description: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+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 2052851] [NEW] add-apt-repository Cannot Manage deb822 Repository Sources
Public bug reported: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a .sources file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: mantic ** Description changed: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a .sources file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): - 1. `sudo add-apt-repository ppa:flacon/ppa` adds the flacon repo as - `/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources` + 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as + '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can - also remove the repo, as expected, by running `sudo add-apt-repository - --remove ppa:flacon/ppa` + also remove the repo, as expected, by running 'sudo add-apt-repository + --remove ppa:flacon/ppa' - 3. However, `add-apt-repository --list` does not list the repo as it + 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the - broken `software-properties-common`. See here: + broken 'software-properties-common'. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html ** Description changed: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a .sources file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the - broken 'software-properties-common'. See here: + broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. h
[Desktop-packages] [Bug 1987159] Re: Drop VNC support from GNOME Remote Desktop in Kinetic
I agree with the general consensus here. RDP is not "desktop interactive" and VNC is insecure, however, when SSH tunneling to the VNC localhost server, is very secure. Enabling Vino for Ubuntu Gnome desktop was brutally simple and easy, plus there is excellent support for using SSH to connect. PLEASE bring VNC (Vino) back to Ubuntu, especially the LTS versions! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987159 Title: Drop VNC support from GNOME Remote Desktop in Kinetic Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: RDP has significantly improved privacy and performance compared to VNC. I am struggling to find any use cases where GNOME's VNC should be preferred to RDP. GNOME is so far unwilling to provide full VNC options in the GNOME Settings app. The VNC feature was labeled as Legacy in Ubuntu 22.04 LTS. There is value in only providing a single remote desktop method by default that works well. gnome-remote-desktop 43 by default only builds the RDP provider and so far I haven't seen complaints about that. Therefore, I think we should drop the VNC feature for Ubuntu 22.10. Otherwise, we need to: 1. enable VNC in gnome-remote-desktop 43 2. Update the VNC patch in gnome-control-center 43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987159/+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 2027783] [NEW] Can't see login screen on resume after YoutTube fullscreen
Public bug reported: Watchign youtube fullscreen, closed laptop, opened laptop, YT stuck in fullscreen and unable to see login screen. I was able to enter pass to get in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.3-060403-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 04:19:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3803] InstallationDate: Installed on 2023-06-26 (17 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.3-060403-generic root=UUID=9d73ee34-4258-4eaa-9690-c36f0155d2a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2020 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr8GCN37WW:bd11/23/2020:br1.37:efr1.33:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:skuLENOVO_MT_81C4_BU_idea_FM_YOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/2027783 Title: Can't see login screen on resume after YoutTube fullscreen Status in xorg package in Ubuntu: New Bug description: Watchign youtube fullscreen, closed laptop, opened laptop, YT stuck in fullscreen and unable to see login screen. I was able to enter pass to get in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.3-060403-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 04:19:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3803] InstallationDate: Installed on 2023-06-26 (17 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.3-060403-generic root=UUID=9d73ee34-4258-4eaa-9690-c36f0155d2a8 r
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
Hi Jeremyszu, That ppa fixed my issue! Is this going to prevent other upgrades? I am not super familiar with how different ppas for same packages would work. I imagine a later version will be marked as an update and override those updates. Daniel, Unfortunately I tried installing the kubuntu wayland packages and the experience was far worse on the dock. So I switched back to x as I'm a pretty big kde fan (I saw some reports that KDE wayland was a bit half baked as of yet across the web, I'm not really in the know). I might switch to gnome to try it out as it has been some years. When I do that I'll definitely try wayland again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions
Hi, I can confirm this for lenovo z16 laptop as well. This seems not yet fixed in jammy? Glad it seems to be being worked on? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1672297] Re: gnome-shell uses lots of memory, and grows over time
FWIW, I have a pretty consistent reproduction of this on my 20.04
machine here. Restarting gnome-shell with Alt-F2 then "r" causes all
the window management stuff to go away, but doesn't actually kill the
process that's reporting the giant resident set size. Manually killing
that pid also causes the WM chrome to disappear for a second and then
pop back once a new gnome-shell process spawns. That one comes up
almost instantly with a huge (but smaller, at least) RSS:
0] jbm@complexity:~/Downloads $ ps l 650626
F UID PIDPPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND
0 1000 6506262554 20 0 6884676 2449912 - Rsl ? 62:14
/usr/bin/gnome-shell
0] jbm@complexity:~/Downloads $ kill 650626
(run top to get the new PID)
130] jbm@complexity:~/Downloads $ ps l 665168
F UID PIDPPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND
0 1000 6651682554 20 0 6248912 1988284 poll_s Ssl ?0:57
/usr/bin/gnome-shell
So, it's gone from 2449912 to 1988284. That isn't nothing: 2.3GiB vs
1.9GiB, but it's still a heck of a lot of RAM for a newly-spawned
process.
Hope this report helps!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Bionic:
Fix Released
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) =
[Desktop-packages] [Bug 908791] Re: Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-Dup launch place
a few years later, i am still seeing this issue running as a normal (non-root) user w/most recent pkgs for 16.04.3LTS. gvfs-backends was not installed automatically w/deja-dup pkg installed today (almost 10yr after this issue was opened). i located this ticket via this post, figured i'd let you know it's still out there. https://askubuntu.com/questions/459679/deja-dup-ssh-method-doesnt-work- writes-locally-instead -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/908791 Title: Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja- Dup launch place Status in Déjà Dup: Expired Status in deja-dup package in Ubuntu: Fix Released Bug description: 1. I'm using up to date ArchLinux, x86_64. 2. 20.2-2 3. org.gnome.DejaDup backend 'file' org.gnome.DejaDup delete-after 0 org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD', '/home/ernestas/dw', '/home/ernestas/Muzika', '/home/ernestas/books'] org.gnome.DejaDup include-list ['$HOME'] org.gnome.DejaDup last-backup '2011-12-26T15:08:43.807421Z' org.gnome.DejaDup last-restore '' org.gnome.DejaDup last-run '2011-12-26T15:08:43.807421Z' org.gnome.DejaDup periodic true org.gnome.DejaDup periodic-period 7 org.gnome.DejaDup prompt-check '' org.gnome.DejaDup root-prompt true org.gnome.DejaDup welcomed true org.gnome.DejaDup.File icon '' org.gnome.DejaDup.File name '' org.gnome.DejaDup.File path 'ftp://ernes...@home.versme.net:21/home/ernestas/backup/' org.gnome.DejaDup.File relpath @ay [] org.gnome.DejaDup.File short-name '' org.gnome.DejaDup.File type 'normal' org.gnome.DejaDup.File uuid '' org.gnome.DejaDup.Rackspace container 'pluto' org.gnome.DejaDup.Rackspace username '' org.gnome.DejaDup.S3 bucket '' org.gnome.DejaDup.S3 folder 'pluto' org.gnome.DejaDup.S3 id '' org.gnome.DejaDup.U1 folder '/deja-dup/pluto' ** Let's say I launch Deja-Dup in home directory /home/ernestas. Then it creates /home/ernestas/sftp:/ or /home/ernestas/ftp:/ directories at which it places backups. What dependencies is Deja-Dup missing and why isn't it displaying any errors about that? To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/908791/+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 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
Updating to groovy-proposed libmutter-7-0, mutter, and mutter-common fixed the display issues with the Irfanview (WINE) snap. Woo! -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: In Progress Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: In Progress Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
This also happens on a Dell XPS 9570. My workaround after reboots, or other events that disable the headphone audio, is to run this: sudo alsactl restore Then things are back to normal for a while. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
This is even more important now, with many people working/learning from home... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1871027] [NEW] xserver-xorg-video-amdgpu list firmware-amd-graphics as a suggested package
Public bug reported: In xserver-xorg-video-ati the suggested firmware-amd-graphics was dropped because the firmware is part of the linux-firmware package in Ubuntu and since I just ran up on it I thought I would report it so that people are not searching for firmware-amd-graphics for no reason at all. ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1871027 Title: xserver-xorg-video-amdgpu list firmware-amd-graphics as a suggested package Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: In xserver-xorg-video-ati the suggested firmware-amd-graphics was dropped because the firmware is part of the linux-firmware package in Ubuntu and since I just ran up on it I thought I would report it so that people are not searching for firmware-amd-graphics for no reason at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1871027/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.5 Kernel Version: 5.4.0-21-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Apr 02 17:53:55 buntu NetworkManager[737]: [1585868035.8797] NetworkManager (version 1.22.10) is starting... (for the first time) Apr 02 17:53:55 buntu NetworkManager[737]: [1585868035.8798] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-po> Apr 02 17:53:55 buntu NetworkManager[737]: [1585868035.8798] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 02 17:53:55 buntu NetworkManager[737]: [1585868035.8798] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Confirmed Bug description: Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1857176] [NEW] [PLT V8200 Series, playback] Playback problem
Public bug reported: Hi, what happened was - I changed my input device to this device and when I did I noticed the output (to same device) became degraded. I was able to fix by setting it from high fidelity, back to headset, and back to high fidelity again. So, it seems setting the input device did some sort of 'configuration reset' that was not shown in the UI. Thanks! Wonderful OS :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jdix 1978 F pulseaudio /dev/snd/controlC0: jdix 1978 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 20 16:52:06 2019 InstallationDate: Installed on 2018-10-08 (438 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: PLT V8200 Series Symptom_Type: None of the above Title: [PLT V8200 Series, playback] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-31 (50 days ago) dmi.bios.date: 06/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L3.24 dmi.board.name: X470 Master SLI/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL3.24:bd06/04/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470MasterSLI/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1857176 Title: [PLT V8200 Series, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Hi, what happened was - I changed my input device to this device and when I did I noticed the output (to same device) became degraded. I was able to fix by setting it from high fidelity, back to headset, and back to high fidelity again. So, it seems setting the input device did some sort of 'configuration reset' that was not shown in the UI. Thanks! Wonderful OS :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jdix 1978 F pulseaudio /dev/snd/controlC0: jdix 1978 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 20 16:52:06 2019 InstallationDate: Installed on 2018-10-08 (438 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: PLT V8200 Series Symptom_Type: None of the above Title: [PLT V8200 Series, playback] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-31 (50 days ago) dmi.bios.date: 06/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L3.24 dmi.board.name: X470 Master SLI/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL3.24:bd06/04/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470MasterSLI/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857176/+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 1851997] [NEW] Typo in im-launch(1) man page
Public bug reported: im-launch(1) says: im-launch - launch input method end execute session program but should say: im-launch - launch input method and execute session program (s/end/and/) This is an upstream bug[1] which should be reported to Debian, but frankly I'm not up to dealing with the Debian BTS at the moment. [1]: https://salsa.debian.org/input-method-team/im- config/blob/24779d612f14c5f6c32ae789c7e7091fd859e7ec/im-launch.1#L5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: im-config 0.34-1ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: i3 Date: Sun Nov 10 15:04:15 2019 InstallationDate: Installed on 2018-08-13 (453 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: im-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1851997 Title: Typo in im-launch(1) man page Status in im-config package in Ubuntu: New Bug description: im-launch(1) says: im-launch - launch input method end execute session program but should say: im-launch - launch input method and execute session program (s/end/and/) This is an upstream bug[1] which should be reported to Debian, but frankly I'm not up to dealing with the Debian BTS at the moment. [1]: https://salsa.debian.org/input-method-team/im- config/blob/24779d612f14c5f6c32ae789c7e7091fd859e7ec/im-launch.1#L5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: im-config 0.34-1ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: i3 Date: Sun Nov 10 15:04:15 2019 InstallationDate: Installed on 2018-08-13 (453 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1851997/+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 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
Comment #19 PPA solved issue for me, will notify if it remains solved after a few reboots. Thanks. -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in gnome-shell source package in Disco: Triaged Status in mutter source package in Disco: Triaged Status in nvidia-graphics-drivers-418 source package in Disco: Confirmed Bug description: Recently upgraded to Disco beta. Running a 1080p screen at 100% scaling. uname -a : Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Graphics card : GeForce GT 710/PCIe/SSE2 Drivers version: Nvidia-Driver-418 Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct package to log it against) or an "Idiot User" issue. As I've upgraded this system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean install between upgrades. When I reboot, all on screen text is tiny. Icons are normal size but text is nearly unreadable. This also effects any text input boxes (i.e. user password) Text in "Show Applications" screen is also effected. *Workaroud* Only work around for the desktop is to go in to "Settings" then "Devices" then Adjust the scaling to 200%, hit Apply, then press "Revert Changes", this resets the scaling to normal. This does not fix the scaling in the "Show Applications" screen. Attached images in Scaling_Issues.zip : Image of text scaling after reboot : Scaling_Small.png Image after the "workaround" to show how it should look like: Scaling_Normal.png Image of "Show Applications" screen which is still effected : Applications_Small.png ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 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 Date: Sun Mar 31 16:00:21 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-07-09 (264 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+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 1822838] Re: [regression][nvidia] gnome-shell is very large
Bug returns after 2 reboots. -- 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/1822838 Title: [regression][nvidia] gnome-shell is very large Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 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: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+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 1822838] Re: [regression][nvidia] gnome-shell is very large
Bug has returned, not sure why to be honest but it seems like this should be fixed, I saw other people having trouble with this as well. -- 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/1822838 Title: [regression][nvidia] gnome-shell is very large Status in gnome-shell package in Ubuntu: Triaged Bug description: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 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: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+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 1822838] Re: [nvidia] gnome-shell is very large
This worked like a charm. Thanks Daniel!! Issue has been resolved. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1822838 Title: [nvidia] gnome-shell is very large Status in gnome-shell package in Ubuntu: Fix Released Bug description: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 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: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+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 1822838] Re: [nvidia] gnome-shell is very large
Bug still persists on those versions, installed all the .deb packages with Package Manager, didn't work unfortunately. My OS froze and had to fix with command line. Maybe I did something wrong, but it didn't work. -- 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/1822838 Title: [nvidia] gnome-shell is very large Status in gnome-shell package in Ubuntu: Incomplete Bug description: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 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: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+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 1822838] [NEW] gnome-shell is very large
Public bug reported: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 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: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. - Notifications, etc are extremely large. + Notifications, etc are extremely large. - Just everything from the shell is like 40% larger as it should be. This - also happens with default themes, settings, etc. + Just everything from the shell is like 40% larger than it should be. + This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 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: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) -- 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/1822838 Title: gnome-shell is very large Status in gnome-shell package in Ubuntu: New Bug description: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 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: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+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 1815329] [NEW] package libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 failed to install/upgrade: package libkpathsea6:amd64 is not ready for configuration cannot configure (
Public bug reported: Just updated and received critical errors. not sure whats wrong. also having trouble printing... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: python3-smbc: Install libkpathsea6: Configure python3-smbc: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Feb 9 21:23:11 2019 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2019-02-09 21:23:10 Commandline: aptdaemon role='role-install-packages' sender=':1.106' Install: python3-smbc:amd64 (1.0.15.5-1) DuplicateSignature: package:libkpathsea6:amd64:2015.20160222.37495-1ubuntu0.1 Unpacking python3-smbc (1.0.15.5-1) ... dpkg: error processing package libkpathsea6:amd64 (--configure): package libkpathsea6:amd64 is not ready for configuration ErrorMessage: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-12-28 (408 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: texlive-bin Title: package libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 failed to install/upgrade: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-bin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-bin in Ubuntu. https://bugs.launchpad.net/bugs/1815329 Title: package libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 failed to install/upgrade: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in texlive-bin package in Ubuntu: New Bug description: Just updated and received critical errors. not sure whats wrong. also having trouble printing... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: python3-smbc: Install libkpathsea6: Configure python3-smbc: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Feb 9 21:23:11 2019 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2019-02-09 21:23:10 Commandline: aptdaemon role='role-install-packages' sender=':1.106' Install: python3-smbc:amd64 (1.0.15.5-1) DuplicateSignature: package:libkpathsea6:amd64:2015.20160222.37495-1ubuntu0.1 Unpacking python3-smbc (1.0.15.5-1) ... dpkg: error processing package libkpathsea6:amd64 (--configure): package libkpathsea6:amd64 is not ready for configuration ErrorMessage: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-12-28 (408 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: texlive-bin Title: package libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 failed to install/upgrade: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1815329/+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 1811808] Re: Tearing and/or flickering when using i3wm
Ok, thanks; I guess I'll live with the tearing for now, then. I agree that it seems a bit pointless/unlikely to spend time fixing this given most people won't run into it now that compositors are so common. Maybe I'll get around to configuring one at some point :) -- 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/1811808 Title: Tearing and/or flickering when using i3wm Status in i3-wm package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
> Does using a Wayland session avoid the bug? Yes, I see no tearing in Totem (or Chrome) when using Wayland. (Note: after uninstalling the Nvidia drivers (`apt purge nvidia-driver-410 && apt autoremove --purge`), I have to boot with `nouveau.modeset=0`, otherwise boot hangs at Plymouth after entering my disk encryption password.) In Wayland, xrandr prints the following: $ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 340mm x 190mm 1920x1080 59.96*+ > Also, what shell are you using? If you mean shell-as-in-graphical, and I understand correctly what that means, then I'm using i3wm. If you mean shell-as-in-CLI, then bash. -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in gnome-shell package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Tearing in Totem with modesetting driver" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230257/+files/totem-tearing.jpg -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
I'm using only one monitor (the one built-in to the laptop), at times I use an external monitor as well, but this problem persists without it plugged in. After removing that block (i.e. using the modesetting driver), I get jagged tearing almost everywhere. Both Chrome and Totem tear very noticeably, but in slightly different ways (I'll attach some pictures). However, when Chrome is in fullscreen mode, there's no tearing at all, but Totem continues to tear when fullscreened. ** Attachment added: "Tearing in Chrome with modesetting driver" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230256/+files/chrome-tearing.jpg -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230058/+files/Xorg.0.log -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
This Xorg.1.log was last modified in November, so I'm unsure if it's relevant. ** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230059/+files/Xorg.1.log -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
I don't have an /etc/X11/xorg.conf, but I do have (along with the various distribution-provided files) a /usr/share/X11/xorg.conf.d/99-custom.conf. ** Attachment added: "99-custom.conf" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230057/+files/99-custom.conf -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
Unfortunately, the BIOS doesn't have an option to disable the Nvidia GPU. ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230056/+files/allpackages.txt -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia
@Alberto: would you be open to adding it again? I need to enable TearFree and select the Intel driver when using my integrated GPU (but if I have `Driver "intel"` in my config when using the Nvidia GPU, I get a black screen on login), so it would be nice to have a way to automatically put a file in xorg.conf.d when switching the GPU. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support using custom xorg.conf files for Nvidia Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Released Status in ubuntu-drivers-common source package in Zesty: Fix Released Bug description: SRU Request: [Impact] Different GPUs may require different options in the xorg.conf file. Currently this is not possible, since the options have been hardcoded in gpu-manager to configure the system automatically. This new (backported) feature allows users to tell gpu-manager to use their own custom xorg.confs for their NVIDIA GPUs. [Test Case] 1) Enable the xenial-proposed repository, and install the ubuntu-drivers-common and the nvidia-prime packages. 2) Install the nvidia driver. 3) Place your configuration file(s) in the /usr/share/gpu-manager.d directory. If you are using a non-hybrid system, you can create the /usr/share /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share /gpu-manager.d/hybrid-power-saving, depending on the power profile you intend to apply your settings to. 4) Restart the system and see if it boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log 5) Make sure that the /etc/X11/xorg.conf matches the file you specified in 3) [Regression Potential] Low, the above mentioned changes are already in Artful, and will not affect the system's behaviour unless new configuration files are put in the /usr/share/gpu-manager.d/ directory. __ This feature has been implemented for Intel (ex. gpumanager_uxa), which is parsing kernel parameter to add option in xorg.conf (commit ff3a4e54). And now Nvidia also need this feature to add Option "nvidiaXineramaInfo" "off" to fix some issues. Btw, I'm thinking it might be a more flexible to have a config file which user could add all options as they want so that we could prevent keeping change gpu-manager when some more options are needed in the future. Needed by LP: #1653592 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667198/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
Removing gstreamer1.0-vaapi doesn't appear to help. -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Output of `vainfo`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229623/+files/vainfo -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Output of `lspci -k`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229624/+files/lspci -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Output of `lscpu`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229622/+files/lscpu -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: Incomplete Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1811808] [NEW] Tearing and/or flickering when using Intel graphics
Public bug reported: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Attachment added: "flickering with TearFree enabled" https://bugs.launchpad.net/bugs/1811808/+attachment/5229271/+files/Screenshot%20from%202019-01-03%2016-49-50.png -- 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/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem package in Ubuntu: New Bug description: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+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 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia
This is no longer found in Bionic, since ubuntu-drivers-common 1:0.5 (see [1]). Was this feature intentionally removed? [1]: https://git.launchpad.net/ubuntu/+source/ubuntu-drivers- common/commit/share/hybrid/gpu- manager.c?id=fb450c8eddf9290225e198ce92123e4fff346589 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support using custom xorg.conf files for Nvidia Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Released Status in ubuntu-drivers-common source package in Zesty: Fix Released Bug description: SRU Request: [Impact] Different GPUs may require different options in the xorg.conf file. Currently this is not possible, since the options have been hardcoded in gpu-manager to configure the system automatically. This new (backported) feature allows users to tell gpu-manager to use their own custom xorg.confs for their NVIDIA GPUs. [Test Case] 1) Enable the xenial-proposed repository, and install the ubuntu-drivers-common and the nvidia-prime packages. 2) Install the nvidia driver. 3) Place your configuration file(s) in the /usr/share/gpu-manager.d directory. If you are using a non-hybrid system, you can create the /usr/share /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share /gpu-manager.d/hybrid-power-saving, depending on the power profile you intend to apply your settings to. 4) Restart the system and see if it boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log 5) Make sure that the /etc/X11/xorg.conf matches the file you specified in 3) [Regression Potential] Low, the above mentioned changes are already in Artful, and will not affect the system's behaviour unless new configuration files are put in the /usr/share/gpu-manager.d/ directory. __ This feature has been implemented for Intel (ex. gpumanager_uxa), which is parsing kernel parameter to add option in xorg.conf (commit ff3a4e54). And now Nvidia also need this feature to add Option "nvidiaXineramaInfo" "off" to fix some issues. Btw, I'm thinking it might be a more flexible to have a config file which user could add all options as they want so that we could prevent keeping change gpu-manager when some more options are needed in the future. Needed by LP: #1653592 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667198/+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 1514057] Re: Incorrect(?) reporting of freeness of third-party nVidia drivers from graphic-drivers PPA
I believe this is due to a simplistic handling of "freeness" in
UbuntuDrivers.detect._is_package_free() – any package not from
restricted or multiverse is considered free:
# it would be better to check the actual license, as we do not have
# the component for third-party packages; but this is the best we can do
# at the moment
if pkg.candidate.section.startswith('restricted') or \
pkg.candidate.section.startswith('multiverse'):
return False
return True
Possibly it would be better to do the logic the other way around ("if
it's in main/universe/whatever, then it's free, otherwise it's
nonfree"), but really a better solution is needed.
However, I notice that the Nvidia drivers on my system are from section
"non-free/libs" – the following patch fixes the problem for me:
--- a/UbuntuDrivers/detect.py 2019-01-10 02:30:54.326668673 +
+++ b/UbuntuDrivers/detect.py 2019-01-10 02:36:24.707733516 +
@@ -165,7 +165,8 @@
# the component for third-party packages; but this is the best we can do
# at the moment
if pkg.candidate.section.startswith('restricted') or \
-pkg.candidate.section.startswith('multiverse'):
+pkg.candidate.section.startswith('multiverse') or \
+pkg.candidate.section.startswith('non-free'):
return False
return True
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1514057
Title:
Incorrect(?) reporting of freeness of third-party nVidia drivers from
graphic-drivers PPA
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Bug description:
pumpkin@pumpkin:~/4788.5236.la$ sudo ubuntu-drivers devices
== /sys/devices/pci:00/:00:03.0/:03:00.0 ==
modalias : pci:v10DEd1080sv10B0sd0401bc03sc00i00
model: GF110 [GeForce GTX 580]
vendor : NVIDIA Corporation
driver : nvidia-340-updates - distro non-free
driver : nvidia-352-updates - distro non-free
driver : nvidia-355 - third-party free recommended
driver : nvidia-352 - third-party free
driver : xserver-xorg-video-nouveau - distro free builtin
driver : nvidia-340 - distro non-free
driver : nvidia-304-updates - distro non-free
driver : nvidia-304 - distro non-free
I have some difficulty believing that nvidia-352 is free and
nvidia-352-updates non-free; I would have thought nvidia-352 and
nvidia-355 are both third-party non-free.
it is possible this is the result of having some extra PPAs installed:
pumpkin@pumpkin:~/4788.5236.la$ sudo apt-get install nvidia-355
Reading package lists... Done
Building dependency tree
Reading state information... Done
Recommended packages:
libcuda1-355 nvidia-opencl-icd-355
The following packages will be upgraded:
nvidia-355
1 to upgrade, 0 to newly install, 0 to remove and 19 not to upgrade.
Need to get 58.6 MB of archives.
After this operation, 3,072 B of additional disk space will be used.
Get:1 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ wily/main
nvidia-355 amd64 355.11-0ubuntu0~gpu15.10.2 [58.6 MB]
So maybe this is a matter of package status being marked up
incorrectly in the PPA?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1514057/+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 66566]
"Cmd+Enter" not opening a new tab from the address bar has been my biggest hangup as I attempt to switch from Chrome to Firefox now. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 583797]
Comment on attachment 9004028 -fixquit.patch make warn=true warn again Redirecting to someone who works on the Firefox frontend. -- 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/583797 Title: "Warn on closing with multiple tabs open" not honored Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy firefox firefox: Installed: 11.0+build1-0ubuntu0.11.10.1 Candidate: 11.0+build1-0ubuntu0.11.10.1 Version table: *** 11.0+build1-0ubuntu0.11.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ oneiric-security/main i386 Packages 100 /var/lib/dpkg/status 7.0.1+build1+nobinonly-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in Firefox, with Edit -> Preferences -> Tabs -> "Warn on closing with multiple tabs open" checkbox checked, is when one click the X, File -> Quit, Ctrl+Q , or Alt+Space -> C, one get's the confirmation box: Confirm close You are about to close x tabs. Are you sure you want to continue? 4) What happens instead is one is not warned and the window closes. PARTIAL WORKAROUND: about:config -> browser.tabs.maxOpenBeforeWarn -> change from 15 to 2. This will pop up the confirmation box clicking the X and Alt+Space -> C only. WORKAROUND: Disable Ctrl+Q quiting the browser by installing keyconfig add-on: http://mozilla.dorando.at/keyconfig.xpi Then Tools -> Add-Ons -> Extensions -> keyconfig Preferences -> highlight Quit -> Disable Original Reporter Comments: I found a "workaround" that says to set "open to a blank page" somewhere else, and I set this, but it still doesn't warn me. I work from home and frequently spend an hour or so putting in data, all on one screen. If I accidentally hit the stupid little x (which is now in the left hand corner just where you don't need it, it is too easy to hit it by accident, but i can't change this, it comes with the distro), i lose all that work. Please tell me how to fix this terrible bug. Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3 GTB7.1 THIS BUG AFFECTS MY SECURITY (INCOME) but i guess would not be classifed as a security bug per se ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Fri May 21 14:07:40 2010 FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/583797/+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 1797147] Re: Backport PRIME switching fixes to Ubuntu 18.04
I tested with LightDM, ubuntu-drivers-common 1:0.5.2.2, and nvidia-prime 0.8.8.2, doing various combinations of `prime-select intel` and `prime- select nvidia`; everything seems to work as described in the original description. Thank you Alberto for your work on this! ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1797147 Title: Backport PRIME switching fixes to Ubuntu 18.04 Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] A recent update (LP: #1778011) in 18.04 has restored the PRIME switching mechanism in Gdm 3 only, while still leaving out support for other login managers (such as Lightdm, and SDDM). In addition to this, we should restore the default pci power control profile for the dGPU when re-enabling performance mode, as we do in Ubuntu 18.10. [Test Case] 1) Make sure that you are using a login manager such as Lightdm or SDDM. 2) Enable the bionic-proposed repository, and install the new "ubuntu- drivers-common", and the new nvidia-prime. 3) Make sure the nvidia packages are installed and working, and enable power saving mode: sudo prime-select intel 4) Log out, log back in, and check that the nvidia kernel module is not loaded: lsmod | grep nvidia 5) Select performance mode: sudo prime-select nvidia 6) Log out, and log back in 7) Check if the nvidia driver loaded: lsmod | grep nvidia [Regression Potential] Low, as switching already fails in 18.04, since X is started before udev adds back the dGPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1797147/+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 1788659] Re: network manager assigns ethernet default route metric of 20100
I eventually figured out that's what was happening. However, the connectivity check is not working correctly. In my case, there is indeed ethernet connectivity, despite it thinking that there isn't. It will assign the network "penalty" metric even when ethernet has been connected for 30+ minutes, so something is causing it to incorrectly fail the connectivity check. If I override the metric manually, it works and uses ethernet, so there is not a problem with the connection. -- 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/1788659 Title: network manager assigns ethernet default route metric of 20100 Status in network-manager package in Ubuntu: Incomplete Bug description: After upgrading from 16.04 to 18.04, when I boot with an ethernet cable connected, Ubuntu prefers to use the wifi interface over the ethernet interface. Wifi is assigned the normal metric of 600 for both of its routing table entries. However ethernet is assigned a metric of 20100. I edited the connection details via nmcli to manually set the ethernet metric to 100. After a reboot, the link route (for the LAN subnet) correctly has a metric of 100. But the default route for eth0 is still 20100. nm-applet shows the wifi icon, correctly indicating that the default route is over wifi rather than ethernet. The only fix is to manually set the route after every reboot, or turn off wifi. This is a regression from 16.04. network-manager 1.10.6-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788659/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Is there another bug I can follow to find out when LightDM will receive support for this update? -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1769654] Re: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics
The -proposed packages fix text selection for Liberation fonts in Chrome for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation in Ubuntu. https://bugs.launchpad.net/bugs/1769654 Title: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics Status in fonts-liberation package in Ubuntu: Fix Released Status in fonts-liberation2 package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Confirmed Status in fonts-liberation source package in Bionic: Fix Committed Status in fonts-liberation2 source package in Bionic: Fix Committed Status in libreoffice source package in Bionic: Confirmed Status in fonts-liberation package in Debian: Fix Released Status in fonts-liberation2 package in Debian: Fix Released Bug description: [Impact] fonts-liberation and fonts-liberation2 in bionic have skewed font metrics. This is causing visible formatting issues in any program rendering text using those fonts, most notably libreoffice (recent versions fail to build because some unit tests that check the rendered layout fail). This was fixed in debian and synced in cosmic (https://salsa.debian.org/fonts-team/fonts-liberation/blob/master/debian/patches/unset_OS2_UseTypoMetrics.patch). Backporting to bionic is a prerequisite to backporting a recent version of libreoffice (6.0.6, bug #1785679). [Test Case] See original description (at the bottom of the description) for example text documents and their expected layout when opened in libreoffice. A good test case is whether libreoffice 6.0.6 builds successfully (all unit tests pass - some unit tests exercise text layout and they fail with the broken version of fonts-liberation2). [Regression Potential] Rendering of text across a variety of programs (especially word processors and web browsers) should be checked to ensure that this doesn't introduce regressions. [Other Info] This is backported straight from Debian, no Ubuntu-specific modifications. [Original description] Ubuntu/Xubuntu 18.04 package includes fonts "Liberation Sans" (etc "Liberation") with sligtly shrinked font metrics. This issue leads to all office documents typed in Liberation Sans fonts have corrupted formatting in Ubuntu 18.04 (but these documents correctly opened in other OS's, for example Ubuntu 17.10). Documents with corrupted formatting can not print properly: all paragraphs are shifted up, embedded tables in text - splitted on page breaks. Document circulation in system based on Ubuntu 18.04 operating systems temporarily paralized, because Liberation fonts are basic fonts for open-source document circulation. In attachment I have type a example office document with 2 pages and enumerated strings. On normal ordinary conditions this document have 54 strings on first page and 54 string on second page. But if this document open in Ubuntu 18.04, it's found than 5 strings from second page moves to first page. Compare font versions embedded with Ubuntu packages we can see that versions are different (sudo apr search fonts-liberation* command): Ubuntu 17.10 - 1:1.07.4-2, 2.00.1-3 Ubuntu 18.04 - 1:1.07.4-5, 2.00.1-5 I have create a bug 117411 "Font metrics slightly changed after update OS to Ubuntu 18.04", see https://bugs.documentfoundation.org/show_bug.cgi?id=117411, but I think that this bug concerns a Ubuntu/Xubuntu 18.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769654/+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 1788659] [NEW] network manager assigns ethernet default route metric of 20100
Public bug reported: After upgrading from 16.04 to 18.04, when I boot with an ethernet cable connected, Ubuntu prefers to use the wifi interface over the ethernet interface. Wifi is assigned the normal metric of 600 for both of its routing table entries. However ethernet is assigned a metric of 20100. I edited the connection details via nmcli to manually set the ethernet metric to 100. After a reboot, the link route (for the LAN subnet) correctly has a metric of 100. But the default route for eth0 is still 20100. nm-applet shows the wifi icon, correctly indicating that the default route is over wifi rather than ethernet. The only fix is to manually set the route after every reboot, or turn off wifi. This is a regression from 16.04. network-manager 1.10.6-2ubuntu1 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1788659 Title: network manager assigns ethernet default route metric of 20100 Status in network-manager package in Ubuntu: New Bug description: After upgrading from 16.04 to 18.04, when I boot with an ethernet cable connected, Ubuntu prefers to use the wifi interface over the ethernet interface. Wifi is assigned the normal metric of 600 for both of its routing table entries. However ethernet is assigned a metric of 20100. I edited the connection details via nmcli to manually set the ethernet metric to 100. After a reboot, the link route (for the LAN subnet) correctly has a metric of 100. But the default route for eth0 is still 20100. nm-applet shows the wifi icon, correctly indicating that the default route is over wifi rather than ethernet. The only fix is to manually set the route after every reboot, or turn off wifi. This is a regression from 16.04. network-manager 1.10.6-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788659/+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 1722286] Re: Same action is forced for lid-close on AC and lid-close on battery
Can you modify this script so that it works when an external monitor is connected or the laptop is docked? gsd overrides logind, and prevents the computer from suspending in these cases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1722286 Title: Same action is forced for lid-close on AC and lid-close on battery Status in GNOME Settings Daemon: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Note: I'm flagging this as a bug in gnome-settings-daemon, but the program itself is not buggy. It's rather the usage of this program instead of unity-settings-daemon in ubuntu 17.10 that causes a system regression. --- Up to and including Ubuntu 17.04, unity-settings-daemon was used to managed suspend policy in the default graphic session (Unity). Unity-settings-daemon is a fork of (an old version of) gnome-settings-daemon. Now that gnome-shell is the default environment, session management is handled by gnome-settings-daemon. In particular, the action to perform when the lid is closed is handled by the gsd-power plugin of gnome-settings-daemon (as it was by unity-settings-daemon). With unity-settings-daemon, two dconf keys where honored (lid-close- ac-action and lid-close-battery-action, under org/gnome/settings- daemon/power ) to specify what action are performed when the user closes the laptop lid, depending on whether the laptop is plugged or on battery. In Ubuntu 17.10, gnome-settings-daemon ignore those settings (unless their value is 'ignore') and delegate actions to systemd-logind. The latter has no knowledge on whether the laptop is plugged or not and apply the same action regardless. This is a regression in a useful (and I believe popular) functionality. It is common to want the laptop to suspend when unplugged but expecting it to remain running when plugged (I believe this is the default on MacOS and windows and both system can be configured to distinguish between on-AC and on-Battery). The functionality can be restored with a bit of sweat with either hooks for acpid (or maybe a session script using the gnome framework to detect events and apply the correct policy, acpid-scripts run as root), but this is clearly not something the average user should have to tinker with. At the *very least* release note should advertise this regression (as a new feature ?) but ideally provide a compatibility layer to restore this functionality. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 16:15:54 2017 InstallationDate: Installed on 2015-06-03 (859 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to artful on 2017-03-16 (207 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1722286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1781739] Re: 18.04 Leaking wireless connection to other users
Hi, the laptop is on vacation for a couple of weeks now, also I have no prior experience updating kernels, i'm unsure whether it is wise to do for me. On Wed, Jul 25, 2018, 8:50 PM Kai-Heng Feng wrote: > ** Also affects: network-manager (Ubuntu) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1781739 > > Title: > 18.04 Leaking wireless connection to other users > > Status in linux package in Ubuntu: > Incomplete > Status in network-manager package in Ubuntu: > New > > Bug description: > In ubuntu 18.04, when setting up a new wireless connection: > > Select "Connect automatically" > Untick "Make this connection available to other users" > Select "Store the password only for this user" > > Once you are connected to the network, switch user once or twice. > Eventually the other user will be connected to the network. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781739/+subscriptions > -- 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/1781739 Title: 18.04 Leaking wireless connection to other users Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: In ubuntu 18.04, when setting up a new wireless connection: Select "Connect automatically" Untick "Make this connection available to other users" Select "Store the password only for this user" Once you are connected to the network, switch user once or twice. Eventually the other user will be connected to the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781739/+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 1744409] [NEW] Unable to arrange displays in gnome control center with 3 connected monitors and having 1 disabled
Public bug reported: Release: Ubuntu 17.10 Package: gnome-control-center Version: 1:3.26.2-0ubuntu0.2 Expected to be able to arrange displays via the displays panel when having three or more displays attached. Displays are locked place as long as one display is disabled. When all displays are enabled positioning works as expected, however when one display is disabled (ex. a docked laptop with two external displays) you are unable to position displays. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Jan 19 16:51:12 2018 InstallationDate: Installed on 2018-01-19 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2018-01-19 (0 days ago) ** Affects: gnome-control-center (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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1744409 Title: Unable to arrange displays in gnome control center with 3 connected monitors and having 1 disabled Status in gnome-control-center package in Ubuntu: New Bug description: Release: Ubuntu 17.10 Package: gnome-control-center Version: 1:3.26.2-0ubuntu0.2 Expected to be able to arrange displays via the displays panel when having three or more displays attached. Displays are locked place as long as one display is disabled. When all displays are enabled positioning works as expected, however when one display is disabled (ex. a docked laptop with two external displays) you are unable to position displays. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Jan 19 16:51:12 2018 InstallationDate: Installed on 2018-01-19 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2018-01-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1744409/+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 1734587] Re: i386 libsane1 package fails to install with file conflicts
Sorry, I forgot I reported the same thing already. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1734587 Title: i386 libsane1 package fails to install with file conflicts Status in sane-backends package in Ubuntu: Invalid Bug description: Tested on Fresh Ubuntu 17.10 Artful and Fresh 18.04 Bionic Basically, I need to install libsane1:i386 for Winehq wine. Unfortunately libsane1:i386 fails to install because there are file conflicts with another instance. I tried apt install --no-install- recommends libsane1:i386 also. Terminal Output: ... Preparing to unpack .../22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb ... Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-1jW92J/22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-1jW92J/22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ... Full log attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1734587/+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 1734587] [NEW] i386 libsane1 package fails to install with file conflicts
Public bug reported: Tested on Fresh Ubuntu 17.10 Artful and Fresh 18.04 Bionic Basically, I need to install libsane1:i386 for Winehq wine. Unfortunately libsane1:i386 fails to install because there are file conflicts with another instance. I tried apt install --no-install- recommends libsane1:i386 also. Terminal Output: ... Preparing to unpack .../22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb ... Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-1jW92J/22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-1jW92J/22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ... Full log attached below. ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: Invalid ** Tags: package-conflict ** Attachment added: "Full log from apt" https://bugs.launchpad.net/bugs/1734587/+attachment/5015032/+files/term.log ** Package changed: sssd (Ubuntu) => sane-backends (Ubuntu) ** Changed in: sane-backends (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1734587 Title: i386 libsane1 package fails to install with file conflicts Status in sane-backends package in Ubuntu: Invalid Bug description: Tested on Fresh Ubuntu 17.10 Artful and Fresh 18.04 Bionic Basically, I need to install libsane1:i386 for Winehq wine. Unfortunately libsane1:i386 fails to install because there are file conflicts with another instance. I tried apt install --no-install- recommends libsane1:i386 also. Terminal Output: ... Preparing to unpack .../22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb ... Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-1jW92J/22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-1jW92J/22-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ... Full log attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1734587/+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 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
Also affects me on Lubuntu 16.04. Installing IBus (sudo apt ibus) and using Preferences > Language Support to change the Keyboard input method system to IBus, followed by a system reboot, has fixed the issue (compose:ralt in Keyboard Layout Handler now functions as expected). -- 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/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 Status in firefox package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+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 1708933] Re: Can't add a Microsoft account to GNOME Online Accounts
I'm seeing the same bug, same gnome-online-accounts version but on 17.04. First time running Online Accounts I was presented with a Microsoft option. I signed in (and I also have a non-standard Live account meaning it's not outlook.com or hotmail.com), seemed successful, I turned off e-mail but left documents on. The account seemed to add but I couldn't find the documents anywhere. Now when I go back into Online Accounts I'm only given three options for accounts to add: Facebook, Flickr, and Google. The Microsoft account doesn't appear. I tried to uninstall completely and install (just the gnome-online-accounts applet) and it still shows the same. Is there a way to remove the configuration and start completely over? I can't even seem to get to that point. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1708933 Title: Can't add a Microsoft account to GNOME Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: In artful: 1) Open Settings->Online Accounts 2) Click on "Microsoft" under "Add an account" 3) See an authorization window pop up, enter my user/password for Microsoft Live 4) Click next, see it ask whether it's OK to give GNOME various permissions 5) Click yes, see the window disappear But at this point, no Microsoft account appears in the active-accounts section. It just seems to have closed the window and done nothing. Is there a way to get better logging for this and try again? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 6 10:03:55 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (1669 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+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 1709890] [NEW] Simple Scan Ignores Back or Front & Back Selections Fujitsu ScanSnap iX500
Public bug reported: What I expect to happen: I expect to get scan output from the back of the page when back is selected, front and back output when front & back is selected in preferences. What happens: only front is shown. $ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 $ apt-cache policy simple-scan simple-scan: Installed: 3.20.0-0ubuntu1 Candidate: 3.20.0-0ubuntu1 Version table: *** 3.20.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Log" https://bugs.launchpad.net/bugs/1709890/+attachment/4930093/+files/simple-scan.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1709890 Title: Simple Scan Ignores Back or Front & Back Selections Fujitsu ScanSnap iX500 Status in simple-scan package in Ubuntu: New Bug description: What I expect to happen: I expect to get scan output from the back of the page when back is selected, front and back output when front & back is selected in preferences. What happens: only front is shown. $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ apt-cache policy simple-scan simple-scan: Installed: 3.20.0-0ubuntu1 Candidate: 3.20.0-0ubuntu1 Version table: *** 3.20.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1709890/+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 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial
Tested chromium-fix-1702407 ppa with -ubuntu 16.0.4 -setting the Media Router option to default again. -copied over original chromium config file. Everything's working so far no crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial Status in chromium-browser package in Ubuntu: In Progress Bug description: $ apt-cache policy chromium-browser chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04.1289 Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 Version table: *** 59.0.3071.109-0ubuntu0.16.04.1289 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ chromium-browser Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= Received signal 11 SEGV_MAPERR 0010 #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace() #1 0x7f8cc1af580b #2 0x7f8cc1e20390 #3 0x5619ce286dc8 #4 0x5619ce289656 #5 0x5619ce289df9 #6 0x5619ce28a143 #7 0x7f8cc1b70821 #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask() #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask() #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f8cc1b2283d #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run() #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler() #14 0x7f8cc1b49628 base::RunLoop::Run() #15 0x7f8cc1b75e36 base::Thread::ThreadMain() #16 0x7f8cc1b70726 #17 0x7f8cc1e166ba start_thread #18 0x7f8cab4c53dd clone r8: 002e r9: 5619cfcdd6ec r10: r11: 7f8cab552f50 r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 7f8c1b0d1eb0 di: si: 7f8c1b0d1eb0 bp: 7f8c1b0d1f00 bx: 7f8c1b0d1eb0 dx: 0061 ax: cx: 7f8bf0047070 sp: 7f8c1b0d1e60 ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Quits <1s after starting on desktop. Output from terminal-based launch is above. Worked earlier today before updating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+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 1676465] [NEW] package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: cups daemon crashed during the regular update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Date: Mon Mar 27 22:31:09 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-01-06 (80 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Lpstat: device for HP_LaserJet_CM1415fn: hp:/net/HP_LaserJet_CM1415fn?ip=192.168.0.210 device for Officejet_7500_E910: hp:/net/Officejet_7500_E910?ip=192.168.0.201 MachineType: Hewlett-Packard HP EliteBook 8440p Papersize: a4 PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" PpdFiles: Officejet_7500_E910: HP Officejet 7500 e910, hpcups 3.16.11 HP_LaserJet_CM1415fn: HP LaserJet CM1410 Series Postscript (recommended) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=UUID=b514345d-cf89-42d8-881a-655d280b16f7 ro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=UUID=b514345d-cf89-42d8-881a-655d280b16f7 ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.60 dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.35 dmi.chassis.asset.tag: SGH138PHC7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- 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/1676465 Title: package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: cups daemon crashed during the regular update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Date: Mon Mar 27 22:31:09 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-01-06 (80 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Lpstat: device for HP_LaserJet_CM1415fn: hp:/net/HP_LaserJet_CM1415fn?ip=192.168.0.210 device for Officejet_7500_E910: hp:/net/Officejet_7500_E910?ip=192.168.0.201 MachineType: Hewlett-Packard HP EliteBook 8440p Papersize: a4 PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" PpdFiles: Officejet_7500_E910: HP Officejet 7500 e910, hpcups 3.16.11 HP_LaserJet_CM1415fn: HP LaserJet CM1410 Series Postscript (recommended) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=UUID=b514345d-cf89-42d8-881a-655d280b16f7 ro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=UUID=b514345d-cf89-42d8-881a-655d280b16f7 ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.60 dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.35 dmi.chassis.asset.tag: SGH138PHC7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-p
[Desktop-packages] [Bug 1471300] Re: Virtual Memory cannot be shown
Possibly a duplicate of #1581229 ** Bug watch added: GNOME Bug Tracker #768063 https://bugzilla.gnome.org/show_bug.cgi?id=768063 ** Also affects: gnome-system-monitor via https://bugzilla.gnome.org/show_bug.cgi?id=768063 Importance: Unknown Status: Unknown -- 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/1471300 Title: Virtual Memory cannot be shown Status in Gnome System Monitor: Unknown Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: Open gnome-system-monitor, switch to the tab "Processes", right-click on a the heading of a column, check "Virtual Memory". On my system (Ubuntu 15.04 64 Bit) with gnome-system-monitor 3.15.91 no virtual memory column is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1471300/+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 1471300] Re: Virtual Memory cannot be shown
The issue for me was that the column was being inserted with zero width. Workaround: resize all the columns until you find where the new column is. -- 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/1471300 Title: Virtual Memory cannot be shown Status in Gnome System Monitor: Unknown Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: Open gnome-system-monitor, switch to the tab "Processes", right-click on a the heading of a column, check "Virtual Memory". On my system (Ubuntu 15.04 64 Bit) with gnome-system-monitor 3.15.91 no virtual memory column is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1471300/+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 1526337] Re: Accelerometer does not change orientation
I am experiencing the same issue, on a Dell Insprion 13 series 7000 model 7378 2-in-1 laptop. Is there a fix for this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1526337 Title: Accelerometer does not change orientation Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: I have a 2-in-1 laptop with an accelerometer (Inspiron 13-7359). I would like the screen to change orientation automatically when the screen is rotated. I've noticed that the accelerometer works correctly, by installing iio-sensors-proxy and manually executing d-Bus methods. I've also noticed that upstream gnome-settings-daemon uses iio-sensors-proxy whereas unity-settings-daemon does not. That's as far as I've come. Do you think we should add iio-sensors- proxy to main and the default image, and also grab Gnome's patches for orientation? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-settings-daemon 15.04.1+16.04.20151214-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 15 14:59:31 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1526337/+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 1001842] Re: No Audio from HDMI After Switching Monitor Off / On
I was able to work around this problem by using the xorg.conf option "CustomEDID". The goal is to essentially tell the system to pretend that your particular model of monitor/TV is always connected to the port in question. First, run this to determine the name of the video port in question: xrandr -d :0 --auto Then, generate an edid file with the 'get-edid' utility. You can pipe the output into the edid-decode utility to see it, and eventually output it to a file (I used /root/edid.bin). Then add something like this to your /etc/X11/xorg.conf, inside the "Device" section: Option "UseHotplugEvents" "False" Option "ConnectedMonitor" "HDMI-0" Option "UseDisplayDevice" "HDMI-0" Option "CustomEDID" "HDMI-0:/root/edid.bin" Where HDMI-0 is the video port name you got from xrandr. If you don't already have an xorg.conf file, you'll need to make one somehow. The "nvidia-xconfig" executable worked for me, but I'm sure it will vary depending on the video card and driver in question. WARNING: I've read that using the CustomEDID option with an incorrect edid file (such as one for the wrong monitor or a different port) can cause hardware damage! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1001842 Title: No Audio from HDMI After Switching Monitor Off / On Status in fglrx-installer package in Ubuntu: Confirmed Bug description: After the 12.04 Update my HDMI audio stops working anytime I turn off or on, my 2nd monitor(plasma TV) System Settings>Sound - Output HDMI audio disappears from the list when monitor is turned off or on and does not reappear. see http://askubuntu.com/questions/133575/hdmi-audio-stops-after-tv- turned-off/139265#139265 I'm guessing it has something to do with sink detection and ATI video The only info I've found is after running pactl list Partial copy Sink #0 State: SUSPENDED Name: alsa_output.pci-_01_00.1.hdmi-stereo Description: Turks HDMI Audio [Radeon HD 6000 Series] Digital Stereo (HDMI) Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 4 Mute: no Volume: 0: 100% 1: 100% 0: 0.00 dB 1: 0.00 dB balance 0.00 Base Volume: 100% 0.00 dB Monitor Source: alsa_output.pci-_01_00.1.hdmi-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE DECIBEL_VOLUME LATENCY SET_FORMATS Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "HDMI 0" alsa.id = "HDMI 0" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "3" alsa.card = "1" alsa.card_name = "HD-Audio Generic" alsa.long_card_name = "HD-Audio Generic at 0xfddfc000 irq 48" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:01:00.1" sysfs.path = "/devices/pci:00/:00:02.0/:01:00.1/sound/card1" device.bus = "pci" device.vendor.id = "1002" device.vendor.name = "Advanced Micro Devices [AMD] nee ATI" device.product.name = "Turks HDMI Audio [Radeon HD 6000 Series]" device.string = "hdmi:1" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "hdmi-stereo" device.profile.description = "Digital Stereo (HDMI)" device.description = "Turks HDMI Audio [Radeon HD 6000 Series] Digital Stereo (HDMI)" alsa.mixer_name = "ATI R6xx HDMI" alsa.components = "HDA:1002aa01,00aa0100,00100200" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: hdmi-output-0: HDMI / DisplayPort (priority: 5900, not available) Active Port: hdmi-output-0 Formats: pcm I checked before and after. The only difference is hdmi-output-0: HDMI / DisplayPort (priority: 5900, not available) Where "not available" is the only change I found. Removing cable from HDMI socket and plugging in again, restores audio. Logging in and out again restores audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1001842/+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 1634149] [NEW] package gnome-session-bin 3.18.1.2-1ubuntu1.16.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem
Public bug reported: On trying to install updates I've got this error message. I don't really know what I'm doing or why its happened but I suspect its to do with my graphics card on my laptop which is an ATI mobility Radeon HD 5650 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-session-bin 3.18.1.2-1ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 17 14:52:25 2016 DuplicateSignature: package:gnome-session-bin:3.18.1.2-1ubuntu1.16.04.2 Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ... dpkg: error processing package gnome-session-bin (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-09-26 (21 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: gnome-session Title: package gnome-session-bin 3.18.1.2-1ubuntu1.16.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1634149 Title: package gnome-session-bin 3.18.1.2-1ubuntu1.16.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnome-session package in Ubuntu: New Bug description: On trying to install updates I've got this error message. I don't really know what I'm doing or why its happened but I suspect its to do with my graphics card on my laptop which is an ATI mobility Radeon HD 5650 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-session-bin 3.18.1.2-1ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 17 14:52:25 2016 DuplicateSignature: package:gnome-session-bin:3.18.1.2-1ubuntu1.16.04.2 Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ... dpkg: error processing package gnome-session-bin (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-09-26 (21 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: gnome-session Title: package gnome-session-bin 3.18.1.2-1ubuntu1.16.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1634149/+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 1628184] [NEW] Cannot cancel changing SSH passphrase in seahorse
Public bug reported: Problem: If a user starts the changing passphrase process in seahorse, but clicks cancel after entering the current passphrase, the passphrase is changed to be empty. Expected: Clicking cancel when prompted to enter a new passphrase should result in no change to the current passphrase. Steps to reproduce: - User has SSH key with nonempty passphrase - Launch seahorse, navigate to SSH key properties, select "Change Passphrase" - Enter current passphrase - Click "Cancel" button twice ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: seahorse 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 11:52:12 2016 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2016-09-23 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, user) SHELL=/usr/bin/fish LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1628184 Title: Cannot cancel changing SSH passphrase in seahorse Status in seahorse package in Ubuntu: New Bug description: Problem: If a user starts the changing passphrase process in seahorse, but clicks cancel after entering the current passphrase, the passphrase is changed to be empty. Expected: Clicking cancel when prompted to enter a new passphrase should result in no change to the current passphrase. Steps to reproduce: - User has SSH key with nonempty passphrase - Launch seahorse, navigate to SSH key properties, select "Change Passphrase" - Enter current passphrase - Click "Cancel" button twice ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: seahorse 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 11:52:12 2016 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2016-09-23 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, user) SHELL=/usr/bin/fish LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1628184/+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 1596532] Re: package nvidia-opencl-icd-361 361.45.11-0ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 5
HDMI sound is somehow not working with the newest driver as well -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1596532 Title: package nvidia-opencl-icd-361 361.45.11-0ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 5 Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Bug description: Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: warning: subprocess old pre-removal script returned error exit status 5 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/nvidia-opencl-icd-361_361.45.11-0ubuntu3_i386.deb (--unpack): there is no script in the new version of the package - giving up Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.23-0ubuntu3) ... Errors were encountered while processing: /var/cache/apt/archives/nvidia-opencl-icd-361_361.45.11-0ubuntu3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.10 Package: nvidia-opencl-icd-361 361.45.11-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic i686 ApportVersion: 2.20.2-0ubuntu1 AptOrdering: nvidia-opencl-icd-361: Purge nvidia-prime: Purge nvidia-settings: Purge NULL: ConfigurePending Architecture: i386 Date: Thu Jun 23 19:15:09 2016 Dependencies: gcc-6-base 6.1.1-7ubuntu11 libc6 2.23-0ubuntu3 libgcc1 1:6.1.1-7ubuntu11 ocl-icd-libopencl1 2.2.9-1 DpkgTerminalLog: Removing nvidia-opencl-icd-361 (361.45.11-0ubuntu2) ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. [1mdpkg:[0m error processing package nvidia-opencl-icd-361 (--purge): subprocess installed pre-removal script returned error exit status 5 ErrorMessage: subprocess installed pre-removal script returned error exit status 5 InstallationDate: Installed on 2016-05-12 (45 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160512) RelatedPackageVersions: dpkg 1.18.7ubuntu1 apt 1.3~exp1 SourcePackage: nvidia-graphics-drivers-361 Title: package nvidia-opencl-icd-361 361.45.11-0ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1596532/+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 1598004] [NEW] no audio
Public bug reported: audio stopped working after update to 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Jun 30 23:16:48 2016 InstallationDate: Installed on 2014-04-17 (806 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140415) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2016-06-04 (26 days ago) dmi.bios.date: 03/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET39WW (1.16 ) dmi.board.name: 786035U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET39WW(1.16):bd03/21/2012:svnLENOVO:pn786035U:pvrThinkPadL520:rvnLENOVO:rn786035U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 786035U dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1598004 Title: no audio Status in alsa-driver package in Ubuntu: New Bug description: audio stopped working after update to 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Jun 30 23:16:48 2016 InstallationDate: Installed on 2014-04-17 (806 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140415) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2016-06-04 (26 days ago) dmi.bios.date: 03/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET39WW (1.16 ) dmi.board.name: 786035U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET39WW(1.16):bd03/21/2012:svnLENOVO:pn786035U:pvrThinkPadL520:rvnLENOVO:rn786035U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 786035U dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1598004/+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 1583624] Re: Mir cannot open a tty when started by lightdm
Forgive my incoherent ramble in #9... Keep this open until lp:~robert-
ancell/lightdm/new-mir-socket-variable lands :-p Also, the new issue is
probably best explained by looking at lp:~mterry/lightdm/initialize-
more/+merge/296836
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
Status in Light Display Manager:
In Progress
Status in Light Display Manager 1.18 series:
In Progress
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Xenial:
Triaged
Bug description:
From mir-greeter.log (and with minor instrumentation from RAOF)
ERROR: QMirServer - Mir failed to start
qtmir.screens: ScreenController::ScreenController
qtmir.mir: MirServer created
qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8",
"--mode=greeter")
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
Throw in function
mir::DefaultServerConfiguration::the_graphics_platform()::
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Exception while creating graphics platform
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
Throw in function int
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Failed to find the current VT. Tried:
/dev/tty0:
Failed to open read-only: Permission denied
Failed to open write-only: Permission denied
/dev/tty:
Failed to open read-only: No such device or address
Failed to open write-only: No such device or address
This occurs when trying to start the unity8 greeter under unity system
compositor
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1583624/+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 1583624] Re: Mir cannot open a tty when started by lightdm
The root cause is the fd that pipe gives to USC is 0. The compositor
starts and begins drawing frames, and lightdm eventually tries writing
to fd=0 (also known as STDIN) which causes an Opperation not permitted
error (see lp:1590447). I wrote a nasty patch that forces lightdm to
keep obtaining file descriptors until fd[0]!=0 and it solved all the
(known) issues that we are seeing.
Mterry and I are workin on a fix for this ^^ and I'll work on the log
name issue right after. I think we can close this bug, as the original
issue has long since been resolved. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
Status in Light Display Manager:
In Progress
Status in Light Display Manager 1.18 series:
In Progress
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Xenial:
Triaged
Bug description:
From mir-greeter.log (and with minor instrumentation from RAOF)
ERROR: QMirServer - Mir failed to start
qtmir.screens: ScreenController::ScreenController
qtmir.mir: MirServer created
qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8",
"--mode=greeter")
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
Throw in function
mir::DefaultServerConfiguration::the_graphics_platform()::
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Exception while creating graphics platform
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
Throw in function int
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Failed to find the current VT. Tried:
/dev/tty0:
Failed to open read-only: Permission denied
Failed to open write-only: Permission denied
/dev/tty:
Failed to open read-only: No such device or address
Failed to open write-only: No such device or address
This occurs when trying to start the unity8 greeter under unity system
compositor
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1583624/+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 1583624] Re: Mir cannot open a tty when started by lightdm
I got the greeter working, but there are 2 other issues. The following
assumes you are using the unity8 greeter to launch a unity7 session
if (seat-type == unity)
The greeter loads, authenticates, a black screen is briefly shown, and the
greeter comes back up. My theory here is that lightdm is trying to start unity7
on the same VT as the greeter, and this is making USC mad. I believe this will
be fixed in USC in the future, but is there a work around we could have for the
time being?
if (seat-type == xlocal)
The log in /var/log/lightdm for the greeter is called (null)-greeter.log. I
think this is because the code path taken doesn't call display_server_set_name
in time. I used to know the answer to this, but I've since forgotten. I'm going
to dig into this part further today, but if you have input, let me know.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
Status in Light Display Manager:
In Progress
Status in Light Display Manager 1.18 series:
In Progress
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Xenial:
Triaged
Bug description:
From mir-greeter.log (and with minor instrumentation from RAOF)
ERROR: QMirServer - Mir failed to start
qtmir.screens: ScreenController::ScreenController
qtmir.mir: MirServer created
qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8",
"--mode=greeter")
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
Throw in function
mir::DefaultServerConfiguration::the_graphics_platform()::
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Exception while creating graphics platform
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
Throw in function int
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Failed to find the current VT. Tried:
/dev/tty0:
Failed to open read-only: Permission denied
Failed to open write-only: Permission denied
/dev/tty:
Failed to open read-only: No such device or address
Failed to open write-only: No such device or address
This occurs when trying to start the unity8 greeter under unity system
compositor
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1583624/+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 1583624] Re: Mir cannot open a tty when started by lightdm
Here is mir-greeter.log using your instrumented lightdm and changing the
unity8 seat type to unity.
http://pastebin.ubuntu.com/16932129/
Thoughts?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
Status in Light Display Manager:
In Progress
Status in Light Display Manager 1.18 series:
In Progress
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Xenial:
Triaged
Bug description:
From mir-greeter.log (and with minor instrumentation from RAOF)
ERROR: QMirServer - Mir failed to start
qtmir.screens: ScreenController::ScreenController
qtmir.mir: MirServer created
qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8",
"--mode=greeter")
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
Throw in function
mir::DefaultServerConfiguration::the_graphics_platform()::
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Exception while creating graphics platform
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
Throw in function int
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Failed to find the current VT. Tried:
/dev/tty0:
Failed to open read-only: Permission denied
Failed to open write-only: Permission denied
/dev/tty:
Failed to open read-only: No such device or address
Failed to open write-only: No such device or address
This occurs when trying to start the unity8 greeter under unity system
compositor
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1583624/+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 1583624] Re: Mir cannot open a tty when started by lightdm
I get
[+0.01s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)'
failed
in the logs (or when running in test mode). This only happens when
trying to run under Mir. Meaning I can delete 51-unity8-greeter.conf and
lightdm starts just fine. The error happens before usc/mir are able to
log anything.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
Status in Light Display Manager:
In Progress
Status in Light Display Manager 1.18 series:
In Progress
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Xenial:
Triaged
Bug description:
From mir-greeter.log (and with minor instrumentation from RAOF)
ERROR: QMirServer - Mir failed to start
qtmir.screens: ScreenController::ScreenController
qtmir.mir: MirServer created
qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8",
"--mode=greeter")
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
Throw in function
mir::DefaultServerConfiguration::the_graphics_platform()::
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Exception while creating graphics platform
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
Throw in function int
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
Dynamic exception type:
boost::exception_detail::clone_impl
>
std::exception::what: Failed to find the current VT. Tried:
/dev/tty0:
Failed to open read-only: Permission denied
Failed to open write-only: Permission denied
/dev/tty:
Failed to open read-only: No such device or address
Failed to open write-only: No such device or address
This occurs when trying to start the unity8 greeter under unity system
compositor
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1583624/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Dude no one cares this is a bug reporting place not an opinion catcher. On 12 Aug 2015 11:46, "teo1978" wrote: > > Please keep your subjective comments to yourself > > I think my comments were pretty objective. > Ubuntu fails at providing a decent user experience, and it's getting worse. > Ubuntu sucks at supporting NVidia (which is probably mostly NVidia's > fault, but other distros do better nonetheless). > Ubuntu spends very little effort in improving its desktop operating system > since their interest have moved to mobile. > Ubuntu fails at fixing bugs in a decent time. > > Now all of this may well be OT here, but they are facts, with little > margin of subjectivity. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1412043). > https://bugs.launchpad.net/bugs/1431753 > > Title: > Nvidia binary driver FTBS due to DKMS layer violation > > Status in nvidia-graphics-drivers-331 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-331-updates package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-340-updates package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-346 package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-346-updates package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-331 source package in Trusty: > Triaged > Status in nvidia-graphics-drivers-331-updates source package in Trusty: > Triaged > Status in nvidia-graphics-drivers-340 source package in Trusty: > Fix Released > Status in nvidia-graphics-drivers-340-updates source package in Trusty: > Fix Released > Status in nvidia-graphics-drivers-346 source package in Trusty: > Fix Released > Status in nvidia-graphics-drivers-346-updates source package in Trusty: > Fix Released > > Bug description: > Filing this against the 340-updates version but possibly the same > applies to older versions, too. The nvidia source package produces two > individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. > The problem is that the DKMS build of the nvidia-uvm module runs > compile steps inside the nvidia modules build directory. This is > violating the DKMS assumption that each module can be build > independently (there is no way of describing cross-modules > dependencies and even more important, the autoinstall step after a new > kernel is installed will run the modules build in parallel). > > Since nvidia and nvidia-uvm are very dependent on each other the right > course of action seems to be to combine both sources in one DKMS > module that produces two kernel modules (this is supported by DKMS). > For the transition this resulting dkms package needs to have a > breaks/replaces for the nvidia-uvm package. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produ
[Desktop-packages] [Bug 1371928] Re: Main window content fully transparent
This happens consistently in my installation. It makes GIMP impossible to use. Please let me know if I can provide any info that will help debug the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1371928 Title: Main window content fully transparent Status in gimp package in Ubuntu: Confirmed Bug description: Sometimes when I launch Gimp, the main window is fully transparent with the exception of the normal frame (title bar, buttons, ...). The only way to fix the problem is to exit and restart Gimp. Ubutun 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1371928/+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 504461] Re: Various Lintian errors
** Changed in: libgdiplus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgdiplus in Ubuntu. https://bugs.launchpad.net/bugs/504461 Title: Various Lintian errors Status in libgdiplus package in Ubuntu: Confirmed Bug description: Binary package hint: libgdiplus Just rebuilt libgdiplus for some font issue debugging; noticed that Lintian picked up these at the end: W: libgdiplus: non-dev-pkg-with-shlib-symlink usr/lib/libgdiplus.so.0.0.0 usr/lib/libgdiplus.so E: libgdiplus: no-shlibs-control-file usr/lib/libgdiplus.so.0.0.0 W: libgdiplus: package-name-doesnt-match-sonames libgdiplus0 Ideally they should be fixed, or Lintian overrides included in the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgdiplus/+bug/504461/+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 562468] Re: No way to save video configuration in Lucid Beta 2
But I filed the bug when the version *was* supported. It seems like, because it took so long for you to check the bug that the version it was reported on became unsupported, it should be your job to check if the problem exists in the currently supported version and update the bug accordingly. Instead of just waiting for bugs to become invalid because you've moved on to a new version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/562468 Title: No way to save video configuration in Lucid Beta 2 Status in nvidia-graphics-drivers package in Ubuntu: Invalid Bug description: Binary package hint: xorg In Lucid there is no user-facing way to save the video configuration because of a catch 22. Here is how to replicate: 1. Go to System -> Preferences -> Monitors 2. Get an error: "It appears that your graphics card does not support the necessary extensions to use this tool. Do you want to use your graphics vendor's tool instead?" 3. Click Yes 4. NVidia X Server Settings program is launched 5. Change some settings 6. NVidia X Server Settings can only save to xorg.conf. Go to X Server Display Configuration -> Save to X Configuration File 7. Get error because Lucid does not use xorg.conf: "Failed to parse existing X config file" 8. Click OK 9. Get prompted to specify the location of the file 10. Can't specify the location because it doesn't exist 11. Click Save anyways 12. Get error: "Unable to remove old X config backup" So the catch 22 is: I can't use Ubuntu's tool to enable my second monitor because my video device isn't supported by it, however I can't use NVidia's tool because Ubuntu Lucid doesn't support xorg.conf. So, every time I reboot I have to launch NVidia's configuration tool and re-configure all of my video settings. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Apr 13 10:56:05 2010 DkmsStatus: vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed nvidia-173, 173.14.22, 2.6.32-19-generic, x86_64: installed MachineType: Dell Inc. Precision WorkStation 670 ProcCmdLine: root=UUID=779cb9b5-cc1e-49ac-b9d5-116eea473d9f ro quiet splash vga=789 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 03/15/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0U7565 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd03/15/2006:svnDellInc.:pnPrecisionWorkStation670:pvr:rvnDellInc.:rn0U7565:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: Precision WorkStation 670 dmi.sys.vendor: Dell Inc. system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/562468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Nima this really isn't the place for that talk. Will EVERYONE please keep this thread on topic about this bug and only this bug please On 19 Jun 2015 21:51, "Nima" wrote: > I want to go to another linux distribution , > Can any body give me a hint about it? > CentOS or Opensuse? Which one is better? > which one has a full resource of software like ,for example "ubuntu > software center"? > Thanks for any help in advance > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1412043). > https://bugs.launchpad.net/bugs/1431753 > > Title: > Nvidia binary driver FTBS due to DKMS layer violation > > Status in nvidia-graphics-drivers-331 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-331-updates package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-340-updates package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-346 package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-346-updates package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-331 source package in Trusty: > Triaged > Status in nvidia-graphics-drivers-331-updates source package in Trusty: > Triaged > Status in nvidia-graphics-drivers-340 source package in Trusty: > Confirmed > Status in nvidia-graphics-drivers-340-updates source package in Trusty: > Confirmed > Status in nvidia-graphics-drivers-346 source package in Trusty: > Confirmed > Status in nvidia-graphics-drivers-346-updates source package in Trusty: > Confirmed > > Bug description: > Filing this against the 340-updates version but possibly the same > applies to older versions, too. The nvidia source package produces two > individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. > The problem is that the DKMS build of the nvidia-uvm module runs > compile steps inside the nvidia modules build directory. This is > violating the DKMS assumption that each module can be build > independently (there is no way of describing cross-modules > dependencies and even more important, the autoinstall step after a new > kernel is installed will run the modules build in parallel). > > Since nvidia and nvidia-uvm are very dependent on each other the right > course of action seems to be to combine both sources in one DKMS > module that produces two kernel modules (this is supported by DKMS). > For the transition this resulting dkms package needs to have a > breaks/replaces for the nvidia-uvm package. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-driv
[Desktop-packages] [Bug 1005914] Re: gnome-screenshot produces black screenshot with only the mouse pointer visible
Same issue here but with LinuxMint 17.1 running on VirtualBox 4.3.28 r100309 running on a WIn7 host. 3D acceleration enabled; screenshot works correctly when disabling 3D acceleration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1005914 Title: gnome-screenshot produces black screenshot with only the mouse pointer visible Status in compiz package in Ubuntu: Confirmed Status in gnome-screenshot package in Ubuntu: Confirmed Status in recordmydesktop package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: I am running Ubuntu 12.04 inside Virtualbox on a Windows host. 3D acceleration is enabled in Virtualbox and I am using compiz + unity, NOT unity2d. gnome-screenshot produces black screenshot with only the mouse pointer visible. it does not matter if I run it by pressing the PrintScreen key or running gnome-screenshot -d 5 in a terminal. WORKAROUND: use unity2d instead of compiz+unity ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 29 15:59:15 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1005914/+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 1324361] Re: Screen blank after resuming from suspend
Worked! Thank you so much for your attention. I updated the BIOS to A07 per the links you sent and it finally works like a charm! -- 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/1324361 Title: Screen blank after resuming from suspend Status in xorg package in Ubuntu: Incomplete Bug description: I can successfully suspend my Ubuntu session. After hitting the power button on my desktop to wake up, the computer and monitor turn back on ok, but the screen comes up blank. The mouse is present and can move, but there is nothing to interact with. I also cannot switch to other terminal modes with Ctrl-Alt-F2, etc. The only way to recover is to hard boot. I tried booting with both S1 and S3 power management modes set in the bios; S1 does not suspend at all (gives errors) and S3 suspends but does not wake up properly as described. I am running Ubuntu 14.04 with Gnome Shell 3.12.1, but the issue persists with standard Unity Ubuntu as well. I have dual monitors with an NVIDIA GeForce 8400 GS rev 3 PCI express adapter using nouveau drivers. I am running full disk encryption; home folder is not encrypted. Any advise is much appreciated. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed May 28 21:56:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1301] InstallationDate: Installed on 2014-05-04 (24 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) MachineType: Dell Inc. OptiPlex 360 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0T656F dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/28/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 360 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed May 28 21:55:06 2014 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1324361/+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 1416951] [NEW] RhythmBox fails to load mp3 plugin
Public bug reported: When trying to set the "preferred format" in the Music tab under Rhythmbox Preferences, a dialog box pops up: Required plugin could not be found Rhythmbox requires to install plugins to create media files of the following type: ID3 tag muxer. I would expect that the plugin could be installed. I pointed rhythmbox to my music folder, which contains a large number of mp3/4 copied over from iTunes (mac). I think this could be related to this bug: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/527475 I attached an edited debug file, which I generated with the command: rhythmbox --debug &> rhythmbox-debug.txt lsb_release -rd Description:Ubuntu 14.10 Release:14.10 apt-cache policy rhythmbox rhythmbox: Installed: 3.0.3-1ubuntu2 Candidate: 3.0.3-1ubuntu2 Version table: *** 3.0.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: rhythmbox 3.0.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 1 21:03:09 2015 EcryptfsInUse: Yes SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: "rhythmbox-debug.txt" https://bugs.launchpad.net/bugs/1416951/+attachment/4310146/+files/rhythmbox-debug.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1416951 Title: RhythmBox fails to load mp3 plugin Status in rhythmbox package in Ubuntu: New Bug description: When trying to set the "preferred format" in the Music tab under Rhythmbox Preferences, a dialog box pops up: Required plugin could not be found Rhythmbox requires to install plugins to create media files of the following type: ID3 tag muxer. I would expect that the plugin could be installed. I pointed rhythmbox to my music folder, which contains a large number of mp3/4 copied over from iTunes (mac). I think this could be related to this bug: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/527475 I attached an edited debug file, which I generated with the command: rhythmbox --debug &> rhythmbox-debug.txt lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 apt-cache policy rhythmbox rhythmbox: Installed: 3.0.3-1ubuntu2 Candidate: 3.0.3-1ubuntu2 Version table: *** 3.0.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: rhythmbox 3.0.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 1 21:03:09 2015 EcryptfsInUse: Yes SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1416951/+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 1399953] Re: Google contacts authentication problem with U-O-A (Trusty, Vivid - Unity7)
I deleted my default keyring and all accounts in UOA. After a restart, I
re-created the online accounts and a new default keyring. The Google
Contacts worked the first time I opened Evolution; however, it failed
again after subsequent restarts/reopening.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1399953
Title:
Google contacts authentication problem with U-O-A (Trusty,Vivid -
Unity7)
Status in account-plugins package in Ubuntu:
Confirmed
Status in evolution-data-server package in Ubuntu:
Confirmed
Bug description:
I simply can not access Google-Contacts with Ubuntu Online Accounts.
After I enabled EDS contacts, If I open evolution & click on the
address-book list, it shows following error:
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code5:
Authentication required".
I tried to revoke access for UOA from google accounts, & re-authorize
it. But it did not help. However google-calendar integration is
working fine. And if log into gnome-shell & add my Google account in
Gnome-Online-Accounts(G-O-A), contacts works as well. The problem only
appearing for google-contacts in UOA. And I couldn't find anything
significant in syslog.
I have multiple google accounts enabled in UOA.
Here is some more information:
khurshid@mypc:~$ ag-tool list-enabled 11
--
Type Service Name
IM google-im
contacts google-contacts
documents google-drive
khurshid@mypc:~$ account-console show 11 | grep Cred
--
CredentialsId: 14 ()
khurshid@mypc:~$ strings ~/.cache/signon-ui/cookies/14.jar
---
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1399953/+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 1398840] Re: dual monitors do not work on Mac Pro black cylinder
For what it is worth, dual monitors work in Fedora 21. $ xrandr -q Screen 0: minimum 320 x 200, current 3280 x 1200, maximum 16384 x 16384 DisplayPort-6 disconnected (normal left inverted right x axis y axis) DisplayPort-7 disconnected (normal left inverted right x axis y axis) DisplayPort-8 disconnected (normal left inverted right x axis y axis) DisplayPort-9 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm 1600x1200 60.00*+ 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0860.00 800x600 75.0060.32 640x480 75.0060.00 720x400 70.08 DisplayPort-10 connected 1680x1050+1600+0 (normal left inverted right x axis y axis) 433mm x 270mm 1680x1050 59.95*+ 1280x1024 75.0260.02 1440x900 59.89 1280x800 59.81 1152x864 75.00 1280x720 59.97 1024x768 75.0870.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6760.00 720x400 70.08 DisplayPort-11 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1-1 disconnected (normal left inverted right x axis y axis) DisplayPort-1-2 disconnected (normal left inverted right x axis y axis) DisplayPort-1-3 disconnected (normal left inverted right x axis y axis) DisplayPort-1-4 disconnected (normal left inverted right x axis y axis) # lshw -C display; lsb_release -a; uname -a *-display description: VGA compatible controller product: Tahiti LE [Radeon HD 7870 XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:02:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:47 memory:8000-8fff memory:a070-a073 ioport:3000(size=256) memory:a074-a075 *-display description: VGA compatible controller product: Tahiti LE [Radeon HD 7870 XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:06:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:49 memory:9000-9fff memory:a060-a063 ioport:2000(size=256) memory:a064-a065 LSB Version::core-4.1-amd64:core-4.1-noarch Distributor ID: Fedora Description:Fedora release 21 (Twenty One) Release:21 Codename: TwentyOne Linux inl426935 3.17.8-300.fc21.x86_64 #1 SMP Thu Jan 8 23:32:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- 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/1398840 Title: dual monitors do not work on Mac Pro black cylinder Status in xorg package in Ubuntu: New Bug description: How do I get dual monitors working on a Mac Pro cylinder? I have two thunderbolt connected displays (one on a minidisplay port to dvi connector, and the other on a mini displayport to vga connector). If I plug only one in, it works. If I plug both in at boot up, than one of them will work randomly, and the other will not work at all. xrandr -q only shows the working one: $ xrandr -q xrandr: Failed to get size of gamma for output default Screen 0: minimum 1600 x 1200, current 1600 x 1200, maximum 1600 x 1200 default connected primary 1600x1200+0+0 0mm x 0mm 1600x1200 77.0* I am using the kernel parameter nomodeset or video does not work at all. I am trying on Ubuntu 14.04 with kernel 3.13.0.39.46. # lshw -C display; lsb_release -a; uname -a *-display UNCLAIMED description: VGA compatible controller product: Tahiti LE [Radeon HD 7870 XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:02:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:8000-8fff memory:a070-a073 ioport:3000(size=256) memory:a074-a075 *-display UNCLAIMED description: VGA compatible controller product: Tahiti LE [Radeon HD 7870 XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:06:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:9000-9fff memory:a06000
[Desktop-packages] [Bug 1412043] [NEW] nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build
Public bug reported: after updating this error was produced ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Tue Jan 13 18:55:24 2015 InstallationDate: Installed on 2014-12-07 (41 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1412043 Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: after updating this error was produced ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Tue Jan 13 18:55:24 2015 InstallationDate: Installed on 2014-12-07 (41 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1412043/+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 1411982] [NEW] Firefox HTML5 Sound Doesn't work with ALSA Jack Plugin
Public bug reported: This is not an Ubuntu specific bug, but rather a bug in the version of the alsa jack plugin that comes with Trusty (exists in any release before 1.0.28 of the plugin). Here is a bug report from the Mozilla database that describes the problem in more detail: https://bugzilla.mozilla.org/show_bug.cgi?id=812900 The basic issue is that if you use a .asoundrc file to route alsa sound through Jack Audio via the alsa-jack plugin, HTML5 sound doesn't work properly in Firefox. There are probably other affected apps as well. ** Affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1411982 Title: Firefox HTML5 Sound Doesn't work with ALSA Jack Plugin Status in alsa-plugins package in Ubuntu: New Bug description: This is not an Ubuntu specific bug, but rather a bug in the version of the alsa jack plugin that comes with Trusty (exists in any release before 1.0.28 of the plugin). Here is a bug report from the Mozilla database that describes the problem in more detail: https://bugzilla.mozilla.org/show_bug.cgi?id=812900 The basic issue is that if you use a .asoundrc file to route alsa sound through Jack Audio via the alsa-jack plugin, HTML5 sound doesn't work properly in Firefox. There are probably other affected apps as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1411982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
I know right! On 14 Jan 2015 13:36, "Michael Heuberger" < michael.heuber...@binarykitchen.com> wrote: > Unsubscribe me! How can I stop getting more emails? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1397425). > https://bugs.launchpad.net/bugs/1268257 > > Title: > nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module > failed to build, with only error: "objdump: '... .tmp_nv.o': No such > file" > > Status in nvidia-graphics-drivers-331 package in Ubuntu: > In Progress > Status in nvidia-graphics-drivers-331-updates package in Ubuntu: > Triaged > > Bug description: > Nvidia kernel module failed to build on kernel 3.13.0-2 > Yesterday when the new kernel was pushed, the dkms process failed. > > ProblemType: Package > DistroRelease: Ubuntu 14.04 > Package: nvidia-331-updates 331.20-0ubuntu9 > ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 > Uname: Linux 3.12.0-7-generic x86_64 > ApportVersion: 2.13.1-0ubuntu1 > Architecture: amd64 > DKMSKernelVersion: 3.13.0-2-generic > Date: Sun Jan 12 01:28:35 2014 > InstallationDate: Installed on 2013-11-03 (69 days ago) > InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 > (20131016.1) > PackageVersion: 331.20-0ubuntu9 > SourcePackage: nvidia-graphics-drivers-331-updates > Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel > module failed to build > UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" Status in nvidia-graphics-drivers-331 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Bug description: Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+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 1400956] [NEW] error when trying to open nautilus w/root permissions
Public bug reported: In terminal: sudo nautilus (nautilus:20736): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files I am running latest version of ubuntu ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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 Date: Tue Dec 9 18:08:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0690] InstallationDate: Installed on 2014-12-07 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire E1-521 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=543254da-f995-4a3a-ad68-ceafebaa83ed ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.05 dmi.board.asset.tag: No Asset Tag dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.05:bd09/11/2012:svnAcer:pnAspireE1-521:pvrV2.05:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-521 dmi.product.version: V2.05 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Dec 9 16:23:02 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400956 Title: error when trying to open nautilus w/root permissions Status in xorg package in Ubuntu: New Bug description: In terminal: sudo nautilus (nautilus:20736): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files I am running latest version of ubuntu ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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 Date: Tue Dec 9 18:08:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0690] InstallationDate: Installed on 2014-12-07 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer Aspire E1-521 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=543254da-f995-4a3a-ad68-ceafebaa83ed ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.b
[Desktop-packages] [Bug 1397425] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
Public bug reported: ubuntu 14.10 error on restart ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 08:06:16 2014 InstallationDate: Installed on 2014-09-19 (70 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-24 (35 days ago) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1397425 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: ubuntu 14.10 error on restart ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 08:06:16 2014 InstallationDate: Installed on 2014-09-19 (70 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-24 (35 days ago) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1397425/+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 1397242] [NEW] nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build
Public bug reported: happens when starting a user session at login time ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-26-generic Date: Fri Nov 28 00:36:53 2014 InstallationDate: Installed on 2013-07-31 (484 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-11 (47 days ago) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1397242 Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: happens when starting a user session at login time ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-26-generic Date: Fri Nov 28 00:36:53 2014 InstallationDate: Installed on 2013-07-31 (484 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-11 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397242/+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 1140716]
I am also experiencing this, on a Gentoo system running on a ThinkPad T440s. I'm not doing anything related to XBMC, simply using xrandr for multihead. The interesting thing is that DRI works fine on my laptop screen (glxgears reports 60fps, which is the refresh rate of my screen), but breaks when I move a window trying to use DRI (e.g. Chrome, glxgears) to the external monitor connected to the mini Display Port output. I see this stuff in dmesg: [ 3561.424762] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring [ 3561.424770] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 3561.424772] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 3561.424774] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 3561.424776] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 3561.424778] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 3566.422957] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring [ 3571.425143] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring [ 3575.423680] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring Seems like the same issue. I'm trying to downgrade X, mesa, et al., to try and get the system back in working order. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a "system error". This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [] warn_slowpath_common+0x7f/0xc0 [26285.658553] [] warn_slowpath_null+0x1a/0x20 [26285.658569] [] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [] i915_reset
[Desktop-packages] [Bug 1392447] [NEW] apport "starts" even when not installed
Public bug reported: When removed (but not purged), apport leaves /etc/init/apport.conf and /etc/init.d/apport, which is enough for commands like "service apport start" to work. "service apport start" runs without complaining and overrides /proc/sys/kernel/core_pattern to send core dumps to apport, even though apport doesn't exist. Apport's service scripts should refuse to run if Apport isn't installed and, in particular, shouldn't break /proc/sys/kernel/core_pattern. Observed in Ubuntu 14.04.1, apport 2.14.1-0ubuntu3.5. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1392447 Title: apport "starts" even when not installed Status in “apport” package in Ubuntu: New Bug description: When removed (but not purged), apport leaves /etc/init/apport.conf and /etc/init.d/apport, which is enough for commands like "service apport start" to work. "service apport start" runs without complaining and overrides /proc/sys/kernel/core_pattern to send core dumps to apport, even though apport doesn't exist. Apport's service scripts should refuse to run if Apport isn't installed and, in particular, shouldn't break /proc/sys/kernel/core_pattern. Observed in Ubuntu 14.04.1, apport 2.14.1-0ubuntu3.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1392447/+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 1041790]
I am also experiencing this, on a Gentoo system running on a ThinkPad T440s. I'm not doing anything related to XBMC, simply using xrandr for multihead. The interesting thing is that DRI works fine on my laptop screen (glxgears reports 60fps, which is the refresh rate of my screen), but breaks when I move a window trying to use DRI (e.g. Chrome, glxgears) to the external monitor connected to the mini Display Port output. I see this stuff in dmesg: [ 3561.424762] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring [ 3561.424770] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 3561.424772] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 3561.424774] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 3561.424776] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 3561.424778] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 3566.422957] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring [ 3571.425143] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring [ 3575.423680] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring Seems like the same issue. I'm trying to downgrade X, mesa, et al., to try and get the system back in working order. -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0" run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1383445] [NEW] pg_createcluster should not silently ignore locale failure
Public bug reported: Ubuntu Version: 14.04 PostgreSQL version 9.3.5 The way it is now: 1. pg_createcluster will take a --locale switch, in order to initialize the cluster with default emplate databases using, for example, en_US or LATIN1. 2. if pg_createcluster is unable to initdb with that locale (for example, if it's missing in the environment), it **silently fails** and reports success, creating the cluster instead as SQL_ASCII, which format is deprecated by the PostgreSQL project. 3. At that point, the user can happily go on to load all of their data into a database in the wrong encoding, resulting in likely extensive downtimes later to fix the problem, and possible data corruption. The way it should be: On step 2, pg_createcluster should fail with an error message. This is per the documentation, which says that pg_createcluster will do this. However, it is inconsistent and user-hostile behavior, and should be changed. I do not know at this time whether this undesirable behavior is from the upstream Debian postgresql-common or not. ** Affects: postgresql-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1383445 Title: pg_createcluster should not silently ignore locale failure Status in “postgresql-common” package in Ubuntu: New Bug description: Ubuntu Version: 14.04 PostgreSQL version 9.3.5 The way it is now: 1. pg_createcluster will take a --locale switch, in order to initialize the cluster with default emplate databases using, for example, en_US or LATIN1. 2. if pg_createcluster is unable to initdb with that locale (for example, if it's missing in the environment), it **silently fails** and reports success, creating the cluster instead as SQL_ASCII, which format is deprecated by the PostgreSQL project. 3. At that point, the user can happily go on to load all of their data into a database in the wrong encoding, resulting in likely extensive downtimes later to fix the problem, and possible data corruption. The way it should be: On step 2, pg_createcluster should fail with an error message. This is per the documentation, which says that pg_createcluster will do this. However, it is inconsistent and user-hostile behavior, and should be changed. I do not know at this time whether this undesirable behavior is from the upstream Debian postgresql-common or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1383445/+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 1379502] Re: Volume is not remembered when using optical output
I can't replicate this bug anymore after the last system update. ** Changed in: unity-control-center (Ubuntu) Status: New => Invalid ** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) => Josh (majik) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1379502 Title: Volume is not remembered when using optical output Status in “unity-control-center” package in Ubuntu: Invalid Bug description: After a reboot, if the selected audio output is not the default analog output (ie optical or coaxial) the volume set by the user is forgotten and so the volume is set to maximum. This is a serious problem because it can damage hearing and equipment. If nothing else the default should be minimum volume, not maximum. Maximum volume should never be the default for anything. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 9 13:15:02 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-10-05 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1379502/+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 1379502] [NEW] Volume is not remembered when using optical output
Public bug reported: After a reboot, if the selected audio output is not the default analog output (ie optical or coaxial) the volume set by the user is forgotten and so the volume is set to maximum. This is a serious problem because it can damage hearing and equipment. If nothing else the default should be minimum volume, not maximum. Maximum volume should never be the default for anything. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 9 13:15:02 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-10-05 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1379502 Title: Volume is not remembered when using optical output Status in “unity-control-center” package in Ubuntu: New Bug description: After a reboot, if the selected audio output is not the default analog output (ie optical or coaxial) the volume set by the user is forgotten and so the volume is set to maximum. This is a serious problem because it can damage hearing and equipment. If nothing else the default should be minimum volume, not maximum. Maximum volume should never be the default for anything. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 9 13:15:02 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-10-05 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1379502/+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 763148] Re: Adding/Removing an external monitor causes open windows to move to another workspace
This bug is still affecting me on Trusty, version 1:0.9.11.2+14.04.20140714-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/763148 Title: Adding/Removing an external monitor causes open windows to move to another workspace Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Committed Status in Compiz Core: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Fix Released Bug description: [Impact] Many users will put different windows in different workspaces for better work flow. If a user connects and/or disconnects an external monitor or projector, all of these windows will be put in the first workspace. Having to go back and move all of the windows back to their workspaces is very frustrating and time consuming. [Test Case] #. Open some applications in different workspaces. #. Plug in an external monitor. [Regression Potential] Very low possibility that a window still ends up in the wrong workspace. Original description: well, i plug in my external screen. expected behaviour would be, if all of my windows would stay in the workspaces i aligned them to, and if they'd be on the same screen i had them in the first place. unfortunatly in unity, if i plug-in (or plug-off) my external screen the windows are all around, but not where i'd expect them to be (namely in the same place they were before). so i always have to toggle expo-mode and re-align all of my windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/763148/+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 1358338] [NEW] nvidia-331-updates 331.38-0ubuntu7.1: nvidia-331-updates kernel module failed to build
Public bug reported: It just crashed. Not sure what it means. Maybe if it were easier to install the latest driver from nvidia it wouldn't break. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DKMSKernelVersion: 3.13.0-34-generic Date: Mon Aug 18 09:26:00 2014 InstallationDate: Installed on 2014-03-18 (152 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.38-0ubuntu7.1: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1358338 Title: nvidia-331-updates 331.38-0ubuntu7.1: nvidia-331-updates kernel module failed to build Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: It just crashed. Not sure what it means. Maybe if it were easier to install the latest driver from nvidia it wouldn't break. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DKMSKernelVersion: 3.13.0-34-generic Date: Mon Aug 18 09:26:00 2014 InstallationDate: Installed on 2014-03-18 (152 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.38-0ubuntu7.1: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1358338/+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 1350473] [NEW] package gettext 0.18.1.1-5ubuntu3 failed to install/upgrade: gettext:i386 0.18.1.1-5ubuntu3 (Multi-Arch
Public bug reported: Upgraded from 11.10 to 12.04. Went to software center to install WINE. Popup asked if I wanted to submit report. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: gettext 0.18.1.1-5ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Jul 30 13:43:01 2014 DuplicateSignature: package:gettext:0.18.1.1-5ubuntu3:gettext:i386 0.18.1.1-5ubuntu3 (Multi-Arch ErrorMessage: gettext:i386 0.18.1.1-5ubuntu3 (Multi-Arch InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: gettext Title: package gettext 0.18.1.1-5ubuntu3 failed to install/upgrade: gettext:i386 0.18.1.1-5ubuntu3 (Multi-Arch UpgradeStatus: Upgraded to precise on 2014-07-30 (0 days ago) ** Affects: gettext (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1350473 Title: package gettext 0.18.1.1-5ubuntu3 failed to install/upgrade: gettext:i386 0.18.1.1-5ubuntu3 (Multi-Arch Status in “gettext” package in Ubuntu: New Bug description: Upgraded from 11.10 to 12.04. Went to software center to install WINE. Popup asked if I wanted to submit report. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: gettext 0.18.1.1-5ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Jul 30 13:43:01 2014 DuplicateSignature: package:gettext:0.18.1.1-5ubuntu3:gettext:i386 0.18.1.1-5ubuntu3 (Multi-Arch ErrorMessage: gettext:i386 0.18.1.1-5ubuntu3 (Multi-Arch InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: gettext Title: package gettext 0.18.1.1-5ubuntu3 failed to install/upgrade: gettext:i386 0.18.1.1-5ubuntu3 (Multi-Arch UpgradeStatus: Upgraded to precise on 2014-07-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1350473/+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 1305335] Re: nautilus fails to copy to ecryptfs Private folder on btrfs - all files 0 bytes
I just stumbled across this bug as well. Only noticed because I wasn't get thumbnails of an image I had just copied into my Private directory. I even tried using cp from the command line, so it's not a nautilus bug. Unfortunately I have no idea which (if any) files I lost as a result of this (I switched to btrfs over a month ago). Unmounting and re-mounting the Private directory causes the files to show up, even after deleting (I added the file, saw it was corrupted, deleted it, unmounted, remounted, and it was there). It wasn't 0 bytes, so there was data there. However it was still corrupt, and the md5sum differed from the original. I immediately copied everything out of my Private directory into a new directory. Everything went OK except for the corrupted file. It gave me input/output errors (on the original and the copies in .Trash), so I can only hope that the rest of the data is not corrupt. This is a VERY serious bug causing data loss with no warning to the user that it's happening. ** Also affects: ecryptfs Importance: Undecided Status: 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/1305335 Title: nautilus fails to copy to ecryptfs Private folder on btrfs - all files 0 bytes Status in eCryptfs: New Status in “nautilus” package in Ubuntu: Confirmed Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.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/ecryptfs/+bug/1305335/+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 1311403] Re: Can't type password after resume.
I'm running latest Utopic and I see this exact same issue as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in “lightdm” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+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 1335456] Re: Play queue extension doesn't fill by album properly
** Also affects: banshee via https://bugzilla.gnome.org/show_bug.cgi?id=726411 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1335456 Title: Play queue extension doesn't fill by album properly Status in Banshee Music Player: Unknown Status in “banshee” package in Ubuntu: New Bug description: When the play queue extension is set to randomly fill "by album", it only adds one album's worth of tracks regardless of how much space is free in the play queue. In addition the "add more" button hardly ever appears to do anything and when it does, it merely adds a single albums worth of tracks again. As a result the player quickly reaches the end of the play queue and starts playing tracks randomly from the library. Expected behaviour, as seen in 12.04, would be for the play queue to fill to its limit with tracks by album, e.g. when the limit is 100 tracks it should fill to that amount, not just a single album's worth of tracks. This is a definite regression between the versio packaged in 12.04 and the one in 14.04. I have not yet been able to build an upstream version of Banshee as: ⟫ sudo apt-get build-dep banshee Reading package lists... Done Building dependency tree Reading state information... Done E: Failed to satisfy Build-Depends dependency for banshee: Installed package libgpod-cil-dev is too new but I suspect it has the same issue as I could not find any similar issue reported in upstream's bugzilla. I have attempted to report this bug in upstream's bugzilla, but it requires me to create an account and doesn't seem to want to email me the verification link for that. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: banshee 2.9.0+really2.6.2-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 28 16:56:14 2014 SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/1335456/+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 1085706] Re: pam_ecryptfs: seteuid error
I can confirm this is still happening on Ubuntu 14.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: pam_ecryptfs: seteuid error Status in eCryptfs: Confirmed Status in GNOME Screensaver: New Status in “ecryptfs-utils” package in Ubuntu: Triaged Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “gnome-screensaver” package in Debian: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 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/ecryptfs/+bug/1085706/+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
