[Touch-packages] [Bug 1825499]
please run the touchpad-edge-detector tool from the libevdev-utils package and post the output here, thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in systemd: Fix Released Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Status in libinput package in Fedora: Confirmed Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/systemd/+bug/1825499/+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 795540] Re: package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcsc-lite (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/795540 Title: package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Binary package hint: pcscd jadler@server:~$ lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 jadler@server:~$ apt-cache policy pcsc pcscada-dbg pcscd pcsc-omnikey pcsc-tools jadler@server:~$ apt-cache policy pcsc-lite N: Unable to locate package pcsc-lite jadler@server:~$ apt-cache policy pcscd pcscd: Installed: 1.7.0-2ubuntu2 Candidate: 1.7.0-2ubuntu2 Version table: *** 1.7.0-2ubuntu2 0 500 http://se.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages 100 /var/lib/dpkg/status Upgrading 10.10 to 11.04 ProblemType: Package DistroRelease: Ubuntu 11.04 Package: pcscd 1.7.0-2ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jun 10 08:17:33 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: pcsc-lite Title: package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to natty on 2011-06-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/795540/+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 1847904] Re: intel grafic
The correct latest Intel graphics driver is: /usr/lib/xorg/modules/drivers/modesetting_drv.so provided by package: xserver-xorg-core which you probably do have. So please describe what kind of problem you are trying to solve. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1847904 Title: intel grafic Status in Ubuntu: Incomplete Bug description: cant install intel grafic drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 13 14:59:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:15bd] InstallationDate: Installed on 2019-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1d57:fa01 Xenta Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X200MA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=704348ec-f63c-4238-870e-381e532c8448 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200MA.504 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200MA.504:bd11/13/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X200MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847904/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
jibel, that's the intended behaviour. We default to always switching to the most recent audio device plugged in. To disable that you will need to comment out: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif -- 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: Confirmed Bug description: 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. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. 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 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
Same issue as previous 3 reporters. All was fine until the latest update(s), I now have the hiss back... Any idea on what might've changed? -- 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/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1786574] Re: remove i2c-i801 from blacklist
Hi Khairul and Julian: I have sent the patch to lkml: https://patchwork.kernel.org/patch/10949569/ But we think Lenovo mixed up the touchpads PnP IDs in X240 series. Please passing "psmouse.synaptics_intertouch=0" in kernel parameter. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: In Progress Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1847597] Re: gnome-control-center cannot access google account
Changed the affected package. @Luigi: The error message indicates that Google requires some kind of verification. Do you have a verified Google address, and is it that address you enter? ** Package changed: gnome-control-center (Ubuntu) => gnome-online- accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1847597 Title: gnome-control-center cannot access google account Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: Good morning, If I run "gnome-control-center online-accounts" from the terminal and trying to add a Google account, I get this error: "Sign in with Google is temporarily disabled for this app. This app has not been verified yet by Google in order to use Google sign in". On the web, Google suggests to contact you, so here I am. Can you fix please? I would use my drive folders on my ubuntu 16.04. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1847597/+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 1847597] [NEW] gnome-control-center cannot access google account
You have been subscribed to a public bug: Good morning, If I run "gnome-control-center online-accounts" from the terminal and trying to add a Google account, I get this error: "Sign in with Google is temporarily disabled for this app. This app has not been verified yet by Google in order to use Google sign in". On the web, Google suggests to contact you, so here I am. Can you fix please? I would use my drive folders on my ubuntu 16.04. Thanks in advance. ** Affects: gnome-online-accounts (Ubuntu) Importance: Low Status: Incomplete -- gnome-control-center cannot access google account https://bugs.launchpad.net/bugs/1847597 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts 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 1847904] [NEW] intel grafic
Public bug reported: cant install intel grafic drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 13 14:59:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:15bd] InstallationDate: Installed on 2019-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1d57:fa01 Xenta Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X200MA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=704348ec-f63c-4238-870e-381e532c8448 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200MA.504 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200MA.504:bd11/13/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X200MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1847904 Title: intel grafic Status in xorg package in Ubuntu: New Bug description: cant install intel grafic drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 13 14:59:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:15bd] InstallationDate: Installed on 2019-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1d57:fa01 Xenta Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X200MA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=704348ec-f63c-4238-870e-381e532c8448 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200MA.504 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0
[Touch-packages] [Bug 1847902] [NEW] pam_nologin should optionally exclude users of the "wheel" group from its access restrictions
Public bug reported: During a remote system upgrade (18.04 to 19.04) something went south and after reboot the machine is stuck at some place in its boot sequence. SSH works, but trying to log-in with a sudo-capable user results in: "System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8)." As Ubuntu has moved away from full root users with passwords + allowing root logins over SSH, I'm totally locked out from my remote system. There is a bug reported for pam_nologin requesting to provide separate exclusion mechanism but in the meantime it is possible to implement a workaround to exclude administrative users from nologin restriction. Here's the bug: https://github.com/linux-pam/linux-pam/issues/42 And here is the workaround that should be implemented in Ubuntu: https://github.com/linux-pam/linux-pam/issues/42#issuecomment-367450193 ** Affects: pam (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1847902 Title: pam_nologin should optionally exclude users of the "wheel" group from its access restrictions Status in pam package in Ubuntu: New Bug description: During a remote system upgrade (18.04 to 19.04) something went south and after reboot the machine is stuck at some place in its boot sequence. SSH works, but trying to log-in with a sudo-capable user results in: "System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8)." As Ubuntu has moved away from full root users with passwords + allowing root logins over SSH, I'm totally locked out from my remote system. There is a bug reported for pam_nologin requesting to provide separate exclusion mechanism but in the meantime it is possible to implement a workaround to exclude administrative users from nologin restriction. Here's the bug: https://github.com/linux-pam/linux-pam/issues/42 And here is the workaround that should be implemented in Ubuntu: https://github.com/linux-pam/linux-pam/issues/42#issuecomment-367450193 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1847902/+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 1586528] Re: Avahi-daemon withdraws address record
I wonder how do you , guys, declare the bug as invalid while the issue is exists and it's still relevant. You could at least call it duplicate with a reference to another issue, but INVALID it is not. To the point: This issue is relevant for me on a freshly installed Kubuntu 19.04. I tried to use the workaround proposed by @ronny, but it doesn't look as a good idea: sudo apt remove isc-dhcp-client Sun 13 Oct 2019 13:45:45 IDT Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dns-root-data dnsmasq-base isc-dhcp-common libdns-export1104 libisc-export1100 libkf5modemmanagerqt6 libndp0 libopenconnect5 libstoken1 libteamdctl0 libtomcrypt1 libtommath1 libtss2-esys0 libtss2-udev pptp-linux Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: isc-dhcp-client network-manager network-manager-gnome network-manager-pptp network-manager-pptp-gnome plasma-nm ubuntu-minimal -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1838806] Re: vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge
Fixed in mesa-vulkan-drivers:amd64 (19.0.8-0ubuntu0~18.04.3) ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1838806 Title: vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge Status in mesa package in Ubuntu: Fix Released Bug description: After yesterday update to 5.0.0-23-generic of the linux-generic- hwe-18.04 kernel every vulkan applications (e.g. steam or vulkan- smoketest) make my desktop freeze (ssh continue working, but the only option is to use sysqr to reboot the system). Similar bug reports: https://github.com/ValveSoftware/steam-for-linux/issues/6268 says it has been fixed in mesa 19.X but don't specify which version this seems related too https://lists.freedesktop.org/archives/amd-gfx/2018-March/020569.html APU: ryzen 2200g workaround: use AMDVLK instead of RADV ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 thread vulkan-smoketes pid 6759) ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: in page starting at address 0x00174000 from 27 ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0030153D ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 thread vulkan-smoketes pid 6759) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mesa-vulkan-drivers (not installed) ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 2 20:11:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] [1002:15dd] InstallationDate: Installed on 2018-11-30 (244 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.90 dmi.board.name: AB350M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.90:bd07/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1838806/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell
Sorry (again) for the late reply. I just got an opportunity to install a fresh ubuntu 19.04, so I thought I would give a try to the patch... But on this fresh install, I do not have the problem... (without even enabling proposed packaged). I don't even understand *why* the x11-bell module is *not* loaded... (I did install the ubuntu-sounds package, as this is a condition in start-pulseaudio-x11). -- 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/1827842 Title: pulseaudio should not load module-x11-bell in gnome-shell Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Disco: Fix Committed Bug description: * Impact The package force load a bell sound which can conflicts with the user configuration * Test case - Enable a login sound in session - Login into a GNOME/Ubuntu session -> the configured sound should be played * Regression potential Try other desktop environments to make sure their login sound behaviour isn't changed, it shouldn't since the customization dropped was specific to the Ubuntu sound theme --- The package `pulseaudio` installs a startup script in `/etc/xdg/autostart/pulseaudio.desktop`, which itself runs `/usr/bin/start-pulseaudio-x11`, which loads a number of x11 related modules in `pulseaudio`. One of these modules is `module-x11-bell`, which makes `pulseaudio` play a sound each time a system bell is emitted (usually by terminal applications, such as bash or vim). This is redundant with gnome-shell, which is also able to handle the system bell (through the gsetting key `org.gnome.desktop.sound event-sounds`). The gnome system bell is directly configurable by the user (Settings > Sound), so it should be preferred over pulseaudio's own system bell. I suggest to patch the `/usr/bin/start-pulseaudio-x11`, to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome Shell (e.g. if GNOME_SHELL_SESSION_MODE is set). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1786574] Re: remove i2c-i801 from blacklist
i'm having the issue again, i run the evtest and the output as attached ** Attachment added: "input.txt" https://bugs.launchpad.net/hwe-next/+bug/1786574/+attachment/5296792/+files/input.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: In Progress Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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
