[Desktop-packages] [Bug 1883370] Re: system-config-printer hangs when trying to change driver
^LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1883370 Title: system-config-printer hangs when trying to change driver Status in System Config Printer: Fix Released Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Confirmed Status in system-config-printer source package in Groovy: Won't Fix Bug description: gnome-control-center is able to find and install my network printer (Samsung M287x) automatically. When I attempt to change the printer driver (default printer driver doesn't support duplex printing) via system-config-printer, system-config-printer will hang. Please see attached log captured via system-config-printer --debug. I am running stock Ubuntu 20.04. Changing the driver worked fine in ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 13 10:34:15 2020 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2020-05-17 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for M267x-287x: socket://192.168.1.166 MachineType: LENOVO 20KHCTO1WW PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M267x-287x.ppd'] failed with exit code 2: grep: /etc/cups/ppd/M267x-287x.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d86e16c0-e48c-492e-9cf8-05a068340cd7 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1883370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883370] Re: system-config-printer hangs when trying to change driver
Please fix this in 20.04 LTR (Focal), too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1883370 Title: system-config-printer hangs when trying to change driver Status in System Config Printer: Fix Released Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Confirmed Status in system-config-printer source package in Groovy: Won't Fix Bug description: gnome-control-center is able to find and install my network printer (Samsung M287x) automatically. When I attempt to change the printer driver (default printer driver doesn't support duplex printing) via system-config-printer, system-config-printer will hang. Please see attached log captured via system-config-printer --debug. I am running stock Ubuntu 20.04. Changing the driver worked fine in ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 13 10:34:15 2020 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2020-05-17 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for M267x-287x: socket://192.168.1.166 MachineType: LENOVO 20KHCTO1WW PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M267x-287x.ppd'] failed with exit code 2: grep: /etc/cups/ppd/M267x-287x.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d86e16c0-e48c-492e-9cf8-05a068340cd7 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1883370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate
I tried this by 20.04, but could not get sound via HDMI cable work, except once, even if I had sample rate 44100 set in daemon.conf. I wonder what is wrong. TV tells: "unknown audio signal, check the source." -- 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/1829364 Title: Will not play sound via HDMI using 48000 Hz sample rate Status in pulseaudio package in Ubuntu: Confirmed Bug description: Does not play sound when playing file that has 48000 Hz sample rate via sink output:iec958-stereo. This is when using proprietary nvidia-340 driver; when using nouveau driver, HDMI is not even recognized (Bug #1844129). Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics adapter) does not have real HDMI audio, but audio is somehow wired from motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000". Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023008] Re: cannot install libegl-mesa0 on 22.04.2 LTS
** Description changed: # Summary `apt install libegl-mesa0` does not install it due to a dependency conflict in the apt repo. libegl-mesa0 has dependency to explicit versions of: * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2. # Expected behavior These closely linked packages to be up-to-date in the Ubuntu repo. + + # Workaround + + It is possible to install libegl-mesa0 by first downgrading the + conflicting package versions: + + apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1 + apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1 + + and then installing it normally: + + apt install libegl-mesa0 + # Details - ``` # apt install libegl-mesa0 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: - libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed - Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed + libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed + Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed E: Unable to correct problems, you have held broken packages.` ``` 1) Is the hard dependency (=) really necessary? 2) Or should I just downgrade existing libglapi-mesa and libgbm1 installs? The difference is minor patch version only so I am hesitant to do so (there must have been a reasons for the .2 patch). # Environment - ## cat /etc/lsb-release + ## cat /etc/lsb-release ``` cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" ``` # apt-cache policy ``` apt-cache policy libegl-mesa0 libegl-mesa0: - Installed: (none) - Candidate: 22.2.5-0ubuntu0.1~22.04.1 - Version table: - 22.2.5-0ubuntu0.1~22.04.1 500 - 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages - 22.0.1-1ubuntu2 500 - 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages + Installed: (none) + Candidate: 22.2.5-0ubuntu0.1~22.04.1 + Version table: + 22.2.5-0ubuntu0.1~22.04.1 500 + 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + 22.0.1-1ubuntu2 500 + 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` -- 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/2023008 Title: cannot install libegl-mesa0 on 22.04.2 LTS Status in mesa package in Ubuntu: New Bug description: # Summary `apt install libegl-mesa0` does not install it due to a dependency conflict in the apt repo. libegl-mesa0 has dependency to explicit versions of: * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2. # Expected behavior These closely linked packages to be up-to-date in the Ubuntu repo. # Workaround It is possible to install libegl-mesa0 by first downgrading the conflicting package versions: apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1 apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1 and then installing it normally: apt install libegl-mesa0 # Details ``` # apt install libegl-mesa0 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed E: Unable to correct problems, you have held broken packages.` ``` 1) Is the hard dependency (=) really necessary? 2) Or should I just downgrade existing libglapi-mesa and libgbm1 installs? The difference is minor patch version only so I am hesitant to do so (there must have
[Desktop-packages] [Bug 2023008] [NEW] cannot install libegl-mesa0 on 22.04.2 LTS
Public bug reported: # Summary `apt install libegl-mesa0` does not install it due to a dependency conflict in the apt repo. libegl-mesa0 has dependency to explicit versions of: * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2. # Expected behavior These closely linked packages to be up-to-date in the Ubuntu repo. # Workaround It is possible to install libegl-mesa0 by first downgrading the conflicting package versions: apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1 apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1 and then installing it normally: apt install libegl-mesa0 # Details ``` # apt install libegl-mesa0 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed E: Unable to correct problems, you have held broken packages.` ``` 1) Is the hard dependency (=) really necessary? 2) Or should I just downgrade existing libglapi-mesa and libgbm1 installs? The difference is minor patch version only so I am hesitant to do so (there must have been a reasons for the .2 patch). # Environment ## cat /etc/lsb-release ``` cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" ``` # apt-cache policy ``` apt-cache policy libegl-mesa0 libegl-mesa0: Installed: (none) Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: 22.2.5-0ubuntu0.1~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 22.0.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: mesa -- 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/2023008 Title: cannot install libegl-mesa0 on 22.04.2 LTS Status in mesa package in Ubuntu: New Bug description: # Summary `apt install libegl-mesa0` does not install it due to a dependency conflict in the apt repo. libegl-mesa0 has dependency to explicit versions of: * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2. # Expected behavior These closely linked packages to be up-to-date in the Ubuntu repo. # Workaround It is possible to install libegl-mesa0 by first downgrading the conflicting package versions: apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1 apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1 and then installing it normally: apt install libegl-mesa0 # Details ``` # apt install libegl-mesa0 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed E: Unable to correct problems, you have held broken packages.` ``` 1) Is the hard dependency (=) really necessary? 2) Or should I just downgrade existing libglapi-mesa and libgbm1 installs? The difference is minor patch version only so I am hesitant to do so (there must have been a reasons for the .2 patch). # Environment ## cat /etc/lsb-release ``` cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" ``` # apt-cache policy ``` apt-cache policy libegl-mesa0 libegl-mesa0: Installed: (none) Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: 22.2.5-0ubuntu0.1~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 22.0.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` To manage notifications
[Desktop-packages] [Bug 1996927] Re: Nautilus send mail not working
bug still found on lunar -- 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/1996927 Title: Nautilus send mail not working Status in nautilus package in Ubuntu: Confirmed Bug description: Hi, After upgrade from 22.04 to 22.10 Send an attached file to email from nautilus is not working anymore. Menu sendmail ( courriel in french) appears when i right click on file , then thunderbird appears but without the attachement . It was working very well with previous releases . regards Yanick ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 17 18:42:19 2022 InstallationDate: Installed on 2021-10-16 (397 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996927] [NEW] Nautilus send mail not working
Public bug reported: Hi, After upgrade from 22.04 to 22.10 Send an attached file to email from nautilus is not working anymore. Menu sendmail ( courriel in french) appears when i right click on file , then thunderbird appears but without the attachement . It was working very well with previous releases . regards Yanick ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 17 18:42:19 2022 InstallationDate: Installed on 2021-10-16 (397 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1996927 Title: Nautilus send mail not working Status in nautilus package in Ubuntu: New Bug description: Hi, After upgrade from 22.04 to 22.10 Send an attached file to email from nautilus is not working anymore. Menu sendmail ( courriel in french) appears when i right click on file , then thunderbird appears but without the attachement . It was working very well with previous releases . regards Yanick ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 17 18:42:19 2022 InstallationDate: Installed on 2021-10-16 (397 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
** Also affects: lightdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in Light Display Manager: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. If I use Budgie Desktop instead of Xfce as desktop environment, it will automatically log out to the LightDM login screen, if I first try to start that Budgie session and then the HDMI output is used as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
** Summary changed: - Nvidia 340 Xorg driver is installed but not loaded after OS upgrade + Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. If I use Budgie Desktop instead of Xfce as desktop environment, it will automatically log out to the LightDM login screen, if I first try to start that Budgie session and then the HDMI output is used as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
** Description changed: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. + + If I use Budgie Desktop instead of Xfce as desktop environment, it will + automatically log out to the LightDM login screen, if I first try to + start that Budgie session and then the HDMI output is used as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
Related question: https://askubuntu.com/q/1370465/21005 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
Maybe lightdm could do something differently? What causes HDMI to appear when I log out of session? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
** Description changed: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. + + WORKAROUND when using nvidia driver: + Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
What does the "Report problem..." button in the dialog do, then if I have to use command line to report the crash files? I see "sudo nvidia-xconfig" generates some basic /etc/X11/xorg.conf file. Regardless, I noted the following: If I log out from the Xfce session back to the LightDM greeter the HDMI output is used, too. And if I thereafter log in back to my session, the HDMI output works there, too. I wonder why it does not work right after the first login after boot? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
BTW after every boot I see "System program problem detected?" dialog and every time I choose "Report problem...". I booted today, too. $ LC_ALL=C ls -l /var/crash/ total 4624 -rw-r- 1 jarnos whoopsie 1416740 Oct 14 11:05 _usr_bin_xfce4-power-manager.1000.crash -rw-r- 1 root whoopsie 3314750 Oct 13 16:03 _usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
Where can those differences be? I could compare to another machine with the same driver. The graphics card is different, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
Could there be something in upgrading process that caused this that clean install wouldn't have done? Could the relevant parts be clean installed now? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
One more thing. I get an error dialog after startup in the desktop. It does not tell what went wrong, but it has an option to report to developers and so I did. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
Hmm. I have another computer that is more successful with nvidia-340 in Xubuntu 20.04. When I compare to Xorg.0.log files, I see differences after line "(II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration". The successful one has "[77.338] (II) xfree86: Adding drm device (/dev/dri/card0) [77.341] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia-340/xorg,/usr/lib/xorg/modules" In the working system there doesn't seem to be a config file: "nvidia-xconfig -t" prints "WARNING: Unable to locate/open X configuration file. Unable to locate/open XConfig file." (with or without run as superuser) so I wonder why this failing one should have? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
I searched for all .conf files in the device for "fbdev" (case insensitive) and found these: /usr/src/linux-headers-5.4.0-84-generic/include/config/auto.conf CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100 /usr/src/linux-headers-5.4.0-84-generic/include/config/tristate.conf CONFIG_XEN_FBDEV_FRONTEND=M /usr/src/linux-headers-5.4.0-88-generic/include/config/auto.conf CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100 /usr/src/linux-headers-5.4.0-88-generic/include/config/tristate.conf CONFIG_XEN_FBDEV_FRONTEND=M -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
There is no string "Default Screen Section" in /usr/share/X11/xorg.conf.d directory. The directory contains files: 10-amdgpu.conf 10-quirks.conf 10-radeon.conf 40-libinput.conf 51-synaptics-quirks.conf 70-synaptics.conf 70-wacom.conf nvidia-drm-outputclass-ubuntu.conf The last one is attached. ** Attachment added: "nvidia-drm-outputclass-ubuntu.conf" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+attachment/5532838/+files/nvidia-drm-outputclass-ubuntu.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
I don't know if it is relevant, but even with Xubuntu 18.04 I had to force pulseaudio sample rate to 44100 to be able to successfully play sound via HDMI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947131] [NEW] HDMI display not recognized
Public bug reported: $ xrandr | grep -i hdmi HDMI-1 disconnected (normal left inverted right x axis y axis) This is even when the monitor is connected. IIRC it has never worked with nouveau, but on the other hand nvidia-340 is unsupported nowadays by Nvidia. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Thu Oct 14 11:55:08 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (889 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1947131 Title: HDMI display not recognized Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: $ xrandr | grep -i hdmi HDMI-1 disconnected (normal left inverted right x axis y axis) This is even when the monitor is connected. IIRC it has never worked with nouveau, but on the other hand nvidia-340 is unsupported nowadays by Nvidia. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Thu Oct 14 11:55:08 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (889 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2:
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
** Description changed: - I tried both nouveau and nvidia-340 deivers. It used to work at least by + I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: - $ xrandr + $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm -1920x1200 77.00* + 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 - GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 + GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: - Your system is not currently configured to drive a VGA console - on the primary VGA device. The NVIDIA Linux graphics driver - requires the use of a text-mode VGA console. Use of other console - drivers including, but not limited to, vesafb, may result in - corruption and stability problems, and is not supported. + Your system is not currently configured to drive a VGA console + on the primary VGA device. The NVIDIA Linux graphics driver + requires the use of a text-mode VGA console. Use of other console + drivers including, but not limited to, vesafb, may result in + corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] + NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: - ERROR: Unable to load info from any available system - - - ERROR: Unable to load info from any available system + ERROR: Unable to load info from any available system + + ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded
There exists no /etc/X11/xorg.conf file. I already switched to nouveau using "Software & Updates" rebooted, switched back to nvidia-340 by the same application, and rebooted, but it did not help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 deivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946987] [NEW] HDMI not recognized after upgrading from 18.04 to 20.04.3
Public bug reported: I tried both nouveau and nvidia-340 deivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: HDMI not recognized after upgrading from 18.04 to 20.04.3 Status in xorg package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 deivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX
[Desktop-packages] [Bug 1922562] Re: Resume from suspend to RAM fails
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Worked with nvidia-340 driver which is no more updated. - When I resume, nothing works. Macbook keyboard lights are on, but - otherwise the machine seems dead. Power button reboot needed. + When I resume, nothing works. Macbook keyboard lights are on, but I get + no response from the machine. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1922562 Title: Resume from suspend to RAM fails Status in linux package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: New Bug description: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but I get no response from the machine. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922562] Re: Resume from suspend to RAM fails
Same thing in focal. I also tried 5.13.0-1010-oem kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1922562 Title: Resume from suspend to RAM fails Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: New Bug description: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but otherwise the machine seems dead. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1922562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922562] Re: Resume from suspend to RAM fails
** Also affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags added: focal ** Description changed: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but otherwise the machine seems dead. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 + and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but otherwise the machine seems dead. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 - Uname: Linux 5.4.0-70-generic x86_64 + Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1922562 Title: Resume from suspend to RAM fails Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: New Bug description: Worked with nvidia-340 driver which is no more updated. When I resume, nothing works. Macbook keyboard lights are on, but otherwise the machine seems dead. Power button reboot needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 and xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-70.78~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 and Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 5 16:16:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (1550 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1922562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
I created the custom default.pa. It adds only two commands when compared to default /etc/pulse/default.pa: load-module module-native-protocol-tcp auth-ip-acl=192.168.100.51 set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo The first one I need for network access of pulseaudio from a separate server (https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Network/#authorization) and the second one sets up the profile for the integrated alsa_card.pci-_00_1b.0 to use it only for input. I use an USB device for output. Pulseaudio should be able to handle these. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Attachment removed: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513625/+files/default.pa -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
>From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached?field.comment=From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached ** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513625/+files/default.pa -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
>From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached?field.comment=From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached ** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513624/+files/default.pa -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Description changed: - First pulseaudio fails for some reason. + First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the + volume control in Xfce panel shows mute after I start session, but I can + not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513397/+files/syslog ** Description changed: - This is not always reproduceable. + First pulseaudio fails for some reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] [NEW] Fails to start pulseaudio (No card found by this name or index.)
Public bug reported: This is not always reproduceable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: This is not always reproduceable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934757] Re: Pulseaudio does not recognize integrated audio device
** Description changed: + I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo" + in "~/.config/pulse/default.pa". It caused pulseaudio to fail with this + version. I removed the line and run pulseaudio. + Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) - EDIT: oh, it works again. I'll keep track of this issue. + EDIT: oh, it works again. I'll keep track of this issue. Maybe I should + have started pulseaudio by systemd? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1934757 Title: Pulseaudio does not recognize integrated audio device Status in pulseaudio package in Ubuntu: New Bug description: I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog- stereo" in "~/.config/pulse/default.pa". It caused pulseaudio to fail with this version. I removed the line and run pulseaudio. Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) EDIT: oh, it works again. I'll keep track of this issue. Maybe I should have started pulseaudio by systemd? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934757] Re: Pulseaudio does not recognize integrated audio device
** Description changed: Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) + + EDIT: oh, it works again. I'll keep track of this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1934757 Title: Pulseaudio does not recognize integrated audio device Status in pulseaudio package in Ubuntu: New Bug description: I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog- stereo" in "~/.config/pulse/default.pa". It caused pulseaudio to fail with this version. I removed the line and run pulseaudio. Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) EDIT: oh, it works again. I'll keep track of this issue. Maybe I should have started pulseaudio by systemd? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934757] [NEW] Pulseaudio does not recognize integrated audio device
Public bug reported: Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression-update -- 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/1934757 Title: Pulseaudio does not recognize integrated audio device Status in pulseaudio package in Ubuntu: New Bug description: Unrecognized device: Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 6 12:16:50 2021 InstallationDate: Installed on 2019-12-05 (578 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (360 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1022858] Re: Guest session asks for a password after switching users
You do not need to switch from guest session to do those nowadays: https://help.ubuntu.com/community/CustomizeGuestSession -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775088] Re: Ubuntu Mate guest session locked out when switching from another account
*** This bug is a duplicate of bug 1022858 *** https://bugs.launchpad.net/bugs/1022858 ** This bug has been marked a duplicate of bug 1022858 Guest session asks for a password after switching users -- 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/1775088 Title: Ubuntu Mate guest session locked out when switching from another account Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: ATTN: Ubuntu Mate Developers Description: Ubuntu 18.04 LTS Release: 18.04 lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status In Ubuntu Mate 18.04 LTS LightDM, I created a file in /etc/lightdm/lightdm.conf, with the line: allow-guest=true This allows me to log into a guest session. The issue is when I try to switch between the guest session and a normal session and back. Switching from guest session to the normal user session is fine. LightDM asks for the normal user password. However, when I try to switch from the normal user to back to the guest session I am asked for password as well. This is the problem as the guest session has no known password. The unlock window has a 'Switch User" button along with Cancel, etc. Clicking the "Switch User" button takes me to the standard LightDM screen. There I can select from the normal user and the guest. However, selecting guest here opens a new guest session, and does not take me back to the guest session already open. This looks like an old bug https://bugs.launchpad.net/bugs/1481804 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 4 17:46:33 2018 InstallationDate: Installed on 2018-05-31 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1775088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1022858] Re: Guest session asks for a password after switching users
Does one need to switch from guest session? Maybe it should be disabled. -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions
@Sushenjit did you file a bug report? -- 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/1481804 Title: LightDM's guest-account script should disable screen lock universally for guest sessions Status in lightdm package in Ubuntu: Fix Released Bug description: Is it feasible to include in /usr/sbin/guest-account script some commands to disable screen lock for guest sessions? It should include several commands, depending on Ubuntu flavour. Examples: Ubuntu MATE (uses mate-screensaver) gsettings set org.mate.screensaver lock-enabled false Xubuntu and others (use light-locker) gsettings set apps.light-locker light-locker-enabled false gsettings set apps.light-locker late-locking false gsettings set apps.light-locker lock-on-lid false gsettings set apps.light-locker lock-on-suspend false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855350] Re: Will not logout or shutdown from guest-session
Mika, I can confirm, oddly it helped renaming /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf to /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf.bak. I am using 20.04 now. -- 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/1855350 Title: Will not logout or shutdown from guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-N (N > 1) in daemon.conf
Well, how are you supposed to know, which resample method is actually used? -- 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/1741045 Title: Change the default resample-method to speex-float-N (N > 1) in daemon.conf Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Bug description: I suggest changing the default resample-method to speex-float-10, instead of speex-float-1, which is the current default now, in /etc/pulse/daemon.conf. It would look like this in daemon.conf: resample-method = speex-float-10 I have always done that since at least 12.04 LTS. I was not satisfied with the sound quality in Ubuntu compared to Windows, so I changed the resample-method. In my day-to-day usage, it gives better sound quality without sacrificing CPU power. I have not tried other resample methods. Maybe there are better options I don't know about. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr1696 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 14:37:25 2018 InstallationDate: Installed on 2017-10-02 (92 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1741045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855350] Re: Will not logout or shutdown form guest-session
** Tags added: eoan focal ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1855350 Title: Will not logout or shutdown form guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876197] Re: Xubuntu 20.04 Guest Session Logout Fails
*** This bug is a duplicate of bug 1855350 *** https://bugs.launchpad.net/bugs/1855350 ** This bug has been marked a duplicate of bug 1855350 Will not logout or shutdown form guest-session -- 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/1876197 Title: Xubuntu 20.04 Guest Session Logout Fails Status in lightdm package in Ubuntu: New Bug description: I've edited "/usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf" so that it now has "allow-guest=true". And I'm now able to login to a Guest Session. But when I attempt to logout I get: Receiver error while trying to log out GDBus.Error.org .. Type of message "(yb)", does not match expected type "(b)" This occurs on both of the Xubuntu 20.04 machines I have, and also on a Virtualbox guest. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1876197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782962] Re: Tearing in chromium-browser video playback
Yes, it still happens on Xubuntu 18.04, nvidia driver, sync to vblank set in OpenGL settings in NVIDIA X Server Settings. But I expect it to be better with 19.10 (Xfce 4.14) when using compositor. Chromium Version 80.0.3987.163 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit) -- 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/1782962 Title: Tearing in chromium-browser video playback Status in chromium-browser package in Ubuntu: Incomplete Bug description: Test video: https://youtu.be/22ftfoCSPQI Tested in chromium-browser with setting "Use hardware acceleration when available". Oh, when I use google-chrome, instead, there is no such tearing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 338350/1038352 files, 2274396/4150016 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Jul 22 08:53:00 2018 DistUpgraded: 2018-04-14 11:02:07,544 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-45-generic, x86_64: installed bbswitch, 0.8, 4.15.0-29-generic, x86_64: installed bbswitch, 0.8, 4.4.0-128-generic, x86_64: installed bbswitch, 0.8, 4.4.0-130-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:853b] InstallationDate: Installed on 2014-09-21 (1399 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) MachineType: Dell Inc. OptiPlex 745 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=d012c1bd-7e56-4035-b321-38d20cb14421 ro SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-04-14 (98 days ago) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jul 22 08:40:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHESEN PS2 to USB Converter KEYBOARD, id 8 inputCHESEN PS2 to USB Converter KEYBOARD, id 9 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10 xserver.errors: No devices detected. Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1782962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen
I didn't notice to mention this earlier as I had no windows open on the top monitor at the time of writing, but it is fair to mention that the top monitor's app overview works flawlessly, only the bottom monitor is broken. Attached picture for clarification. ** Attachment added: "Top monitor has the app overview working as expected, bottom is running at tiny scale" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+attachment/5343512/+files/Kuvakaappaus%20-%202020-03-30%2021-49-43.png -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen
I have reported this problem on the gnome-shell gitlab, new bug ID is 2528. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2528 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2528 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2528 -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1869571/+attachment/5342951/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen Status in gnome-shell package in Ubuntu: New Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1869571/+attachment/5342948/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen Status in gnome-shell package in Ubuntu: New Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1869571/+attachment/5342950/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen Status in gnome-shell package in Ubuntu: New Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1869571/+attachment/5342949/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen Status in gnome-shell package in Ubuntu: New Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen
apport information ** Tags added: apport-collected focal third-party-packages ** Description changed: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome- shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu21 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-02-25 (33 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) + Package: gnome-shell 3.36.0-2ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fi_FI.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 + Tags: third-party-packages focal + Uname: Linux 5.4.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1869571/+attachment/5342947/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen Status in gnome-shell package in Ubuntu: New Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on
[Desktop-packages] [Bug 1869571] [NEW] Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen
Public bug reported: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome- shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "First picture showing the problem" https://bugs.launchpad.net/bugs/1869571/+attachment/5342892/+files/Kuvakaappaus%20-%202020-03-29%2014-14-22.png -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen Status in gnome-shell package in Ubuntu: New Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862162] Re: Badly working video mode on the greeter
** Description changed: In the video mode there are moving stripes on the screen and monitor turns off occasionally. (Maybe this is just bad behaving monitor, an old Samsung TV) It became got good after I run xrandr --output HDMI-1 --mode 1920x1080 (and --auto for each other video output) in /usr/local/bin/monitor- config.sh and I put display-setup-script=/usr/local/bin/monitor-config.sh - in lightdm configuration, except that screens partly overlap even if the + in LightDM configuration, except that screens partly overlap even if the other monitor is right of other. Couldn't they be mirroring each other? + Anyway, I can make it work decently as extended desktop if I use --left- + of or --right-of. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 6 13:35:12 2020 InstallationDate: Installed on 2019-12-05 (62 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) LightdmConfig: [Seat:*] display-setup-script=/usr/local/bin/monitor-config.sh SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1862162 Title: Badly working video mode on the greeter Status in lightdm package in Ubuntu: New Bug description: In the video mode there are moving stripes on the screen and monitor turns off occasionally. (Maybe this is just bad behaving monitor, an old Samsung TV) It became got good after I run xrandr --output HDMI-1 --mode 1920x1080 (and --auto for each other video output) in /usr/local/bin/monitor- config.sh and I put display-setup-script=/usr/local/bin/monitor-config.sh in LightDM configuration, except that screens partly overlap even if the other monitor is right of other. Couldn't they be mirroring each other? Anyway, I can make it work decently as extended desktop if I use --left-of or --right-of. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 6 13:35:12 2020 InstallationDate: Installed on 2019-12-05 (62 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) LightdmConfig: [Seat:*] display-setup-script=/usr/local/bin/monitor-config.sh SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1862162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862162] Re: Badly working video mode on the greeter
** Description changed: In the video mode there are moving stripes on the screen and monitor - turns off occasionally. (Maybe this is bad behaving monitor, an old - Samsung TV) It got good after I run + turns off occasionally. (Maybe this is just bad behaving monitor, an old + Samsung TV) It became got good after I run - xrandr --output HDMI-1 --auto + xrandr --output HDMI-1 --mode 1920x1080 - (and similar for each other video output) in /usr/local/bin/monitor- + (and --auto for each other video output) in /usr/local/bin/monitor- config.sh and I put display-setup-script=/usr/local/bin/monitor-config.sh - in lightdm configuration. + in lightdm configuration, except that screens partly overlap even if the + other monitor is right of other. Couldn't they be mirroring each other? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 6 13:35:12 2020 InstallationDate: Installed on 2019-12-05 (62 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) LightdmConfig: - [Seat:*] - display-setup-script=/usr/local/bin/monitor-config.sh + [Seat:*] + display-setup-script=/usr/local/bin/monitor-config.sh SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1862162 Title: Badly working video mode on the greeter Status in lightdm package in Ubuntu: New Bug description: In the video mode there are moving stripes on the screen and monitor turns off occasionally. (Maybe this is just bad behaving monitor, an old Samsung TV) It became got good after I run xrandr --output HDMI-1 --mode 1920x1080 (and --auto for each other video output) in /usr/local/bin/monitor- config.sh and I put display-setup-script=/usr/local/bin/monitor-config.sh in LightDM configuration, except that screens partly overlap even if the other monitor is right of other. Couldn't they be mirroring each other? Anyway, I can make it work decently as extended desktop if I use --left-of or --right-of. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 6 13:35:12 2020 InstallationDate: Installed on 2019-12-05 (62 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) LightdmConfig: [Seat:*] display-setup-script=/usr/local/bin/monitor-config.sh SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1862162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862162] [NEW] Badly working video mode on the greeter
Public bug reported: In the video mode there are moving stripes on the screen and monitor turns off occasionally. (Maybe this is bad behaving monitor, an old Samsung TV) It got good after I run xrandr --output HDMI-1 --auto (and similar for each other video output) in /usr/local/bin/monitor- config.sh and I put display-setup-script=/usr/local/bin/monitor-config.sh in lightdm configuration. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 6 13:35:12 2020 InstallationDate: Installed on 2019-12-05 (62 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) LightdmConfig: [Seat:*] display-setup-script=/usr/local/bin/monitor-config.sh SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1862162 Title: Badly working video mode on the greeter Status in lightdm package in Ubuntu: New Bug description: In the video mode there are moving stripes on the screen and monitor turns off occasionally. (Maybe this is bad behaving monitor, an old Samsung TV) It got good after I run xrandr --output HDMI-1 --auto (and similar for each other video output) in /usr/local/bin/monitor- config.sh and I put display-setup-script=/usr/local/bin/monitor-config.sh in lightdm configuration. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 6 13:35:12 2020 InstallationDate: Installed on 2019-12-05 (62 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) LightdmConfig: [Seat:*] display-setup-script=/usr/local/bin/monitor-config.sh SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1862162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
** Description changed: - The following command tells the files: + The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ + Only pulseaudio is a regular file; other ones are symbolic links, so it + is enough to modify the first one. + gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 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: jarnos 1200 F pulseaudio - /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio - /dev/snd/controlC0: jarnos 1200 F pulseaudio - /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: jarnos 1200 F pulseaudio + /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio + /dev/snd/controlC0: jarnos 1200 F pulseaudio + /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Triaged Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \
[Desktop-packages] [Bug 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/243 -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Triaged Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 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: jarnos 1200 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio /dev/snd/controlC0: jarnos 1200 F pulseaudio /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631715] Re: Password required twice returning from suspend
Stephen, do you use xfce4-screensaver? Is the other lock screen from light-locker. You do not have to use both. Check your autostarts. Purging light-locker changes power manager settings UI, but there is still checkbox for locking. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1631715 Title: Password required twice returning from suspend Status in light-locker package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Clean install - no updates available. Suspend machine and restart. Lock screen requiring password - enter password and return to suspended desktop. Within a few seconds machine locks and password is required once more. Appears to depend on how fast I enter the password the first time. Using the same hardware I've installed nvidia 340.96 and tried to reproduce the issue without success. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: light-locker 1.7.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 9 09:15:38 2016 InstallationDate: Installed on 2016-10-09 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1631715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
Sebastien Bacher, I attach the output of 'LC_ALL=C journalctl -b'. I issued ls command on 11.39.34 and it took about 5 minutes to complete. ** Attachment added: "LC_ALL=C journalctl -b" https://bugs.launchpad.net/libmtp/+bug/1792085/+attachment/5323736/+files/j.log ** Summary changed: - MTP not working/very slow on Bionic + Regression: MTP not working/very slow -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: Regression: MTP not working/very slow Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: Regression: MTP not working/very slow
The previous was on Xubuntu 19.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: Regression: MTP not working/very slow Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
It is odd that this slowness happens with some directories, but not with others. For example it happens on a directory with 7 files; file names consist of letters, '-', digits and '.'. ls command on that directory takes about 5 minutes. But there are other directories (where there are more or less files) with which there is no such delay. Do you have any clue why is this? ** Tags added: eoan ** Tags added: regression -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked
Does it work better with nvidia driver? You could use another locker in 18.10 as workaround. See contents of /usr/bin/xflock4 script for hint. (You have to kill light-locker process and make it not start in "Session and Startup" dialog. -- 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/1830408 Title: [nouveau][XFCE] Do not see login screen after screen is blanked Status in lightdm package in Ubuntu: New Bug description: I've just upgraded to 18.10 from 18.04. Now when power manager (or whoever) puts the screen to blank, I cannot login, because I do not see anything. Befeore the upgrade, mouse move or keypress led to login screen. Now does not. Workaround: When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears. Where is the problem and how to fix it please? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 24 17:59:31 2019 DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1682] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682] InstallationDate: Installed on 2018-09-03 (263 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK Computer Inc. U36SD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1830408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1022858] Re: Guest session asks for a password after switching users
Guess what? Affects Xubuntu 19.10. What is so difficult in not asking password when guest session is concerned? -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857708] [NEW] Uses GNU awk specific option in bash completions, but gawk is not a dependency
Public bug reported: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 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: jarnos 1200 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio /dev/snd/controlC0: jarnos 1200 F pulseaudio /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: New Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list
[Desktop-packages] [Bug 1742912] Re: Please confine guest sessions again
I installed gnome-terminal and got 'unconfined'. So I could view the home directory of another user, but if the directories had no permissions for Other group, I could not view the contents in guest session. So I think a better solution than disabling guest sessions is to make proper default permissions for directories under /home directory. -- 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/1742912 Title: Please confine guest sessions again Status in lightdm package in Ubuntu: Confirmed Bug description: This is a continuation of LP: #1663157 where as a workaround for the guest session not being confined the session got disabled. This bug tracks the fix for proper confinement. Original bug report text: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742912] Re: Please confine guest sessions again
I tested this on Xubuntu 18.04.3, and xfce4-terminal gives the expected output (like xterm as well). I do not see how this should depend on the terminal application used. I guess it is pretty safe to use guest session in Xubuntu. -- 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/1742912 Title: Please confine guest sessions again Status in lightdm package in Ubuntu: Confirmed Bug description: This is a continuation of LP: #1663157 where as a workaround for the guest session not being confined the session got disabled. This bug tracks the fix for proper confinement. Original bug report text: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811402] Re: Can not switch to virtual console (TTY)
** Description changed: - If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). + If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used; update: now I can return even if light-locker is used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6 for text console, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used; update: now I can return even if light-locker is used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6 for text console, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1811402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen
Oh, I found alternative way that works for GRUB menu resolution and console resolution, too, and no need to create /etc/X11/xorg.conf. Edit /etc/default/grub accordingly: GRUB_GFXMODE=1280x1024,auto GRUB_GFXPAYLOAD_LINUX=keep,text You may want to or have to use a different resolution than 1280x1024. Thereafter "sudo update-grub" and reboot. Reference: https://linuxconfig.org/how-to-increase-tty-console-resolution-on-ubuntu-18-04-server https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen
I used sudo nvidia-xconfig to create initial /etc/X11/xorg.conf file like told in #18 Then added Section "Files" ModulePath "/usr/lib/nvidia-340/xorg" ModulePath "/usr/lib/xorg/modules" # ModulePath "/usr/lib/x86_64-linux-gnu/xorg" EndSection in /etc/X11/xorg.conf The last directory is empty, so I guess that is why it is ok to comment it out. Works for the login screen, but other TTY:s have small resolution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen
ls /usr/lib/x86_64-linux-gnu/nvidia* tells "No such file or directory" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate
** Description changed: Does not play sound when playing file that has 48000 Hz sample rate via - sink output:iec958-stereo + sink output:iec958-stereo. This is when using proprietary nvidia-340 + driver; when using nouveau driver, HDMI is not even recognized (Bug + #1844129). Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics adapter) does not have real HDMI audio, but audio is somehow wired from motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000". Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard -- 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/1829364 Title: Will not play sound via HDMI using 48000 Hz sample rate Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound when playing file that has 48000 Hz sample rate via sink output:iec958-stereo. This is when using proprietary nvidia-340 driver; when using nouveau driver, HDMI is not even recognized (Bug #1844129). Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics adapter) does not have real HDMI audio, but audio is somehow wired from motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000". Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate
** Description changed: Does not play sound when playing file that has 48000 Hz sample rate via sink output:iec958-stereo + + Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics + adapter) does not have real HDMI audio, but audio is somehow wired from + motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the + attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps + 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000". Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard -- 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/1829364 Title: Will not play sound via HDMI using 48000 Hz sample rate Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound when playing file that has 48000 Hz sample rate via sink output:iec958-stereo Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics adapter) does not have real HDMI audio, but audio is somehow wired from motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000". Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate
** Summary changed: - Will not play sound via HDMI unless you run pavucontrol first + Will not play sound via HDMI using 48000 Hz sample rate ** Description changed: - Does not play sound via sink output:iec958-stereo unless I start - pavucontrol before running the player such as paplay. Player does not - show any error and takes its time to play, but there is no sound. + Does not play sound when playing file that has 48000 Hz sample rate via + sink output:iec958-stereo Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard -- 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/1829364 Title: Will not play sound via HDMI using 48000 Hz sample rate Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound when playing file that has 48000 Hz sample rate via sink output:iec958-stereo Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
I had this problem, too, but it suddenly started to work in the middle of session. I don't know, if installing package android-tools-adb and pcmanfm had anything to do with it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 218637] Re: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space.
** Description changed: OS: from Hardy to at least Bionic. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. WORKAROUNDS: Run setxkbmap -option "nbsp:none" to make type regular space character. Even better option is to use "classic", "mac" or "nodeadkeys" keyboard variant instead of "". This could be set up in /etc/default/keyboard and maybe in configuration dialog in your desktop environment. Non-breaking space can still be typed (in GTK apps) by u 00a0, if needed. Another option is to use compose key: . In Bash scripts you could also use `printf '\u00a0'` or `printf '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en` instead of `printf`.) Or you could set up a variable `readonly nbsp=$'\u00a0'`. + + Yet another workaround would be to use a font that displays regular + space and non-breaking space differently, but is there one? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/218637 Title: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space. Status in Geany: New Status in gedit: New Status in GNOME Terminal: New Status in nano: New Status in xfce4-terminal: New Status in xkeyboard-config package in Ubuntu: Opinion Bug description: OS: from Hardy to at least Bionic. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. WORKAROUNDS: Run setxkbmap -option "nbsp:none" to make type regular space character. Even better option is to use "classic", "mac" or "nodeadkeys" keyboard variant instead of "". This could be set up in /etc/default/keyboard and maybe in configuration dialog in your desktop environment. Non-breaking space can still be typed (in GTK apps) by u 00a0, if needed. Another option is to use compose key: . In Bash scripts you could also use `printf '\u00a0'` or `printf '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en` instead of `printf`.) Or you could set up a variable `readonly nbsp=$'\u00a0'`. Yet another workaround would be to use a font that displays regular space and non-breaking space differently, but is there one? To manage notifications about this bug go to: https://bugs.launchpad.net/geany/+bug/218637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 218637] Re: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space.
** Description changed: - OS: from Hardy to at least Trusty. + OS: from Hardy to at least Bionic. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. - A workaround in to run + WORKAROUNDS: + + Run setxkbmap -option "nbsp:none" - to make type regular space character. To make this default setting, you could add + to make type regular space character. - XKBOPTIONS="nbsp:none" + Even better option is to use "classic", "mac" or "nodeadkeys" keyboard + variant instead of "". This could be set up in /etc/default/keyboard and + maybe in configuration dialog in your desktop environment. - in '/etc/default/keyboard'. + Non-breaking space can still be typed (in GTK apps) by u + 00a0, if needed. Another option is to use compose key: + . - Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking - space in scripts and in command line. - - Non-breaking space can be typed (in GTK apps) by u 00a0, if needed, but it looks exactly like a regular space. - For me, would be a good shortcut for non-breaking space. + In Bash scripts you could also use `printf '\u00a0'` or `printf + '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en` + instead of `printf`.) Or you could set up a variable `readonly + nbsp=$'\u00a0'`. -- 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/218637 Title: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space. Status in Geany: New Status in gedit: New Status in GNOME Terminal: New Status in nano: New Status in xfce4-terminal: New Status in xorg package in Ubuntu: Invalid Bug description: OS: from Hardy to at least Bionic. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. WORKAROUNDS: Run setxkbmap -option "nbsp:none" to make type regular space character. Even better option is to use "classic", "mac" or "nodeadkeys" keyboard variant instead of "". This could be set up in /etc/default/keyboard and maybe in configuration dialog in your desktop environment. Non-breaking space can still be typed (in GTK apps) by u 00a0, if needed. Another option is to use compose key: . In Bash scripts you could also use `printf '\u00a0'` or `printf '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en` instead of `printf`.) Or you could set up a variable `readonly nbsp=$'\u00a0'`. To manage notifications about this bug go to: https://bugs.launchpad.net/geany/+bug/218637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 218637] Re: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space.
** Summary changed: - Non-breaking space is easy to write accidentally and impossible to distinguish from regular space. + Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space. -- 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/218637 Title: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space. Status in Geany: New Status in gedit: New Status in GNOME Terminal: New Status in nano: New Status in xfce4-terminal: New Status in xorg package in Ubuntu: Invalid Bug description: OS: from Hardy to at least Bionic. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. WORKAROUNDS: Run setxkbmap -option "nbsp:none" to make type regular space character. Even better option is to use "classic", "mac" or "nodeadkeys" keyboard variant instead of "". This could be set up in /etc/default/keyboard and maybe in configuration dialog in your desktop environment. Non-breaking space can still be typed (in GTK apps) by u 00a0, if needed. Another option is to use compose key: . In Bash scripts you could also use `printf '\u00a0'` or `printf '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en` instead of `printf`.) Or you could set up a variable `readonly nbsp=$'\u00a0'`. To manage notifications about this bug go to: https://bugs.launchpad.net/geany/+bug/218637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 218637] Re: Non-breaking space is easy to write accidentally and impossible to distinguish from regular space.
** Description changed: OS: from Hardy to at least Trusty. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. A workaround in to run setxkbmap -option "nbsp:none" - to make type regular space character, - and use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking space in scripts and in command line. + to make type regular space character. To make this default setting, you could add + + XKBOPTIONS="nbsp:none" + + in '/etc/default/keyboard'. + + Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking + space in scripts and in command line. Non-breaking space can be typed (in GTK apps) by u 00a0, if needed, but it looks exactly like a regular space. For me, would be a good shortcut for non-breaking space. -- 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/218637 Title: Non-breaking space is easy to write accidentally and impossible to distinguish from regular space. Status in Geany: New Status in gedit: New Status in GNOME Terminal: New Status in nano: New Status in xfce4-terminal: New Status in xorg package in Ubuntu: Invalid Bug description: OS: from Hardy to at least Trusty. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. A workaround in to run setxkbmap -option "nbsp:none" to make type regular space character. To make this default setting, you could add XKBOPTIONS="nbsp:none" in '/etc/default/keyboard'. Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non- breaking space in scripts and in command line. Non-breaking space can be typed (in GTK apps) by u 00a0, if needed, but it looks exactly like a regular space. For me, would be a good shortcut for non-breaking space. To manage notifications about this bug go to: https://bugs.launchpad.net/geany/+bug/218637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811402] Re: Can not switch to virtual console (TTY)
** Description changed: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). - This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6, and TTY7 gives the X session. + This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6 for text console, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6 for text console, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1811402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811402] Re: Can not switch to virtual console (TTY)
** Description changed: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). - This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. + This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6 for text console, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1811402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829599] [NEW] Does not report error about setting an unsupported resample method
Public bug reported: Command 'pulseaudio --dump-resample-methods' displays available resample methods, but there are more methods described in 'man pulse- daemon.conf'. For example, if I run 'pulseaudio --resample-method=soxr- hq'. Either it should be documented which resample method is used, if an unavailable one is requested, or it should report an error. Anyway, as for 'pulseaudio --resample-method=' tab completion in Bash works well listing available methods. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 18 10:26:58 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1699 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2018-04-14 (398 days ago) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1829599 Title: Does not report error about setting an unsupported resample method Status in pulseaudio package in Ubuntu: New Bug description: Command 'pulseaudio --dump-resample-methods' displays available resample methods, but there are more methods described in 'man pulse- daemon.conf'. For example, if I run 'pulseaudio --resample-method =soxr-hq'. Either it should be documented which resample method is used, if an unavailable one is requested, or it should report an error. Anyway, as for 'pulseaudio --resample-method=' tab completion in Bash works well listing available methods. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 18 10:26:58 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1699 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2018-04-14 (398 days ago) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829364] Re: Will not play sound via HDMI unless you run pavucontrol first
** Description changed: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. + + Workaround: + Set + alternate-sample-rate = 44100 + in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jarnos 1283 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard -- 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/1829364 Title: Will not play sound via HDMI unless you run pavucontrol first Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829364] Re: Will not play sound via HDMI unless you run pavucontrol first
When pavucontrol is not running, it depends on sample rate of playback, whether or not the sound is audible: $ speaker-test -r 48000 not audible $ speaker-test -r 47999 audible -- 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/1829364 Title: Will not play sound via HDMI unless you run pavucontrol first Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829364] [NEW] Will not play sound via HDMI unless you run pavucontrol first
Public bug reported: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1829364 Title: Will not play sound via HDMI unless you run pavucontrol first Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04
I did already # libdir=/usr/lib/x86_64-linux-gnu/python3.6/site-packages # cp /usr/share/lirc/python-pkg/config.py $libdir/lirc # ln -s $libdir/lirc /usr/lib/python3/dist-packages/ # ln -s $libdir/lirc-setup /usr/lib/python3/dist-packages/ as superuser and 'systemctl disable --now lircd-uinput.service' as recommended in #26 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 Status in lirc package in Ubuntu: Invalid Bug description: Lirc 0.10.0-2 is never configured after installation. Manually running "dpkg-reconfigure lirc " also does not do anything. I also noticed that /usr/share/lirc/remotes is empty, which is where I had my config file for Ubuntu 16.04. This was an upgrade install from 16.04. Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04
^fails. If I add the lirc group, then I can run 'sg dialout lirc-setup', and setup, and even make ir receiver react, but testing by irw still does not display anything. Is there some guide for what has changed so that setting up correctly would be easier? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 Status in lirc package in Ubuntu: Invalid Bug description: Lirc 0.10.0-2 is never configured after installation. Manually running "dpkg-reconfigure lirc " also does not do anything. I also noticed that /usr/share/lirc/remotes is empty, which is where I had my config file for Ubuntu 16.04. This was an upgrade install from 16.04. Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04
I tried running lirc-setup on fresh 18.04 install, but it fais as group lirc does not exist. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 Status in lirc package in Ubuntu: Invalid Bug description: Lirc 0.10.0-2 is never configured after installation. Manually running "dpkg-reconfigure lirc " also does not do anything. I also noticed that /usr/share/lirc/remotes is empty, which is where I had my config file for Ubuntu 16.04. This was an upgrade install from 16.04. Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811402] Re: Can not switch to virtual console (TTY)
** Description changed: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. - This bug also breaks light-locker, suspend to RAM, switching user and - maybe something else. + This bug also breaks light-locker, switching user and maybe something + else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1811402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811402] Re: Can not switch to virtual console (TTY)
My 18.04 upgrade was somewhat corrupted. I had to do some manual troubleshooting first to make the upgrade complete. I do not know, if it is still complete, but this bug exists anyway. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. This bug also breaks light-locker, suspend to RAM, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1811402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819194] [NEW] TTY not visible
*** This bug is a duplicate of bug 1811402 *** https://bugs.launchpad.net/bugs/1811402 Public bug reported: NA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-340 340.107-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 8 19:29:33 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (792 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** This bug has been marked a duplicate of bug 1811402 Can not switch to virtual console (TTY) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1819194 Title: TTY not visible Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-340 340.107-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 8 19:29:33 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (792 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nvidia-graphics-drivers-340 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-340/+bug/1819194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811402] Re: Can not switch to virtual console (TTY)
Does not work with 340.107-0ubuntu0.18.04.2 either. HW: Geforce 9400M. I do not know, if related, but with different hardware and 340.107-0ubuntu0.16.04.2 in Xenial I can switch to TTY: On a laptop with a monitor connected to HDMI, the TTY is seen in integrated display only even if the X session is seen on the HDMI monitor. On a (Xenial) PC with a VGA monitor connected TTY is shown in the monitor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. This bug also breaks light-locker, suspend to RAM, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1811402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Fixed in 340.107-0ubuntu0.16.04.2 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 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-304/+bug/1573508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819077] Re: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible point
Works fine with 340.107-0ubuntu0.16.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1819077 Title: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible- pointer-types]) Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Bug description: SRU Request: [Impact] nvidia-340 (from xenial-proposed) breaks compatibility with linux-generic-hwe-16.04. [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update simply re-enables a patch that had been disabled in 340.107-0ubuntu0.16.04.1 _ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.15.0-46-generic Date: Fri Mar 8 01:23:53 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed DuplicateSignature: dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1202 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.107-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Bug #1819077 ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 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-304/+bug/1573508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819077] [NEW] nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build
Public bug reported: nvidia-340 (from xenial-proposed) does not work with kernel from linux- generic-hwe-16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.15.0-46-generic Date: Fri Mar 8 01:23:53 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed DuplicateSignature: dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1202 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.107-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Mar 7 23:28:16 2019 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1819077 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nvidia-340 (from xenial-proposed) does not work with kernel from linux-generic-hwe-16.04. ProblemType: Package DistroRelease: Ubuntu
[Desktop-packages] [Bug 1791409] Re: LIRC not working on Ubuntu 18.04
I upgraded from 16.04 to 18.04 and lirc does not work anymore. systemd shows errors such as "lircd-0.10.0[928]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*" I suppose it is a bug, as lirc should work after upgrade without manual reconfiguration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 Status in lirc package in Ubuntu: Incomplete Bug description: It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is not working correctly. The usual configuration menu to select your remote does not come up after installing the package. Saw some other mentions of this issue as well on the forums: https://ubuntuforums.org/showthread.php?t=2396923 This handy blog post shows a workaround of installing an older version (0.9.0) from xenial to get it to work: https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in- ubuntu-18-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
