[Touch-packages] [Bug 1858035] Re: Xorg freeze (Ubuntu 19.10 stuck on splash screen)
Hey, quick question. I'm running into similar problems, but on grub right before the splash screen. After removing your drive, did you happen to have anything else like a charging cable or wired/wireless mouse in your ports? -- 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/1858035 Title: Xorg freeze (Ubuntu 19.10 stuck on splash screen) Status in xorg package in Ubuntu: New Bug description: Yesterday I had just installed Ubuntu 19.10 and after my third or fourth reboot it would not start, it just got stuck on the splash screen. I didn't know what to do, but I still had the USB from which I had installed Ubuntu, so I plugged it in and booted up from the USB, and then I pressed the shutdown button, and before it shut down Ubuntu asked me to remove the installation media and press OK, I did, the laptop shut down, and now I booted up my laptop as usual, not from the USB, and this time it did not get stuck on the splash screen. So I left it at that, but just now, I booted up my laptop,and again it got stuck again, and so again I did the boot up from the USB, shut down, remove USB, and reboot as usual from the laptops HDD. Now it works again. This problem seems to happen on a random basis. I hope this helps to solve this problem. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 1 18:58:18 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0410] InstallationDate: Installed on 2019-12-30 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude E4310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=6e8b1021-3bce-4fb7-a48b-eb93e408c4d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0XG3JF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0XG3JF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/xorg/+bug/1858035/+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 1858181] [NEW] Xorg freeze with bluetooth mouse plugin, 19.10
Public bug reported: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b: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 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze ubuntu -- 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/1858181
[Touch-packages] [Bug 1858168] [NEW] Ubuntu 19.10 after updating the "Other Software" tab in "Software & Updates" the "cache refresh" hangs
Public bug reported:
Running the command from a terminal window The following messages are
logged when the hang occurs:
simon@Ubuntu-2600K:~$ sudo software-properties-gtk
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.Error: pk-client-error-quark: W: Skipping acquire of
configured file 'main/binary-i386/Packages' as repository
'http://packages.microsoft.com/repos/vscode stable InRelease' doesn't support
architecture 'i386'
E: The repository
'http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu eoan
Release' does not have a Release file.
W: Updating from such a repository can't be done securely, and is therefore
disabled by default.
W: See apt-secure(8) manpage for repository creation and user configuration
details.
(319)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in
new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in
new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in
new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
I note similar issues reported for other functions however, these seem
to have been resolved.
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
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/1858168
Title:
Ubuntu 19.10 after updating the "Other Software" tab in "Software &
Updates" the "cache refresh" hangs
Status in software-properties package in Ubuntu:
New
Bug description:
Running the command from a terminal window The following messages are
logged when the hang occurs:
simon@Ubuntu-2600K:~$ sudo software-properties-gtk
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.Error: pk-client-error-quark: W: Skipping acquire of
configured file 'main/binary-i386/Packages' as repository
'http://packages.microsoft.com/repos/vscode stable InRelease' doesn't support
architecture 'i386'
E: The repository
'http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu eoan
Release' does not have a Release file.
W: Updating from such a repository can't be done securely, and is therefore
disabled by default.
W: See apt-secure(8) manpage for repository creation and user configuration
details.
(319)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
I note similar issues reported for other functions however, these seem
to have been resolved.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1858168/+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 1858164] [NEW] libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates
Public bug reported: 1) The release of Ubuntu you are using: $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 2) The version of the package you are using: $ dpkg -l | grep libpulse ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries ii libpulse0:i3861:11.1-1ubuntu7.5 i386 PulseAudio client libraries ii libpulsedsp:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio OSS pre-load library 3) What you expected to happen "sudo apt install libpulse-dev" should installed libpulse-dev. 4) What happened instead $ sudo apt install libpulse-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. libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed E: Unable to correct problems, you have held broken packages. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1858164 Title: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates Status in pulseaudio package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using: $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 2) The version of the package you are using: $ dpkg -l | grep libpulse ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries ii libpulse0:i3861:11.1-1ubuntu7.5 i386 PulseAudio client libraries ii libpulsedsp:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio OSS pre-load library 3) What you expected to happen "sudo apt install libpulse-dev" should installed libpulse-dev. 4) What happened instead $ sudo apt install libpulse-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. libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858164/+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 1858152] [NEW] fstrim.service no longer trims /home partition
Public bug reported: When I was running disco, fstrim.service would trim all of my partitions: Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) trimmed on /dev/mapper/ubuntu--vg-home Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) trimmed on /dev/sda5 Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded. Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. After upgrading to eoan, my /home partition is no longer trimmed: Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) trimmed on /dev/sda5 Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded. Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. Checking the unit file (/lib/systemd/system/fstrim.service), I noticed there is a "ProtectHome=yes" option. Removing this option caused my /home partition to be trimmed once again. I believe the "ProtectSystem=strict" option may also cause partitions in non-standard partition schemes to be skipped by fstrim.service (although I have not tested this). ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition Status in util-linux package in Ubuntu: New Bug description: When I was running disco, fstrim.service would trim all of my partitions: Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) trimmed on /dev/mapper/ubuntu--vg-home Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) trimmed on /dev/sda5 Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded. Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. After upgrading to eoan, my /home partition is no longer trimmed: Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) trimmed on /dev/sda5 Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded. Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. Checking the unit file (/lib/systemd/system/fstrim.service), I noticed there is a "ProtectHome=yes" option. Removing this option caused my /home partition to be trimmed once again. I believe the "ProtectSystem=strict" option may also cause partitions in non-standard partition schemes to be skipped by fstrim.service (although I have not tested this). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858152/+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 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libpciaccess (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: Confirmed Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: Confirmed Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83] (EE) 9: /usr/lib/xorg/Xorg
[Touch-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pciutils (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: Confirmed Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: Confirmed Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83] (EE) 9: /usr/lib/xorg/Xorg
[Touch-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
I'm hitting this issue on some new server hardware when trying to use lspci from pciutils with a 16.04 installation. I'm wondering of there has there been any progress on getting this fix released for Xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: Confirmed Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: Confirmed Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13)
[Touch-packages] [Bug 1858141] [NEW] "Advanced" tab is missing from Print dialog in Qt5 applications
Public bug reported: Please backport Qt patch 213391 to qtbase-opensource-src in Bionic: https://codereview.qt-project.org/#/c/213391/ [Impact] On Kubuntu 18.04 (bionic), any applications using Qt5 are unable to fully configure printers from within the "Print..." dialog because the "Advanced" tab is no longer present. Settings shown here will differ by printer, but this includes important settings such as paper type (plain, glossy, photo, etc.), print resolution, and ink usage strategies. Gwenview and Okular are notable affected applications. GTK applications are unaffected and do show the advanced options provided by the printer driver. As a workaround for Qt5 applications, the printer *default* advanced settings can be successfully accessed and changed from within the "Printers" section of Plasma's "System Settings", but this is cumbersome, unintuitive, and is not the intended way of interacting with these settings on a per-print-job basis. [Additional Information] This was identified as a bug in Qt5 upstream: https://bugreports.qt.io/browse/QTBUG-54464 The bug was fixed upstream in Qt 5.11, but Bionic is stable on Qt 5.9. I'd like to request that this patch be backported to Bionic, please. [Regression Potential] OpenSUSE has already backported this patch to their Qt 5.9 stable branch, so there is precedent for this patch being low risk: https://build.opensuse.org/package/view_file/KDE:Qt:5.9/libqt5-qtbase/0010-Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=1 Software Versions: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ apt-cache policy libqt5printsupport5 libqt5printsupport5: Installed: 5.9.5+dfsg-0ubuntu2.4 Candidate: 5.9.5+dfsg-0ubuntu2.4 Version table: *** 5.9.5+dfsg-0ubuntu2.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.9.5+dfsg-0ubuntu2.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 5.9.5+dfsg-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1858141 Title: "Advanced" tab is missing from Print dialog in Qt5 applications Status in qtbase-opensource-src package in Ubuntu: New Bug description: Please backport Qt patch 213391 to qtbase-opensource-src in Bionic: https://codereview.qt-project.org/#/c/213391/ [Impact] On Kubuntu 18.04 (bionic), any applications using Qt5 are unable to fully configure printers from within the "Print..." dialog because the "Advanced" tab is no longer present. Settings shown here will differ by printer, but this includes important settings such as paper type (plain, glossy, photo, etc.), print resolution, and ink usage strategies. Gwenview and Okular are notable affected applications. GTK applications are unaffected and do show the advanced options provided by the printer driver. As a workaround for Qt5 applications, the printer *default* advanced settings can be successfully accessed and changed from within the "Printers" section of Plasma's "System Settings", but this is cumbersome, unintuitive, and is not the intended way of interacting with these settings on a per-print-job basis. [Additional Information] This was identified as a bug in Qt5 upstream: https://bugreports.qt.io/browse/QTBUG-54464 The bug was fixed upstream in Qt 5.11, but Bionic is stable on Qt 5.9. I'd like to request that this patch be backported to Bionic, please. [Regression Potential] OpenSUSE has already backported this patch to their Qt 5.9 stable branch, so there is precedent for this patch being low risk: https://build.opensuse.org/package/view_file/KDE:Qt:5.9/libqt5-qtbase/0010-Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=1 Software Versions: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ apt-cache policy libqt5printsupport5 libqt5printsupport5: Installed: 5.9.5+dfsg-0ubuntu2.4 Candidate: 5.9.5+dfsg-0ubuntu2.4 Version table: *** 5.9.5+dfsg-0ubuntu2.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.9.5+dfsg-0ubuntu2.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 5.9.5+dfsg-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to:
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
When will the fix be released? -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
Applying the patch fixed my problem with my Sony WH-H900N headphones. Probably a different bug but if I open Sound Settings -> Input and change the input from "Internal Microphone Built-in Audio" to "Headset WH-H900N (h.ear)" the quality degrades and the Output profile changes to "Headset Head Unit (HSP/HFP)". If I change the Output profile back to "High Fidelity Playback (A2DP Sink)" I get high quality audio again but the Input changes back to "Internal Microphone Built-in Audio". Or is it that you can't use the headset microphone and get high quality audio at the same time? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+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 1858111] [NEW] package linux-firmware 1.183.3 failed to install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script post-installation retornou erro do status de
Public bug reported: ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.3 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 2 11:17:34 2020 Dependencies: ErrorMessage: o subprocesso instalado, do pacote linux-firmware, o script post-installation retornou erro do status de saída 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package linux-firmware 1.183.3 failed to install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- 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/1858111 Title: package linux-firmware 1.183.3 failed to install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script post- installation retornou erro do status de saída 1 Status in initramfs-tools package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.3 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 2 11:17:34 2020 Dependencies: ErrorMessage: o subprocesso instalado, do pacote linux-firmware, o script post-installation retornou erro do status de saída 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package linux-firmware 1.183.3 failed to install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script post-installation retornou erro do status de saída 1 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/1858111/+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 1857914] Re: resize2fs destroy the content of the partition
So if the same procedure (with exactly the same files) reproduces reliably when using a partition and gpart --- and it does not reproduce at all, even with multiple attmepts, without gpart, then it is clearly a gpart bug. ** Package changed: e2fsprogs (Ubuntu) => gpart (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1857914 Title: resize2fs destroy the content of the partition Status in gpart package in Ubuntu: New Bug description: Hello The used version of ubuntu is 19.10 So the used version of ubuntu is GParted 0.32.0 and the used of resize2fs is 1.45.3 (14-Jul-2019) I wanted to shrink by 20 GB the size of an old partition created with ubuntu 18.04 and stored on an external hard drive connected by USB3. The process says it works perfectly well see attachment file But the partition can no longer be mounted. The message is: mount: /mnt/sdb2 : wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error. if I do the stupidity to launch the fsk command to repair, I find all the files and directory in the special directory called Lost + found Being able to remake the original content, I have seen four times that it gives this unpleasant result. It also allows me to change the scenario. - If I use an internal disk partition instead of the external disk, you're fine. - If I use version 18.04, everything is fine even if I use the external disk - If I make a new partition on the external disk in version 19.10, I can shrink also without any problem. So I think there is a software regression for a very specific context. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914/+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 1858106] Re: package nvidia-dkms-390 390.129-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- 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/1858106 Title: package nvidia-dkms-390 390.129-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't know what happened just installed the system and on the first system boot he reported me this error ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Thu Jan 2 10:27:11 2020 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package nvidia-dkms-390 390.129-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 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/1858106/+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 1858106] [NEW] package nvidia-dkms-390 390.129-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit statu
Public bug reported: I don't know what happened just installed the system and on the first system boot he reported me this error ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Thu Jan 2 10:27:11 2020 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package nvidia-dkms-390 390.129-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- 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/1858106 Title: package nvidia-dkms-390 390.129-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't know what happened just installed the system and on the first system boot he reported me this error ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Thu Jan 2 10:27:11 2020 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package nvidia-dkms-390 390.129-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 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/1858106/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
I can confirm that applying the patch from #30 in 18.04 does seem to fix the problem when using WH-1000XM3. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+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 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
Julian, feel free to let me know if you need any help, for example with testing etc. It would be great if this could be fixed before Ubuntu 20.04 (or at least 20.10) is released. :-) Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+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 1857914] Re: resize2fs destroy the content of the partition
Hello I cannot reproduce the incident with this method export LC_ALL=POSIX sudo mke2fs -t ext4 /USB1910bis/fs.img 30G mke2fs 1.45.3 (14-Jul-2019) Creating regular file /mnt/USB1910bis/fs.img Creating filesystem with 7864320 4k blocks and 1966080 inodes Filesystem UUID: 2cf9eafb-628c-45d3-b452-6bdf785ae24d Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done sudo mount -v -o loop /USB1910bis/fs.img /mnt mount: /dev/loop12 mounted on /mnt. It is necessary to copy files because when the partition does not contain any, it can shrink without difficulty sudo ls -ls /mnt total 20 4 drwx-- 20 root root 4096 Jan 2 13:20 P2 16 drwx-- 2 root root 16384 Jan 2 12:56 lost+found sudo umount -v /mnt umount: /mnt unmounted sudo e2fsck -fy /USB1910bis/fs.img e2fsck 1.45.3 (14-Jul-2019) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /USB1910bis/fs.img: 3929/1966080 files (0.4% non-contiguous), 3978206/7864320 blocks sudo resize2fs /USB1910bis/fs.img 20G resize2fs 1.45.3 (14-Jul-2019) Resizing the filesystem on /USB1910bis/fs.img to 5242880 (4k) blocks. The filesystem on /USB1910bis/fs.img is now 5242880 (4k) blocks long. sudo e2fsck -fy /USB1910bis/fs.img e2fsck 1.45.3 (14-Jul-2019) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /USB1910bis/fs.img: 3929/1310720 files (0.4% non-contiguous), 3937075/5242880 blocks sudo mount -v -o loop /USB1910bis/fs.img /mnt mount: /dev/loop12 mounted on /mnt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1857914 Title: resize2fs destroy the content of the partition Status in e2fsprogs package in Ubuntu: New Bug description: Hello The used version of ubuntu is 19.10 So the used version of ubuntu is GParted 0.32.0 and the used of resize2fs is 1.45.3 (14-Jul-2019) I wanted to shrink by 20 GB the size of an old partition created with ubuntu 18.04 and stored on an external hard drive connected by USB3. The process says it works perfectly well see attachment file But the partition can no longer be mounted. The message is: mount: /mnt/sdb2 : wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error. if I do the stupidity to launch the fsk command to repair, I find all the files and directory in the special directory called Lost + found Being able to remake the original content, I have seen four times that it gives this unpleasant result. It also allows me to change the scenario. - If I use an internal disk partition instead of the external disk, you're fine. - If I use version 18.04, everything is fine even if I use the external disk - If I make a new partition on the external disk in version 19.10, I can shrink also without any problem. So I think there is a software regression for a very specific context. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1857914/+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 1858092] Re: Network Manager not saving OpenVPN password
** Package changed: ubuntu => network-manager (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in network-manager package in Ubuntu: New Bug description: Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+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 1858092] [NEW] Network Manager not saving OpenVPN password
You have been subscribed to a public bug: Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kwallet manager network openvpn -- Network Manager not saving OpenVPN password https://bugs.launchpad.net/bugs/1858092 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- 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 1858090] Re: Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
The attachment "keyboard-configuration.config.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858093] [NEW] Display Driver Issue
Public bug reported: Not able to Suspend/Hibernate and facing issues in brightness controlling. Also screen don't turn off once it is locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 17:30:41 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:096a] InstallationDate: Installed on 2019-12-25 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d0ddd98e-6672-461c-bb96-25092a84666e ro quiet splash acpi_backlight=vendor vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 0MNRJY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd06/25/2019:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn0MNRJY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- 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/1858093 Title: Display Driver Issue Status in xorg package in Ubuntu: New Bug description: Not able to Suspend/Hibernate and facing issues in brightness controlling. Also screen don't turn off once it is locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 17:30:41 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:096a] InstallationDate: Installed on 2019-12-25 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d0ddd98e-6672-461c-bb96-25092a84666e ro quiet splash acpi_backlight=vendor vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 0MNRJY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd06/25/2019:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn0MNRJY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
[Touch-packages] [Bug 1858090] Re: Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
** Patch added: "keyboard-configuration.config.patch" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+attachment/5317045/+files/keyboard-configuration.config.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] Re: Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
After making the keyboard detection search pattern for /proc/bus/input/devices more generic, dpkg-reconfigure keyboard- configuration works. The patch is attached. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] Re: Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
Analysis:
This is caused by keyboard-configuration trying and failing to detect a
keyboard.
It detects my USB keyboard using InterfaceClass 03, InterfaceSubClass 01, and
InterfaceProtocol 01 in /sys/bus/usb/devices/ .
It detects the built-in keyboard on my other computer using "AT Set" in
/proc/bus/input/devices .
However it does not detect the Surface Type Keyboard ('N: Name="Microsoft
Surface Type Cover Keyboard"') in /proc/bus/input/devices .
The problem is in the keyboard_present() function of line 36230 of
/var/lib/dpkg/info/keyboard-configuration.config .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1858090
Title:
Surface Type Cover not detected by dpkg-reconfigure keyboard-
configuration
Status in console-setup package in Ubuntu:
New
Bug description:
keyboard-configuration does not detect a Surface Type Cover as a
keyboard during dpkg-reconfigure. This causes it to skip the dialog
and prevents one from configuring the Type Cover.
$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
$ apt-cache policy keyboard-configuration
keyboard-configuration:
Installed: 1.191ubuntu3
Candidate: 1.191ubuntu3
Version table:
*** 1.191ubuntu3 500
500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
What I expected to happen:
# dpkg-reconfigure keyboard-configuration
[I get prompted with an interactive dialog asking me to configure the
keyboard]
What happened instead:
# dpkg-reconfigure keyboard-configuration
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
update-initramfs: deferring update (trigger activated)
[...]
[The expected dialog doesn't show up, and it goes straight to
rebuilding the boot image]
Workaround:
Plug in a standalone USB Keyboard before running the command.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.10
Package: console-setup 1.191ubuntu3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Tags: eoan
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: dialout kvm plugdev sudo systemd-journal wireshark
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Just got this on 19.10 on a thinkpad t470s. $ uname -a Linux hostname 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I run ZFS. My first thought was OOM, but can't see any mentions of it. ... jan. 02 09:51:06 hostname gnome-shell[27297]: Usage of object.actor is deprecated for ArgosButton get@resource:///org/gnome/shell/ui/environment.js:249:29 _processOutput@/home/larsfp/.local/share/gnome-shell/extensions/argos@pew.worldwide wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _update/<@/home/larsfp/.local/share/gnome-shell/extensions/argos@pew.worldwidemann. spawnWithCallback/<@/home/larsfp/.local/share/gnome-shell/extensions/ar...@pew.worl readStream/<@/home/larsfp/.local/share/gnome-shell/extensions/argos@pew.worldwidema jan. 02 09:51:30 hostname /usr/lib/gdm3/gdm-x-session[27136]: i965: Failed to submit batchbuffer: Bad address jan. 02 09:51:30 hostname seahorse[8246]: seahorse: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. jan. 02 09:51:30 hostname firefox[986]: firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. jan. 02 09:51:30 hostname gnome-shell[27297]: Gdk-Message: 09:51:30.655: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource te jan. 02 09:51:30 hostname at-spi-bus-launcher[27266]: X connection to :0 broken (explicit kill or server shutdown). jan. 02 09:51:30 hostname pulseaudio[26437]: X connection to :0 broken (explicit kill or server shutdown). ... -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in Mesa: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Unknown Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1794033/+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 1858090] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317043/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] ConsoleSetup.txt
apport information ** Attachment added: "ConsoleSetup.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317040/+files/ConsoleSetup.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317044/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] Keyboard.txt
apport information ** Attachment added: "Keyboard.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317042/+files/Keyboard.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] [NEW] Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
Public bug reported: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected eoan ** Tags added: apport-collected eoan ** Description changed: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 19.10 + Package: console-setup 1.191ubuntu3 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: dialout kvm plugdev sudo systemd-journal wireshark + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion:
[Touch-packages] [Bug 1858090] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317041/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
** Changed in: hwe-next Status: New => Fix Released -- 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/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: Fix Released Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Status in pulseaudio source package in Disco: Fix Released Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] Low, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. For the Bionic, This SRU also includes the fix of LP: #1556439, this fix is safe and is very low possible to introduce any regression too, because it just adds a sink-input/source-output state checking, if the sink-input/source-output is unlinking or unlinked, it is useless to move it to a new sink/source, furthermore it will trigger an assertion that make the pulseaudio crash, adding this check can fix this problem (LP: #1556439). [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+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
