[Touch-packages] [Bug 1965094] Re: "Additional Drivers" application crashes on startup
It seems like the apt_pkg.Cache is not fully initialised in SoftwarePropertiesGtk.py when this happens (no "packages" attribute can be found). ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => Confirmed ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965094 Title: "Additional Drivers" application crashes on startup Status in software-properties package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Click on "Show applications" in the dock * Click on "Additional Drivers" Expected: It is possible to see and install additional drivers Actual: Application "software-properties-gtk" crashes Background: I installed 22.04 daily build from scratch on my new Samsung laptop just a few days ago and I have almost no custom settings. Output from screenfetch: ./+o+- [...] y- -yy+ OS: Ubuntu 22.04 jammy ://+//-yyo Kernel: x86_64 Linux 5.15.0-22-generic .++ .:/++/-.+sss/` Uptime: 1d 9h 37m .:++o: //:--:/- Packages: 1810 o:+o+:++.`..```.-/oo+/ Shell: bash 5.1.16 .:+o:+o/. `+sssoo+/Resolution: 3840x1080 .++/+:+oo+o:` /sssooo. DE: GNOME 41.4 /+++//+:`oo+o /::--:. WM: Mutter \+/+o+++`o++o ++. WM Theme: Adwaita .++.o+++oo+:` /dddhhh. GTK Theme: Yaru-dark [GTK2/3] .+.o+oo:. `odd+Icon Theme: Yaru \+.++o+o``-.:ohdh+ Font: Ubuntu 11 `:o+++ `oyo++os: Disk: 21G / 1,2T (2%) .o:`.syhhh/.oo++o` CPU: 11th Gen Intel Core i7-1165G7 @ 8x 4,7GHz [40.0°C] /osyyo++ooo+++/ GPU: Iris Xe Graphics ` +oo+++o\: RAM: 2627MiB / 15725MiB `oo++. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 08:34:57 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-14 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
** Description changed: + [Impact] + + * Linux-restricted-modules for the 390 drivers were disabled + temporarily back in January, however they were not re-enabled when + support for the new kernel was added. + + * Including the 390 release in the ISO causes the 5.13 packages to be + pulled in. + + [Test Plan] + + * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver + can be installed with its linux-restricted-modules. + + [Where problems could occur] + + * The addition of modules for an already existing driver series would not +cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: + https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + _ + Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. ** Description changed: [Impact] - * Linux-restricted-modules for the 390 drivers were disabled + * Linux-restricted-modules for the 390 drivers were disabled temporarily back in January, however they were not re-enabled when support for the new kernel was added. - * Including the 390 release in the ISO causes the 5.13 packages to be + * Including the 390 release in the ISO causes the 5.13 packages to be pulled in. [Test Plan] - * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver + * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricted-modules. [Where problems could occur] - * The addition of modules for an already existing driver series would not -cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: + * The addition of modules for an already existing driver series would not + cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + + * Other kernel releases support the 390 series. _ Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated.
[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942208] Re: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers"
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: New => In Progress ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1942208 Title: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers" Status in OEM Priority Project: Confirmed Status in software-properties package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: [steps to reproduce] 1. Install Stock ubuntu 20.04.3 on XPS 15 9510 2. Installing without using "Third-party packages" 3. After installation completed, launch "Software & Updates" -> "Additional Drivers" -> "Using NVIDIA driver 470" 4. dpkg -l | grep nvidia [Expected result] It should use pre-signed nvidia driver instead of dkms e.g. linux-modules-nvidia-470-5.11.0-27-generic linux-modules-nvidia-470-generic-hwe-20.04 linux-objects-nvidia-470-5.11.0-27-generic linux-signatures-nvidia-5.11.0-27-generic [Actual result] ii nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 amd64 NVIDIA DKMS package --- $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy software-properties-* software-properties-gtk: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages software-properties-kde: Installed: (none) Candidate: (none) Version table: software-properties-qt: Installed: (none) Candidate: 0.98.9.5 Version table: 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe i386 Packages 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/universe i386 Packages software-properties-common: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
I have uploaded linux-base_4.5ubuntu1.3 (bionic) and linux- base_4.5ubuntu3.2 (focal). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: In Progress Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: In Progress Status in debianutils source package in Bionic: New Status in linux-base source package in Bionic: New Status in debianutils source package in Focal: New Status in linux-base source package in Focal: New Status in debianutils source package in Hirsute: New Status in linux-base source package in Hirsute: In Progress Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875339] Re: xorg does not use nvidia gpu on a I+N machine.
Can you attach your /var/log/gpu-manager.log after reproducing the problem, please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875339 Title: xorg does not use nvidia gpu on a I+N machine. Status in OEM Priority Project: Confirmed Status in xorg package in Ubuntu: New Bug description: On a machine with I+N, I install with focal 20.04 image. I didn't turn on auto-login. I checked "install 3rd party driver" during installation. It does install Nvidia driver (440.82+really.440.64-0ubuntu6). On first boot, I double check by run 'prime-select query'. It return nvidia. run nvidia-smi, no program is using NV GPU. --- $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b) Version: 20.0.4 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.4 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.4 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 --- Run lsmod | grep nvidia, I got: --- nvidia_uvm970752 0 nvidia_drm 49152 0 nvidia_modeset 1114112 1 nvidia_drm nvidia 20430848 8 nvidia_uvm,nvidia_modeset drm_kms_helper184320 2 nvidia_drm,i915 ipmi_msghandler 106496 2 ipmi_devintf,nvidia drm 491520 11 drm_kms_helper,nvidia_drm,i915 --- I run $ sudo prime-select intel $ sudo prime-select nvidia $ sudo reboot After reboot, nothing changed. However, previously, on the same machine, I once get it works. (nvidia-smi show some X related process use GPU, glxinfo -B show Nvidia). I remembered I create another admin account, and later on, I found it's fixed. I didn't remember what else exactly make it happened. I re-installed again, and try to do more tests, can't fix it so far. LP: #1875315 have all the log that it first fixed. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:58:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 3541 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8c0e264c-f63c-4d5a-b85f-6faf4008b9e6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to load info from any available system ERROR:
[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I still can't reproduce the problem here. I am attaching the output of lspci -vvv. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5358377/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@Daniel: I tested this on an NVIDIA only system. I am going to test again on a fresh focal installation, to see if it makes any difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I have just updated an Eoan installation to Focal, enabled auto-login, and I can't reproduce the problem. I am using the 440.64 driver, and nvidia-drm.modeset is disabled. I can also see the bootsplash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe
[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@Martin: comment #13 says that autologin works without problems with nouveau. @all: are you able to use auto-login if add the following line to your /etc/X11/Xwrapper.config and reboot? needs_root_rights = yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1854985] Re: pm-utils overrides runtime power management mode for audio devices
** Changed in: pm-utils (Ubuntu) Status: New => Triaged ** Changed in: pm-utils (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: pm-utils (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1854985 Title: pm-utils overrides runtime power management mode for audio devices Status in pm-utils package in Ubuntu: Triaged Bug description: In newer Ubuntu 18.04 HWE kernels, it is possible for GPU HDA controllers to be dynamically runtime-suspended if the HDA's power/control mode is set to "auto". However, pm-utils explicitly sets this to "on" when resuming, which prevents runtime power management of these devices from working as intended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1854985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
I have tested the new packages here, and I can confirm that they solve the problem. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: Triaged Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Bug description: [Impact] * It should be possible to change DRM driver without rebooting. * It should be possible to correctly suspend & resume, whilst preserving driver state. * This bug is for userspace/logind fixes, required to get above working. * Related kernel change is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778658 * https://github.com/torvalds/linux/commit/5775b843a619b3c93f946e2b55a208d9f0f48b59 [Test Case] * Test and verify that on machines with Nvidia discrete graphics, one can change performance/power-saving modes without rebooting. [Regression Potential] * There are changes to the fd handling that are passed to logind. At worst, fd to the NVIDIA driver will still be held, and thus one would continue to not be able to switch graphics modes without rebooting. [Other Info] * original bug report: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
Attaching the debdiff ** Patch added: "systemd_237-3ubuntu10.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777099/+attachment/5154277/+files/systemd_237-3ubuntu10.2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Bug description: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Bug description: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
The packages in bionic-proposed work well here, on my Lenovo Yoga Pro 2 with my Yamaha SRT-1000 soundbar. Sound quality is really good using A2DP, and the audio never goes out of sync when I watch videos, and it doesn't break up when I listen to music. I'm also attaching the output of "apt-cache policy '*pulse*'". ** Attachment added: "installed-packages" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/+attachment/5144156/+files/installed-packages ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. Furthermore, the changes only affect the bluez5-device module, in pulseaudio, and they make the buffer updating logic more conscious of how things can change when the connection drops. This is unlikely to affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
@Łukasz: I have updated the regression potential part with more details. As a side note, I've been running the code for days, using my Yamaha SRT-1000 (a bluetooth soundbar) with my laptop, and I have yet to see the audio go out of sync, or crackle (which were quite frequent before the changes). This makes bluetooth audio pretty much on par with MacOS. ** Description changed: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. + + Furthermore, the changes only affect the bluez5-device module, in + pulseaudio, and they make the buffer updating logic more conscious of + how things can change when the connection drops. This is unlikely to + affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. Furthermore, the changes only affect the bluez5-device module, in pulseaudio, and they make the buffer updating logic more conscious of how things can change when the connection drops. This is unlikely to affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Please approve pulseaudio 11.1-1ubuntu7.1 in bionic-proposed. ** Description changed: - As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped - working properly. It was working fine in Jaunty. + SRU Request: + + [Impact] + When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. + + [Test Case] + 1) Enable the -proposed repository, and install the new pulseaudio + + 2) Restart your computer, connect it to a bluetooth device (e.g. a + headset or a speaker), play one or more videos either locally or online, + and see if you can still reproduce the problem. + + [Regression Potential] + Low, as the changes are upstream, and, if anything, it should also fix a memory leak. + + + As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: In Progress Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list:
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
** Changed in: pulseaudio (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: In Progress Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: Triaged => In Progress ** Changed in: pulseaudio (Ubuntu Bionic) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: Triaged Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted
** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: software-properties (Ubuntu) ** No longer affects: software-properties (Ubuntu Bionic) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 source package in Bionic: New Status in nvidia-graphics-drivers-390 source package in Bionic: Triaged Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted
@Doug: I'm working on the meta-package part for LP: #175 , this is a separate bug report, only about the blacklist file. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in software-properties package in Ubuntu: Confirmed Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Triaged ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
The code in my MP was approved. Please merge it, and let's proceed with the SRU. ** Description changed: - When you are in the initial install state, you can easily switch from - the Nouvea drivers to the Nvidia drivers by choosing the option in - "Software and Updates -> Additional Drivers". However, when you attempt - to switch back (by selecting the nouveau option and clicking Apply), and - subsequently reboot, your system will still come up using the Nvidia - drivers, and you will WTF. + SRU Request: + + [Impact] + Currently, the Additional Drivers tool uninstalls only the driver package that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that package is only a meta-package. Removing the meta-package will not uninstall the driver. + + We should make sure to uninstall all its nvidia related dependencies, + not only the meta-package. + + [Test Case] + 1) Open the "Software & Updates" app, and select the "Additional Drivers" tab + + 2) Uninstall the NVIDIA 390 driver + + 3) Check that, for example, the nvidia-dkms-390 package was uninstalled: + + apt-cache policy nvidia-dkms-390 + + The package will be reported as installed, because the current code + didn't remove it. + + [Regression Potential] + Relatively low, as the change in behaviour only affects the nvidia driver, and it only causes the Additional Drivers tool to remove dependencies of the meta-package that have the "nvidia" string in their name. + + __ + When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in software-properties package in Ubuntu: In Progress Bug description: SRU Request: [Impact] Currently, the Additional Drivers tool uninstalls only the driver package that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that package is only a meta-package. Removing the meta-package will not uninstall the driver. We should make sure to uninstall all its nvidia related dependencies, not only the meta-package. [Test Case] 1) Open the "Software & Updates" app, and select the "Additional Drivers" tab 2) Uninstall the NVIDIA 390 driver 3) Check that, for example, the nvidia-dkms-390 package was uninstalled: apt-cache policy nvidia-dkms-390 The package will be reported as installed, because the current code didn't remove it. [Regression Potential] Relatively low, as the change in behaviour only affects the nvidia driver, and it only causes the Additional Drivers tool to remove dependencies of the meta-package that have the "nvidia" string in their name. __ When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning
[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
The fix for this bug is in the bazaar branch listed above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in software-properties package in Ubuntu: In Progress Bug description: When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/175/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
** Changed in: software-properties (Ubuntu) Status: Triaged => In Progress ** No longer affects: nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in software-properties package in Ubuntu: In Progress Bug description: When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/175/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: New => Triaged ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: software-properties (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Triaged Bug description: When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/175/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762200] Re: [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** No longer affects: nvidia-graphics-drivers-340 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-390 (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1762200 Title: [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: System: Ubuntu 18.04 (08.04.2018 updated) PC: Dell inspiron n5110 laptop CPU: intel i7 2630QM GPU: nvidia gt 525m *** I installed latest nvidia driver, but driver detects 2 screen. bad thing is gdm, i can't see gdm greeter only purple background. greeter in primary(unknown) screen Please check screenshot *** U1804PC:~$ lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 525M] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 05) 09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34) 0b:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02) U1804PC:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1762200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
All the required components should be in Bionic now. I am closing this bug report. Feel free to file a new bug report, if you experience any further problems with the driver. P.S. disabling the discrete GPU (on systems with hybrid graphics) does not work yet, but it will soon. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752123] Re: Force 8bit RGB config
** Changed in: mutter (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752123 Title: Force 8bit RGB config Status in cogl package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Triaged Bug description: New mesa supports 10bit RGB configs, and this causes issues with cogl/mutter which get a random EGLConfig that breaks some autopkgtests. To fix this this merge request is needed for mutter https://gitlab.gnome.org/GNOME/mutter/merge_requests/36 and a similar one for cogl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1752123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
It seems like the kernel and the nvidia driver weren't built using the same compiler. Please, either ssh into your machine, or press CTRL+ALT+F2 and do the following: 1) Make sure security updates are enabled, and update your system ("apt- cache policy gcc-5" should report 5.4.0-6ubuntu1~16.04.9 on Xenial) 2) Make sure no driver from NVIDIA's website is installed. If it is, please uninstall it first. 3) When gcc-5 is updated, re-install the nvidia package from the archive: sudo apt-get install --reinstall nvidia-384 (or nvidia-340) 4) Restart your computer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
I am attaching the output of the following command: lsinitramfs /boot/initrd.img-`uname -r` | grep drm ** Attachment added: "initramfs_drm" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+attachment/4610107/+files/initramfs_drm ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561643] [NEW] initramfs-tools ignores the FRAMEBUFFER option
Public bug reported: initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536438] Re: Need add uaccess tag for /dev/dri/renderD*
** Description changed: + [Impact] + The lts-wily backported kernel introduces the amdgpu driver. Graphics cards that use this driver need the render node (/dev/dri/renderD*) to be accessible to users. + + [Test Case] + Install the lts-wily kernel, and check whether /dev/dri/renderD* is accessible or not. + + [Regression Potential] + Low, as the change is already upstream and included in wily. + + 3.16/3.19 Linux kernel add render node support which will create /dev/dri/renderD*. uaccess tag must be added to the /lib/udev/rules.d/70-uaccess.rules to make it access-able to login user just like /dev/dri/card*. It has been done on Ubuntu 15.04, but 14.04.3 has not. 14.04.3 70-uaccess.rules # DRI video devices SUBSYSTEM=="drm", KERNEL=="card*", TAG+="uaccess" 15.04 70-uaccess.rules # DRI video devices SUBSYSTEM=="drm", KERNEL=="card*|renderD*", TAG+="uaccess" Please fix this for AMD GPU driver will use the /dev/dri/renderD*. Fixed upstream in https://github.com/systemd/systemd/commit/735e5d - ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu20.14 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 21 10:06:24 2016 InstallationDate: Installed on 2015-09-16 (126 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Need add uaccess tag for /dev/dri/renderD* + SRU: Need add uaccess tag for /dev/dri/renderD* -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1536438 Title: SRU: Need add uaccess tag for /dev/dri/renderD* Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Committed Bug description: [Impact] The lts-wily backported kernel introduces the amdgpu driver. Graphics cards that use this driver need the render node (/dev/dri/renderD*) to be accessible to users. [Test Case] Install the lts-wily kernel, and check whether /dev/dri/renderD* is accessible or not. [Regression Potential] Low, as the change is already upstream and included in wily. 3.16/3.19 Linux kernel add render node support which will create /dev/dri/renderD*. uaccess tag must be added to the /lib/udev/rules.d/70-uaccess.rules to make it access-able to login user just like /dev/dri/card*. It has been done on Ubuntu 15.04, but 14.04.3 has not. 14.04.3 70-uaccess.rules # DRI video devices SUBSYSTEM=="drm", KERNEL=="card*", TAG+="uaccess" 15.04 70-uaccess.rules # DRI video devices SUBSYSTEM=="drm", KERNEL=="card*|renderD*", TAG+="uaccess" Please fix this for AMD GPU driver will use the /dev/dri/renderD*. Fixed upstream in https://github.com/systemd/systemd/commit/735e5d ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu20.14 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 21 10:06:24 2016 InstallationDate: Installed on 2015-09-16 (126 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1536438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536438] Re: Need add uaccess tag for /dev/dri/renderD*
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1536438 Title: Need add uaccess tag for /dev/dri/renderD* Status in systemd package in Ubuntu: Triaged Bug description: 3.16/3.19 Linux kernel add render node support which will create /dev/dri/renderD*. uaccess tag must be added to the /lib/udev/rules.d/70-uaccess.rules to make it access-able to login user just like /dev/dri/card*. It has been done on Ubuntu 15.04, but 14.04.3 has not. 14.04.3 70-uaccess.rules # DRI video devices SUBSYSTEM=="drm", KERNEL=="card*", TAG+="uaccess" 15.04 70-uaccess.rules # DRI video devices SUBSYSTEM=="drm", KERNEL=="card*|renderD*", TAG+="uaccess" Please fix this for AMD GPU driver will use the /dev/dri/renderD*. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu20.14 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 21 10:06:24 2016 InstallationDate: Installed on 2015-09-16 (126 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1536438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file
This is not really a bug in ubuntu-drivers-common. Those are just debugging messages (no actual error there). I can probably get rid of them but still that doesn't explain why a second xserver was started. Maybe another user logged into the system from lightdm? Or maybe lightdm is acting funny for some reason. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1452610 Title: /etc/modprobe.d is not a file Status in lightdm package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: /var/log/upstart# cat lightdm.log /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Above looks weird... modprobe.d is a directory & why update- alternatives are called?! This is lightdm 1.10.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1452610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic
yes, the problem with fglrx is well known and I'm working on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Trusty: Fix Committed Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev Reading package lists... Done Building dependency tree 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: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
** Also affects: alsa-plugins (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: alsa-plugins (Ubuntu Trusty) Status: New = Invalid ** Changed in: ubuntu-drivers-common (Ubuntu Trusty) Status: New = Triaged ** Changed in: ubuntu-drivers-common (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. Status in “alsa-plugins” package in Ubuntu: Invalid Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “alsa-plugins” source package in Trusty: Invalid Status in “ubuntu-drivers-common” source package in Trusty: Triaged Bug description: On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system) pulseaudio is running twice. This makes attaching/deattaching of usb-headset and other stuff impossible because the two instances fight ove rthe events. Tow reproduce just boot up the current image and do a ps -ef | grep pulseaudio ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgh2336 F pulseaudio sgh2796 F pulseaudio /dev/snd/controlC0: sgh2336 F pulseaudio sgh2796 F pulseaudio CurrentDesktop: KDE Date: Sun Mar 23 22:36:50 2014 InstallationDate: Installed on 2013-12-24 (89 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267442] Re: Install nvidia-331 on X/K/Lubuntu results in unbootable machine
I tried to reproduce the problem using a Xubuntu 14.04 image and everything worked as expected: http://people.canonical.com/~amilone/xubuntu-output.log The main problem is that systems older than 14.04 might still have a /etc/lightdm/lightdm.conf that was altered by older nvidia-prime releases. I thought lightdm would take care of the issue by removing such configuration file but I was wrong. This is the preinst script from lightdm in trusty: if dpkg-maintscript-helper supports mv_conffile; then dpkg-maintscript-helper mv_conffile \ /etc/lightdm.conf \ /etc/lightdm/lightdm.conf \ 0.3.7-0ubuntu2 -- $@ fi I believe 0.3.7-0ubuntu2 should be updated to a more recent release such as 1.10.1-0ubuntu1~. This is something that we should deal with in the lightdm package though. I don't think it would be right for nvidia-prime to remove lightdm's configuration files. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Status: New = Triaged ** Changed in: lightdm (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1267442 Title: Install nvidia-331 on X/K/Lubuntu results in unbootable machine Status in “lightdm” package in Ubuntu: Triaged Status in “nvidia-prime” package in Ubuntu: Incomplete Bug description: Install of nvidia-331 completes, assuming it edits lightdm.conf left with this - not any use if you're not using Ubuntu greeter-session=unity-greeter user-session=ubuntu display-setup-script=/sbin/prime-offload display-stopped-script=/sbin/prime-switch have to comment out the exisiting greeter and user session lines and replace with display-setup-script=/sbin/prime-offload display-stopped-script=/sbin/prime-switch user-session=xubuntu greeter-session=lightdm-gtk-greeter to get a satisfactory boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1267442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop
On 08-09-14 12:23:24, Laércio de Sousa wrote: I've crated a topic in NVIDIA DevZone Forums about shipping this udev rule. Someone have pointed out about the possibility of no kernel devices (like /dev/dri/card*) being available, since they are not created by NVIDIA drivers, but by other kernel modules. So I'm proposing this alternative udev rule as a fallback for the case we cannot guarantee /dev/dri/card* is available in the system: SUBSYSTEM==pci, ATTRS{vendor}==0x10de, DRIVER==nvidia, TAG+=seat, TAG+=master-of-seat Ok, it makes sense, I'll test and update the rules accordingly for fglrx and nvidia. Thanks for the update. -- Alberto Milone -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1365336 Title: Lightdm update=No desktop Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Status in “xserver-xorg-video-vesa” package in Ubuntu: Confirmed Status in “xserver-xorg-video-vmware” package in Ubuntu: Confirmed Bug description: Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me with no desktop on normal boot. Machine boots directly to tty1. Logged in at tty1 and then startx leads to a desktop that requires password to start properly and with themes unapplied. Password required to reboot machine. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 4 08:20:14 2014 InstallationDate: Installed on 2014-07-17 (48 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1365336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop
** Also affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Also affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Package changed: nvidia-graphics-drivers (Ubuntu) = nvidia-graphics- drivers-331-updates (Ubuntu) ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: Confirmed = Triaged ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1365336 Title: Lightdm update=No desktop Status in “fglrx-installer” package in Ubuntu: Triaged Status in “fglrx-installer-updates” package in Ubuntu: Triaged Status in “lightdm” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Triaged Bug description: Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me with no desktop on normal boot. Machine boots directly to tty1. Logged in at tty1 and then startx leads to a desktop that requires password to start properly and with themes unapplied. Password required to reboot machine. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 4 08:20:14 2014 InstallationDate: Installed on 2014-07-17 (48 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1365336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop
** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer-updates (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Also affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer (Ubuntu) Status: New = Triaged ** Changed in: fglrx-installer-updates (Ubuntu) Status: New = Triaged ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New = Triaged ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: New = Triaged ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided = Critical ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided = Critical ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided = Critical ** Changed in: fglrx-installer (Ubuntu) Importance: Undecided = Critical ** Changed in: fglrx-installer-updates (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1365336 Title: Lightdm update=No desktop Status in “fglrx-installer” package in Ubuntu: Triaged Status in “fglrx-installer-updates” package in Ubuntu: Triaged Status in “lightdm” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Triaged Bug description: Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me with no desktop on normal boot. Machine boots directly to tty1. Logged in at tty1 and then startx leads to a desktop that requires password to start properly and with themes unapplied. Password required to reboot machine. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 4 08:20:14 2014 InstallationDate: Installed on 2014-07-17 (48 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1365336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop
** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Triaged = In Progress ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: Triaged = In Progress ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: Triaged = In Progress ** Changed in: fglrx-installer (Ubuntu) Status: Triaged = In Progress ** Changed in: fglrx-installer-updates (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1365336 Title: Lightdm update=No desktop Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Bug description: Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me with no desktop on normal boot. Machine boots directly to tty1. Logged in at tty1 and then startx leads to a desktop that requires password to start properly and with themes unapplied. Password required to reboot machine. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 4 08:20:14 2014 InstallationDate: Installed on 2014-07-17 (48 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1365336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop
Thank you for reporting the problem and for debugging it, and thank you, Laércio, for providing a solution. I have just uploaded a fix for the relevant nvidia drivers. An update for fglrx will follow soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1365336 Title: Lightdm update=No desktop Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Bug description: Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me with no desktop on normal boot. Machine boots directly to tty1. Logged in at tty1 and then startx leads to a desktop that requires password to start properly and with themes unapplied. Password required to reboot machine. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 4 08:20:14 2014 InstallationDate: Installed on 2014-07-17 (48 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1365336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp