[Touch-packages] [Bug 1782984] Re: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libx11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04 Status in libx11 package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+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 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
I was thinking about this over the weekend, and I think we overlooked the impact of setting CONFIG_SECURITY_DMESG_RESTRICT in the kernel config has on downstream users of Groovy's kernel, namely when it becomes Focal's HWE kernel. Focal won't be receiving any patches for /usr/bin/dmesg, so I think it is better to not set CONFIG_SECURITY_DMESG_RESTRICT in kernel config, but to instead set kernel.dmesg_restrict systctl to 1 in /etc/sysctl.d/10-kernel-hardening.conf. This would ensure it only changes Groovy onward, and doesn't cause any regressions for Focal HWE users. I have emailed Seth Forshee asking to revert the config change. -- 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/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may
[Touch-packages] [Bug 1886245] Re: BCM20702A bluetooth freezing after boot
This looks like a hardware problem or a kernel bug so reassigning... ** Summary changed: - bluetooth freezing after boot + BCM20702A bluetooth freezing after boot ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Summary changed: - BCM20702A bluetooth freezing after boot + BCM20702A bluetooth freezing for 4-9 seconds ** Summary changed: - BCM20702A bluetooth freezing for 4-9 seconds + BCM20702A bluetooth mouse freezing for 4-9 seconds -- 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/1886245 Title: BCM20702A bluetooth mouse freezing for 4-9 seconds Status in linux package in Ubuntu: Confirmed Bug description: Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will work as normal. I am using a plugable USB Bluetooth adapter for Bluetooth connections. I am using blueman to connect. Mouse used is a Kensington Exper Mouse Wireless Trackball Issue does not occur with bluetooth speakers, or headphones. Computer- Dell Precision 5520. Logs show these errors as below bt_uhid_send: Invalid argument (22) Bluetooth: hci0: advertising data len corrected Description: Ubuntu 20.04 LTS Release: 20.04 blueman: Installed: 2.1.2-1 Candidate: 2.1.2-1 Version table: *** 2.1.2-1 500 500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 13:24:01 2020 InstallationDate: Installed on 2020-06-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.2 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:7E:32:2F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:193521 acl:13666 sco:0 events:137 errors:0 TX bytes:5858 acl:61 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886245/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug has been marked a duplicate of bug 1782984 PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04 ** Bug watch removed: Claws Mail bugzilla #4203 http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 ** Bug watch removed: redmine.audacious-media-player.org/issues #798 https://redmine.audacious-media-player.org/issues/798 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: New Bug description: GTK2 applications randomly crash or freeze with error like: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. : ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. where is the name of the executable, e.g. audacious, soffice.bin, etc. RELATED BUGS LibreOffice: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161 PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984 Audacious: https://redmine.audacious-media-player.org/issues/798 FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084 ClawsMail: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 OTHER APPLICATIONS SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1782984] Re: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04
** Changed in: libx11 (Ubuntu) Importance: Undecided => High ** Bug watch removed: github.com/rust-windowing/glutin/issues #1034 https://github.com/rust-windowing/glutin/issues/1034 ** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/issues #108 https://gitlab.freedesktop.org/mesa/mesa/issues/108 ** Bug watch removed: gitlab.gnome.org/GNOME/gtk/-/issues #2767 https://gitlab.gnome.org/GNOME/gtk/-/issues/2767 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04 Status in libx11 package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+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 1886351] [NEW] [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while
Public bug reported: I recently installed Ubuntu 20.04 on my Toshiba Satellite-L740 laptop. I seem to lose audio periodically. At first I thought I hit something on the keyboard accidentally, but can now confirm it is a random occurrence with no input from me. I have tried toggling the mute/volume of the system but cannot recover the audio. When the audio is lost there is still audio activity shown on the VU meter from the source shown under the output device in sound settings. I also plugged in headphones and am able to hear audio in the headset. When unplugging headset the sound does not return to the speakers. There was no issue with audio on the laptop prior to installing Ubuntu 20.04 (previously Windows 10). It seems to come back on it's own sometimes but then gets lost again. A reboot of the machine sometimes recovers the audio but sometimes not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe1410 F pulseaudio /dev/snd/pcmC0D0c: joe1410 F...m pulseaudio /dev/snd/pcmC0D0p: joe1410 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 19:23:02 2020 InstallationDate: Installed on 2020-06-02 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jul 05 17:44:12 joe dbus-daemon[729]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.26' (uid=125 pid=925 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 17:44:17 joe dbus-daemon[729]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.38' (uid=125 pid=925 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 17:44:56 joe systemd[900]: pulseaudio.service: Succeeded. Jul 05 17:45:05 joe systemd[900]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2012 dmi.bios.vendor: INSYDE dmi.bios.version: 2.60 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-01V00E:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L745 dmi.product.sku: PSK0YU-01V00E dmi.product.version: PSK0YU-01V00E dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1886351 Title: [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: I recently installed Ubuntu 20.04 on my Toshiba Satellite-L740 laptop. I seem to lose audio periodically. At first I thought I hit something on the keyboard accidentally, but can now confirm it is a random occurrence with no input from me. I have tried toggling the mute/volume of the system but cannot recover the audio. When the audio is lost there is still audio activity shown on the VU meter from the source shown under the output device in sound settings. I also plugged in headphones and am able to hear audio in the headset. When unplugging headset the sound does not return to the speakers. There was no issue with audio on the laptop prior to installing Ubuntu 20.04 (previously Windows 10). It seems to come back on it's own sometimes but then gets lost again. A reboot of the machine sometimes recovers the audio but sometimes not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Touch-packages] [Bug 1886330] Re: pulseaudio not working in Virtualbox
The attached info shows PulseAudio was running when you reported the bug: !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes Are you sure the problem is PulseAudio not running (the process should be named 'pulseaudio')? If so then please check for any crash files in /var/crash If you don't find any relevant crash files then please wait until the problem happens again and then run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1886330 Title: pulseaudio not working in Virtualbox Status in pulseaudio package in Ubuntu: Incomplete Bug description: I run my "work" VMs and in Xubuntu pulse audio often does not start. In this dump I tried to start music through Firefox and through my media player quodlibet and none of the audio starts. See attachment with the pulseaudio volume control and quodlibet stuck on time 0:00 like Firefox. I do not have the problem with plain Ubuntu, Ubuntu Mate nor with Ubuntu Studio. The problem is annoying, because I use Xubuntu for office and communication like Email and the WhatsApp/Firefox/ICE combination and with this bug WhatsApp is useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1490 F pulseaudio /dev/snd/pcmC0D0c: bertadmin 1490 F...m pulseaudio /dev/snd/pcmC0D0p: bertadmin 1490 F...m pulseaudio /dev/snd/timer: bertadmin 1490 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 5 11:33:48 2020 InstallationDate: Installed on 2018-03-11 (847 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886330/+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 1886161] Re: UU should work on roaming laptops
** Summary changed: - UU is almost useless on itinerant laptops + UU should work on roaming laptops -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops Status in unattended-upgrades package in Ubuntu: New Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
** Changed in: dnsmasq (Ubuntu) Status: Triaged => New ** Changed in: dnsmasq (Ubuntu Precise) Status: Triaged => New ** Changed in: network-manager (Ubuntu) Status: Invalid => New ** Changed in: network-manager (Ubuntu Precise) Status: Invalid => New ** Changed in: dnsmasq (Ubuntu) Assignee: nikhil (nikhilnikki) => (unassigned) ** Changed in: dnsmasq (Ubuntu Precise) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Changed in: network-manager (Ubuntu Precise) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Changed in: network-manager (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Summary changed: - dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers + SDFEEWRDSsdfdasfsdf ** Description changed: - A number of reports already filed against network-manager seem to - reflect this problem, but to make things very clear I am opening a new - report. Where appropriate I will mark other reports as duplicates of - this one. - - Consider a pre-Precise system with the following /etc/resolv.conf: - - nameserver 192.168.0.1 - nameserver 8.8.8.8 - - The first address is the address of a nameserver on the LAN that can - resolve both private and public domain names. The second address is the - address of a nameserver on the Internet that can resolve only public - names. - - This setup works fine because the GNU resolver always tries the first- - listed address first. - - Now the administrator upgrades to Precise and instead of writing the - above to resolv.conf, NetworkManager writes - - server=192.168.0.1 - server=8.8.8.8 - - to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to - resolv.conf. Resolution of private domain names is now broken because - dnsmasq treats the two upstream nameservers as equals and uses the - faster one, which could be 8.8.8.8. + dfasfwerwq2323sf ** Tags removed: precise xenial ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: SDFEEWRDSsdfdasfsdf Status in dnsmasq package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Precise: New Status in network-manager source package in Precise: New Status in dnsmasq package in Debian: New Bug description: dfasfwerwq2323sf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
** Description changed: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. - Users in groups 'adm', 'systemd-journal' can see all messages. - Pass -q to turn off this notice. + Users in groups 'adm', 'systemd-journal' can see all messages. + Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: - 1) CONFIG_SECURITY_DMESG_RESTRICT=y in the kernel. + 1) Add kernel.dmesg_restrict = 1 to +/etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - - Ownership changes to root:adm - - Permissions changed to 0750 (-rwxr-x---) - - Add cap_syslog capability to binary. - 3) Add a commented out '# kernel.dmesg_restrict = 0' to -/etc/sysctl.d/10-kernel-hardening.conf + - Ownership changes to root:adm + - Permissions changed to 0750 (-rwxr-x---) + - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. + + Test packages are available in the following ppa: + https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. - Users have the ability to disable DMESG_RESTRICT by uncommenting the - sysctl in /etc/sysctl.d/10-kernel-hardening.conf. + Users have the ability to disable DMESG_RESTRICT by changing + kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf + from '1' to '0', followed by a reboot. -- 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/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in
[Touch-packages] [Bug 1886331] Re: Xorg freeze
The attached file 'dmesg.0' shows the amdgpu kernel driver crashed on startup. So I assume that file is meant to show a case where the problem happened. ** Tags added: amdgpu ** Summary changed: - Xorg freeze + Cannot boot sometimes - black screen with a mouse pointer. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Cannot boot sometimes - black screen with a mouse pointer. + [amdgpu] Cannot boot sometimes - black screen with a mouse pointer. -- 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/1886331 Title: [amdgpu] Cannot boot sometimes - black screen with a mouse pointer. Status in linux package in Ubuntu: New Bug description: Cannot boot sometimes - black screen with a mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 18:47:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615] InstallationDate: Installed on 2020-06-05 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Laptop 15-cw1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 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/31/2019 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8615 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.34:bd07/31/2019:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cw1xxx dmi.product.sku: 6QF12EA#AB7 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886331/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
** Summary changed: - PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04 + Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+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 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
I have created patches for both the procps package and the util-linux package which implements the proposed changes. You can find test packages in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test Debdiff for procps: https://paste.ubuntu.com/p/qvmHgMhXSj/ Debdiff for util-linux: https://paste.ubuntu.com/p/SYrK9xrwnP/ I have tested the packages on a Groovy daily build, and the changes function as intended. The default user, who is in the adm group can use dmesg freely, and unprivileged users can no longer access dmesg. I am looking for feedback about the maintainability of the util-linux patches, particularly about the additional burden it would place on merges performed in the future. My main worry is the additional dependency of libcap2-bin needed to set CAP_SYSLOG on /bin/dmesg. -- 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/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188
[Touch-packages] [Bug 1886204] Re: Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu) ** Tags added: radeon -- 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/1886204 Title: Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Initially, Ubuntu started with far lower resolution than my monitor. I've tried xrandr --newmode command*, it temporarily helps to get back to my original 1600X900 resolution. But now screen sometimes go back to that lower resolution (and randpomly comes back to normal after some time), and xrandr doesn't help. Plus, my screen keeps flickering, sometimes quite frequently. Combined with low resolution, it has become almost unbearable at this point. Things work alright with windows 10 (dual boot). Further details: 1. Sometimes, but not always, simply going to Display Setting by GUI or typing xrandr in command line fixes it. 2. I sometimes see "drm:radeon_vga_detect [radeon]] ERROR VGA-1: probed a monitor but no|invalid EDID" while shutting down or in /var/log/syslog. Also quite frequently "ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id" in the log. 3. Using read-edid package, I noticed that while on low res, it can't detect EDID on any bus. However if I keep running this command, at some point it successfully reads & parses EDID. Then, if I go to Display Setting, or after some time automatically- the resolution comes back to normal. 4. Reinstalled ubuntu 20.04, removed that cron job. Didn't change the situation. 5. I've tried Wayland, awesome window manager, lightdm display manager. I'd rather not change the GNOME environment. 6. Tried Ubuntu 18.04.4 (current OS), now its always low resolution. Config: CPU: Ryzen 3700x, MB: Asus Tuf x570 Gaming plus, Monitor: Samsung SyncMaster E2020 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.7.1-050701-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 20:53:51 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Turks PRO [Radeon HD 6570/7570/8550] [174b:e193] InstallationDate: Installed on 2020-07-02 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic root=UUID=e26c767f-e791-4209-905a-0e9eaa3bc363 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.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/+source/xserver-xorg-video-ati/+bug/1886204/+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 1886269] Re: ps/2 mouse not working
I can't see any evidence of a PS/2 mouse being detected in your logs. Only a Bluetooth mouse. If this is a software bug then it would probably be a kernel bug. ** Package changed: xorg (Ubuntu) => linux (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/1886269 Title: ps/2 mouse not working Status in linux package in Ubuntu: New Bug description: ps/2 mouse not working , gave some command in terminal , this bug came out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 19:25:07 2020 DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:d613] InstallationDate: Installed on 2020-06-30 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago) dmi.bios.date: 01/08/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Fri Jul 3 08:17:23 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886269/+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 1876670] Re: nfs does not mount at boot with bridge
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1876670 Title: nfs does not mount at boot with bridge Status in systemd package in Ubuntu: Expired Bug description: I am running a Ubuntu 20.04 server with lxd and kvm/qemu. I try to connect a nfs share at boot. It is working while I do not configure any bridge with netplan. I am creating directly a systemd service for the NFS mount but I have the same problem if I edit the fstab file. #/etc/systemd/system/mnt-nas.mount [Unit] Description=NAS devices After=network.target [Mount] What=192.168.1.20:/volume2/media Where=/mnt/nas Type=nfs Options=_netdev,auto [Install] WantedBy=multi-user.target ## TEST WITHOUT BRIDGE #/etc/netplan/01-netcfg.yaml network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes root@bowser:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether f8:75:a4:00:be:ad brd ff:ff:ff:ff:ff:ff inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic eno1 valid_lft 86244sec preferred_lft 86244sec inet6 fe80::fa75:a4ff:fe00:bead/64 scope link valid_lft forever preferred_lft forever 3: wlp1s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 60:f2:62:38:d7:c2 brd ff:ff:ff:ff:ff:ff root@bowser:~# journalctl -b ... May 04 08:58:08 bowser systemd-networkd[535]: eno1: Gained carrier May 04 08:58:08 bowser kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None May 04 08:58:08 bowser kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready May 04 08:58:08 bowser systemd[1]: systemd-rfkill.service: Succeeded. May 04 08:58:08 bowser set-cpufreq[795]: Setting powersave scheduler for all CPUs May 04 08:58:08 bowser systemd[1]: ondemand.service: Succeeded. May 04 08:58:08 bowser systemd[1]: dmesg.service: Succeeded. May 04 08:58:09 bowser systemd-networkd[535]: eno1: Gained IPv6LL May 04 08:58:09 bowser systemd-timesyncd[757]: Network configuration changed, trying to establish connection. May 04 08:58:10 bowser systemd-networkd[535]: eno1: DHCPv4 address 192.168.1.100/24 via 192.168.1.1 May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, trying to establish connection. May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, trying to establish connection. May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, trying to establish connection. May 04 08:58:10 bowser systemd-networkd-wait-online[611]: managing: eno1 May 04 08:58:10 bowser systemd[1]: Finished Wait for Network to be Configured. May 04 08:58:10 bowser systemd[1]: Reached target Network is Online. May 04 08:58:10 bowser systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped. May 04 08:58:10 bowser systemd[1]: Reached target Remote File Systems (Pre). May 04 08:58:10 bowser systemd[1]: Mounting NAS devices... May 04 08:58:10 bowser systemd[1]: Starting Availability of block devices... May 04 08:58:10 bowser systemd[1]: Condition check resulted in Pollinate to seed the pseudo random number generator being skipped. May 04 08:58:10 bowser systemd[1]: Starting OpenBSD Secure Shell server... May 04 08:58:10 bowser systemd[1]: Finished Availability of block devices. May 04 08:58:10 bowser kernel: FS-Cache: Loaded May 04 08:58:10 bowser sshd[952]: Server listening on 0.0.0.0 port 22. May 04 08:58:10 bowser sshd[952]: Server listening on :: port 22. May 04 08:58:10 bowser systemd[1]: Started OpenBSD Secure Shell server. May 04 08:58:10 bowser kernel: FS-Cache: Netfs 'nfs' registered for caching May 04 08:58:10 bowser kernel: NFS: Registering the id_resolver key type May 04 08:58:10 bowser kernel: Key type id_resolver registered May 04 08:58:10 bowser kernel: Key type id_legacy registered May 04 08:58:10 bowser systemd[1]: /lib/systemd/system/rpc-statd.service:16: PIDFile= references a path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly. May 04 08:58:10 bowser systemd[1]: Starting Preprocess NFS configuration... May 04 08:58:10 bowser systemd[1]: nfs-config.service: Succeeded. May 04 08:58:10 bowser systemd[1]: Finished Preprocess NFS configuration. May 04 08:58:10
[Touch-packages] [Bug 1876915] Re: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1876915 Title: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: Expired Bug description: Im not sure what caused this problem ProblemType: Package DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat May 2 11:27:39 2020 DpkgHistoryLog: Start-Date: 2020-05-02 11:27:19 Commandline: /usr/bin/unattended-upgrade Upgrade: libcups2:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), libcups2:i386 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-server-common:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-common:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-bsd:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-core-drivers:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-daemon:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), libcupsimage2:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-client:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-ipp-utils:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1) ErrorMessage: installed cups-daemon package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-30 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. Q500A Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d1314bd9-a342-4a79-ba05-fd27f747bc14 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d1314bd9-a342-4a79-ba05-fd27f747bc14 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: cups Title: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-04-02 (32 days ago) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q500A.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q500A 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.:bvrQ500A.205:bd08/17/2012:svnASUSTeKCOMPUTERINC.:pnQ500A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ500A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Q dmi.product.name: Q500A dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1876915/+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 1886259] Re: Nvidia driver is not in the correct directory
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (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/1886259 Title: Nvidia driver is not in the correct directory Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Ubuntu 20.04 The packages installed by the metapackage nvidia-driver-440 do not put the nvidia x server module in the right place. The server cannot find it. My file /var/log/Xorg.0.log was collected by apport. nvidia-driver-440_440.100-0ubuntu0.20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Jul 4 04:46:32 2020 DistUpgraded: 2020-06-01 17:37:38,642 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0532] InstallationDate: Installed on 2016-12-01 (1310 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=69311ad3-1ba4-46b2-80b4-5e8986e36f36 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (32 days ago) dmi.bios.date: 02/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0YW5N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd02/06/2013:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0YW5N5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1886259/+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 1886246] Re: Xorg freeze
That sounds like two different issues so we will make this bug just about the mouse problem. Please open a new bug for the other issue if you like. It seems like there's a hardware/kernel problem with that mouse due to these occasional messages: [ 11273.560] (II) event11 - YSPRINGTECH USB OPTICAL MOUSE: SYN_DROPPED event - some input events have been lost. [ 12901.284] (II) event6 - YSPRINGTECH USB OPTICAL MOUSE: SYN_DROPPED event - some input events have been lost. [ 15824.486] (II) event6 - YSPRINGTECH USB OPTICAL MOUSE: SYN_DROPPED event - some input events have been lost. So please try a different USB mouse and/or a different USB port. ** Summary changed: - Xorg freeze + Sometimes on my lock screen, my mouse stops for a moment ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Description changed: - Sometimes on my lock screen, my mouse stops for a moment, and also many - times certain application freezes and then I have to force quit them. - Also, it is not going too fast, it takes much time to boot up. + Sometimes on my lock screen, my mouse stops for a moment Please send me the solution I had recently sifted form windows to ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 10:22:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] [1002:9838] (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] [1025:104b] + Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] [1002:9838] (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] [1025:104b] InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire ES1-520 ProcEnviron: - LANGUAGE=en_IN:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + LANGUAGE=en_IN:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=01e0d428-3558-4f95-a0f0-994b27c807c3 ro quiet splash i8042.nopnp vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Bellemere_BE dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion: dmi.product.family: KB dmi.product.name: Aspire ES1-520 dmi.product.sku: Aspire ES1-520_104B_V1.06 dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886246 Title: Sometimes on my lock screen, my mouse stops for a moment Status in linux package in Ubuntu: Incomplete Bug description: Sometimes on my lock screen, my mouse stops for a moment Please send me the solution I had recently sifted form windows to ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
** Summary changed: - Resizing any window will randomly result in glitchy appearance for a fraction of a second + Resizing any window will randomly result in graphics corruption for a fraction of a second -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms
@Dan, can you let us know when we can expect the SRU progress to Focal to complete please? -- 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/1883846 Title: hwdb: Mask rfkill event from intel-hid on HP platforms Status in HWE Next: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Fix Committed Bug description: [Impact] Press wireless hotkey on HP's latest generation laptops generate two rfkill events, prevent airplane mode from turning off. One event is from intel-hid and the other one is from hp-wireless. [Fix] Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use rfkill from hp-wireless. [Test] With the one-liner fix, press wireless hotkey only generate one rfkill event, hence airplane mode works as expected. [Regression Potential] Low, use hp-wireless over intel-hid is anticipated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883846/+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 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.
same problem on Ubuntu 18.04, when running mate-polkit command in terminal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1222356 Title: WARNING: Couldn't register with accessibility bus: Did not receive a reply. Status in at-spi2-core package in Ubuntu: Fix Released Status in at-spi2-core package in Debian: Fix Released Bug description: The following warnings/errors appear after calling ubuntu-bug ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport-gtk 2.12.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 10:54:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+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 1876219] Re: iris driver for old cpu
@star-gmx : The above did work for me (but I only tried setting the variable before the command such as "VARIABLE=value command"), setting this variable MESA_LOADER_DRIVER_OVERRIDE=i965 for anything that uses the MESA driver, stops segmentation faults from happening. -- 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/1876219 Title: iris driver for old cpu Status in mesa package in Ubuntu: Confirmed Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1886330] [NEW] pulseaudio not working in Virtualbox
Public bug reported: I run my "work" VMs and in Xubuntu pulse audio often does not start. In this dump I tried to start music through Firefox and through my media player quodlibet and none of the audio starts. See attachment with the pulseaudio volume control and quodlibet stuck on time 0:00 like Firefox. I do not have the problem with plain Ubuntu, Ubuntu Mate nor with Ubuntu Studio. The problem is annoying, because I use Xubuntu for office and communication like Email and the WhatsApp/Firefox/ICE combination and with this bug WhatsApp is useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1490 F pulseaudio /dev/snd/pcmC0D0c: bertadmin 1490 F...m pulseaudio /dev/snd/pcmC0D0p: bertadmin 1490 F...m pulseaudio /dev/snd/timer: bertadmin 1490 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 5 11:33:48 2020 InstallationDate: Installed on 2018-03-11 (847 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot_2020-07-05_11-52-59.png" https://bugs.launchpad.net/bugs/1886330/+attachment/5389892/+files/Screenshot_2020-07-05_11-52-59.png -- 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/1886330 Title: pulseaudio not working in Virtualbox Status in pulseaudio package in Ubuntu: New Bug description: I run my "work" VMs and in Xubuntu pulse audio often does not start. In this dump I tried to start music through Firefox and through my media player quodlibet and none of the audio starts. See attachment with the pulseaudio volume control and quodlibet stuck on time 0:00 like Firefox. I do not have the problem with plain Ubuntu, Ubuntu Mate nor with Ubuntu Studio. The problem is annoying, because I use Xubuntu for office and communication like Email and the WhatsApp/Firefox/ICE combination and with this bug WhatsApp is useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1490 F pulseaudio /dev/snd/pcmC0D0c: bertadmin 1490 F...m pulseaudio /dev/snd/pcmC0D0p: bertadmin 1490 F...m pulseaudio /dev/snd/timer: bertadmin 1490 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 5 11:33:48 2020 InstallationDate: Installed on 2018-03-11 (847 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886330/+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 1886331] [NEW] Xorg freeze
Public bug reported: Cannot boot sometimes - black screen with a mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 18:47:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615] InstallationDate: Installed on 2020-06-05 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Laptop 15-cw1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 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/31/2019 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8615 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.34:bd07/31/2019:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cw1xxx dmi.product.sku: 6QF12EA#AB7 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu ** Attachment added: "dmesg.0" https://bugs.launchpad.net/bugs/1886331/+attachment/5389899/+files/dmesg.0 -- 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/1886331 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Cannot boot sometimes - black screen with a mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 18:47:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615] InstallationDate: Installed on 2020-06-05 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Laptop 15-cw1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 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/31/2019 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8615 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP
[Touch-packages] [Bug 1886314] [NEW] preinstall `earlyoom` by default
Public bug reported: Fedora done this https://fedoraproject.org/wiki/Changes/EnableEarlyoom ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1886314 Title: preinstall `earlyoom` by default Status in ubuntu-meta package in Ubuntu: New Bug description: Fedora done this https://fedoraproject.org/wiki/Changes/EnableEarlyoom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1886314/+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 1787460] Re: Unattended upgrades removed linux-image-generic
The issues with virtualbox and hwe can be tracked in bug 1866518 or bug 1874309 ** No longer affects: linux-meta (Ubuntu) ** No longer affects: linux-meta (Ubuntu Trusty) ** No longer affects: linux-meta (Ubuntu Xenial) ** No longer affects: linux-meta (Ubuntu Bionic) ** No longer affects: linux-meta (Ubuntu Cosmic) ** No longer affects: linux-meta (Ubuntu Disco) ** No longer affects: linux-meta-hwe (Ubuntu) ** No longer affects: linux-meta-hwe (Ubuntu Trusty) ** No longer affects: linux-meta-hwe (Ubuntu Xenial) ** No longer affects: linux-meta-hwe (Ubuntu Bionic) ** No longer affects: linux-meta-hwe (Ubuntu Cosmic) ** No longer affects: linux-meta-hwe (Ubuntu Disco) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+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 1258919] Re: 067b:2305 printing issue with parallel-to-usb adapter
I am using PL2305 to print to an old Fujitsu line printer and was missing the last few lines of the printout every time. The workaround suggested above worked for me, too :) I changed: lpadmin -p fujitsu -v usb://Unknown/Printer -E to lpadmin -p fujitsu -E -v parallel:/dev/usb/lp0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1258919 Title: 067b:2305 printing issue with parallel-to-usb adapter Status in cups package in Ubuntu: Confirmed Bug description: I have an old HP Deskjet 710C parallel printer. I really don't print a lot, so it ages well. I just replaced my former desktop with a new barebone without parallel port - no space to embed a PCI IEEE 1284 adapter. So I just bought a cable which is a parallel-to-usb adapter : it is a Sweex adapter, the kernel recognizes it as : Prolific Technology, Inc. PL2305 Parallel Port I configured cups to use this new adapter, with the same old pnm2ppa driver. When I try to print a test page from cups (or other printings) it goes well, until close to the end, when the printing suddenly stops, without the sheet being released : I have to power off the printer, which as a side effect triggers the sheet ejection before power off. I read various articles and forums on this topic before posting. Playing with usblp, kernel blacklists and /dev/usb/lp0 does not solve anything. I wanted to be sure that it was not the Prolific controller which was flawed. So I connected it to a windows 7 virtual machine into Virtualbox; Windows installed various drivers, and eventually various printings ran seamlessly - without my issue on GNU/Linux. So my conclusion is that the controller is ok. I also just tested mainline kernel http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.13-rc3-trusty/linux- image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201312061335_amd64.deb . No improvement, my test page stops being printed at the same spot close to the end. So I can assume that there is a bug in the controller's driver. Best regards R. Grasso WORKAROUND: Setup Lprng locally from lpr - not configurable from KDE/Systemsettings - then from my main computer with CUPS 1.6.1, I configured a remote printer: lpd://10.0.0.1/lp ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image (not installed) ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sun Dec 8 13:53:43 2013 HibernationDevice: RESUME=UUID=a16e3a2c-0f38-4e72-9c51-145a864b60a1 InstallationDate: Installed on 2013-11-06 (32 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Shuttle Inc. DS47D MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=8c51cecc-9054-4edc-8b06-afb7bb4ebd2e ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FS47D dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03:bd08/09/2013:svnShuttleInc.:pnDS47D:pvrV1.0:rvnShuttleInc.:rnFS47D:rvr1.0:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: DS47D dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1258919/+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 1876219] Re: iris driver for old cpu
@akechishiro: Did the above mentioned workaround works for you? -- 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/1876219 Title: iris driver for old cpu Status in mesa package in Ubuntu: Confirmed Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1310186] Re: mediascanner prevents unmounting usb device
** Changed in: mediascanner2 (Ubuntu) Status: Triaged => Fix Released ** Changed in: mediascanner2 (Ubuntu) Assignee: (unassigned) => zawlatt (ayngzawlatt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1310186 Title: mediascanner prevents unmounting usb device Status in mediascanner2 package in Ubuntu: Fix Released Bug description: Trying to unmount a block device I just mounted, I get the following error (sorry for not resetting the locale. It says "Device is busy"): :~$ sudo umount /media/tkluck/tjk-backup umount2: Apparaat of hulpbron is bezig umount: /media/tkluck/tjk-backup: apparaat is bezig (Welke processen het apparaat gebruiken kan mogelijk gevonden worden met behulp van lsof(8) of fuser(1).) umount2: Apparaat of hulpbron is bezig I get the same error in a dialog window when trying to unmount from the file manager. Using lsof shows that the media-scanner daemon is the culprit: tkluck@ultrabook-tjk:~$ lsof /media/tkluck/tjk-backup COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME mediascan 2898 tkluck 16r DIR 252,3 2498562 /media/tkluck/tjk-backup mediascan 2898 tkluck 17r DIR 252,3 4096 50855937 mediascan 2898 tkluck 18r DIR 252,3 4096 39080372 mediascan 2898 tkluck 19r DIR 252,312288 39080513 mediascan 2898 tkluck 20r DIR 252,320480 39080525 mediascan 2898 tkluck 21r DIR 252,3 4096 46792990 mediascan 2898 tkluck 22r DIR 252,3 4096 46792991 mediascan 2898 tkluck 23r DIR 252,316384 46793749 mediascan 2898 tkluck 24r DIR 252,3 4096 47317994 mediascan 2898 tkluck 25r DIR 252,3 4096 47317997 mediascan 2898 tkluck 26r DIR 252,3 4096 47317999 Sending it sudo kill -9 2898 solved this for me. This is on Ubuntu GNOME 14.04. I uninstalled the mediascanner2.0 to solve this "once and for all" (which has no other impact since I do not use Unity). My guess is that the scan usually finishes quickly after mounting. But because this particular drive contains a big filetree, it doesn't, resulting in the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1310186/+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 1886336] [NEW] Network Manager permissions issue
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 network-manager: Installed: 1.22.10-1ubuntu2.1 Candidate: 1.22.10-1ubuntu2.1 Version table: *** 1.22.10-1ubuntu2.1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages Having recently updated from 19.19 to 20.04, I am now unable to add/edit any connections. When I try, a dialogue box pops up saying; "Failed to activate {SSID} Not authorized to control networking." I have spent some time trawling the web but no obvious solution was found, but one post mentioned "nmcli g permissions" which I tried as user and using sudo. User output; PERMISSION VALUE org.freedesktop.NetworkManager.enable-disable-network no org.freedesktop.NetworkManager.enable-disable-wifi no org.freedesktop.NetworkManager.enable-disable-wwan no org.freedesktop.NetworkManager.enable-disable-wimax no org.freedesktop.NetworkManager.sleep-wake no org.freedesktop.NetworkManager.network-control auth org.freedesktop.NetworkManager.wifi.share.protecte d no org.freedesktop.NetworkManager.wifi.share.open no org.freedesktop.NetworkManager.settings.modify.sys tem no org.freedesktop.NetworkManager.settings.modify.own auth org.freedesktop.NetworkManager.settings.modify.hos tname auth org.freedesktop.NetworkManager.settings.modify.glo bal-dns auth org.freedesktop.NetworkManager.reload auth org.freedesktop.NetworkManager.checkpoint-rollback auth org.freedesktop.NetworkManager.enable-disable-statistics no org.freedesktop.NetworkManager.enable-disable-connectivity-check no org.freedesktop.NetworkManager.wifi.scan unknown Sudo output; org.freedesktop.NetworkManager.enable-disable-network yes org.freedesktop.NetworkManager.enable-disable-wifi yes org.freedesktop.NetworkManager.enable-disable-wwan yes org.freedesktop.NetworkManager.enable-disable-wimax yes org.freedesktop.NetworkManager.sleep-wake yes org.freedesktop.NetworkManager.network-control yes org.freedesktop.NetworkManager.wifi.share.protecte d yes org.freedesktop.NetworkManager.wifi.share.open yes org.freedesktop.NetworkManager.settings.modify.sys tem yes org.freedesktop.NetworkManager.settings.modify.own yes org.freedesktop.NetworkManager.settings.modify.hos tname yes org.freedesktop.NetworkManager.settings.modify.glo bal-dns yes org.freedesktop.NetworkManager.reload yes org.freedesktop.NetworkManager.checkpoint-rollback yes org.freedesktop.NetworkManager.enable-disable-statistics yes org.freedesktop.NetworkManager.enable-disable-connectivity-check yes org.freedesktop.NetworkManager.wifi.scan unknown Now it seems to me that I should have more permissions as a user. I have checked what the User output is when you boot into the live ISO and it has all the same permissions as the Sudo output shown above. So my guess would be that this is what myproblem is. How can I fix these permission issues as a workaround while you investigate this bug. Thanks. Jim! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jul 5 19:07:19 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-13 (1361 days ago) InstallationMedia: It IpRoute: default via 192.168.0.2 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.176 metric 600 ProcEnviron: LANGUAGE=en_GB PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-03-14 (113 days ago) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-01-01T15:53:38.227396 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1886336 Title: Network Manager permissions issue Status in network-manager package in Ubuntu: New Bug description: Description:Ubuntu 20.04 LTS Release:20.04 network-manager: Installed: 1.22.10-1ubuntu2.1 Candidate: 1.22.10-1ubuntu2.1 Version table: *** 1.22.10-1ubuntu2.1 500
[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia+Intel & Ubuntu 20.04? (ASUS Laptop)
** Summary changed: - Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) + Second Monitor on HDMI blank screen with Nvidia+Intel & Ubuntu 20.04? (ASUS Laptop) ** No longer affects: mesa-utils (Ubuntu) ** Summary changed: - Second Monitor on HDMI blank screen with Nvidia+Intel & Ubuntu 20.04? (ASUS Laptop) + Second Monitor on HDMI blank screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) ** Summary changed: - Second Monitor on HDMI blank screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) + Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :