[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Upstream found a regression[1] with the new patch in #128, Jeremy will review and re-test the solution in focal before asking for sponsorship. [1] Multiple regressions in multi-user environments since 3.36.2 (#602) · Issues · GNOME / gdm · GitLab - https://gitlab.gnome.org/GNOME/gdm/-/issues/602 ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #602 https://gitlab.gnome.org/GNOME/gdm/-/issues/602 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgr
[Desktop-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
after pacmd --list, when the system has woken from sleep, and now is on the wrong sound output. note that it's not going to the internal sound card at the moment, but the other hdmi device. even though looking at the diff, it thinks the default sync hasn't changed, it actually is now going to the wrong output, and i have to manually switch it to the other hdmi/dp in the sound settings. ** Attachment added: "after.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5406021/+files/after.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 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 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
before pacmd --list, with the input correctly selected as 5.1 surround on HDMI / DisplayPort 2. ** Attachment added: "before.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5406020/+files/before.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 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 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: gdm3 (Ubuntu) Assignee: Alberto Milone (albertomilone) => jeremyszu (os369510) ** Changed in: gdm3 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor:
[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)
The patch was accepted upstream: https://hg.mozilla.org/mozilla- central/rev/5d87a8dae5fe55360890e4ea4ed12135a8e909ed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1893021 Title: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar) Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: When testing firefox 80.0+build2 on xenial (from https://launchpad.net /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm observing that the flash plugin (installed by flashplugin-installer) doesn't work. This appears to affect only xenial, flash is working in the bionic and focal builds. This is what I'm seeing when launching firefox from a terminal: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar This is most likely caused by this recent upstream change: https://phabricator.services.mozilla.com/D84623 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1893021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)
treloar: the update is pending publication by the security team, thanks for your patience. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1893021 Title: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar) Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: When testing firefox 80.0+build2 on xenial (from https://launchpad.net /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm observing that the flash plugin (installed by flashplugin-installer) doesn't work. This appears to affect only xenial, flash is working in the bionic and focal builds. This is what I'm seeing when launching firefox from a terminal: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar This is most likely caused by this recent upstream change: https://phabricator.services.mozilla.com/D84623 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1893021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893139] Re: Firefox 80 blocks flash
*** This bug is a duplicate of bug 1893021 *** https://bugs.launchpad.net/bugs/1893021 No need to do anything, this bug is already marked as duplicate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1893139 Title: Firefox 80 blocks flash Status in firefox package in Ubuntu: New Bug description: Up until last night I was using Firefox 79.0 on Ubuntu 16.04, I got an update to Firefox 80, now I can no longer play games on Kongregate as it seems all flash is blocked. I can still play Kongregate games in Chrome, but as Firefox is my main browser I wish to enable functionality in it once more or rollback to version 79, can anyone inform me how to go back to 79? I cannot even find my way to the repository for 79, only 80 is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1893139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
If not going for marking the subtest flaky as in groovy, I have prepared force-reset-test as alternatives in: - https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390005 - https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390004 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
To match the open packages blocked on this in active releases I added linux-meta for BIonic (thanks Kleber for the hint) and Focal (Thanks Kelsey for the hint). I think all of those had enough of retry-until-success and I'd ask again for how we should proceed there. Masking/Resetting the test via an override would throw away so much other coverage, but lacking other feedback I'll at least proposed the change - maybe this also brings more attention to here. Last 20 focal amd64 upstream (F 5% S 0% B 5% => P 90%/) F.B. systemd-fsckd (F 95% S 0% B 5% => P 0%/) FFBF ppc64el systemd-fsckd (F 65% S 0% B 0% => P 35%/) ...F s390x systemd-fsckd (F 60% S 0% B 0% => P 40%/) bionic amd64 boot-smoke (F 20% S 0% B 0% => P 80%/) ...F.FFF upstream (F 10% S 0% B 0% => P 90%/) ...F..F. systemd-fsckd (F 85% S 0% B 0% => P 15%/) FFF.FF.. They all seem to continue to be heavy on "systemd-fsckd" ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/mutter/-/issues/1402 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I'd updated the debdiff to insert a DEP-3 header. Here is the new debdiff. ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5406013/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+attachment/5405700/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Description changed: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] - Low, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. + Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPRO
[Desktop-packages] [Bug 1893601] Re: 4k not working
Although I can see from 'kernel-modes.txt' that the problem is originating from the kernel. So the Wayland session is unlikely to help. ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid ** No longer affects: xorg-server (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - 4k not working + [i915] 4K modes are missing when connected by HDMI -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1893601 Title: [i915] 4K modes are missing when connected by HDMI (but are shown in the EDID) Status in linux package in Ubuntu: New Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p114 dmi.product.sku: X6F90AA#ABA 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893601] Re: 4k not working
The option is unfortunately a little too hidden... You need to click on your username on the login screen and then use the icon/menu in the bottom right corner of the screen before entering your password. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1893601 Title: [i915] 4K modes are missing when connected by HDMI (but are shown in the EDID) Status in linux package in Ubuntu: New Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p114 dmi.product.sku: X6F90AA#ABA 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
I reported it here: https://gitlab.gnome.org/GNOME/mutter/-/issues/1402 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1402 https://gitlab.gnome.org/GNOME/mutter/-/issues/1402 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1893601] Re: 4k not working
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1893601 Title: 4k not working Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p114 dmi.product.sku: X6F90AA#ABA 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1893601] Re: 4k not working
Hi Daniel, Thank you for your quick response. The details are here. 1. Selecting 'Ubuntu on Wayland' from the login screen. Do you now get 4K modes offered in Settings? - I don't see any Wayland option. The max resolution at Display Settings is 1080p. 2. Run: grep . /sys/class/drm/*/modes > kernel-modes.txt - Attached the file. Thanks and Regards, Vimal Raj (949)310-5218 On Sun, Aug 30, 2020 at 9:05 PM Daniel van Vugt <1893...@bugs.launchpad.net> wrote: > Please try: > > 1. Selecting 'Ubuntu on Wayland' from the login screen. Do you now get > 4K modes offered in Settings? > > 2. Run: > >grep . /sys/class/drm/*/modes > kernel-modes.txt > >and then attach the resulting text file here. > > > ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > ** Also affects: linux (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1893601 > > Title: > 4k not working > > Status in linux package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.8 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Aug 30 20:35:52 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed > ExtraDebuggingInterest: No > GraphicsCard: >Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA > controller]) > Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] > InstallationDate: Installed on 2020-08-28 (2 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver >Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired > Keyboard >Bus 001 Device 004: ID 8087:0aa7 Intel Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: HP 510-p114 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/02/2016 > dmi.bios.vendor: AMI > dmi.bios.version: F.13 > dmi.board.asset.tag: CNV6370S3L > dmi.board.name: 81B4 > dmi.board.vendor: HP > dmi.board.version: 00 > dmi.chassis.asset.tag: CNV6370S3L > dmi.chassis.type: 3 > dmi.chassis.vendor: HP > dmi.modalias: > dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: > dmi.product.family: 103C_53316J G=D > dmi.product.name: 510-p114 > dmi.product.sku: X6F90AA#ABA > 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.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893601/+subscriptions > ** Attachment added: "kernel-modes.txt" https://bugs.launchpad.net/bugs/1893601/+attachment/5405992/+files/kernel-modes.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1893601 Title: 4k not working Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x8
[Desktop-packages] [Bug 1625324] Re: prints pdf files very faintly on EPSON WF-7620. All other types of files print normally
[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 Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1625324 Title: prints pdf files very faintly on EPSON WF-7620. All other types of files print normally Status in cups package in Ubuntu: Expired Bug description: Printer is installed as a network printer. Windows does not print pdf files faintly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 15:06:37 2016 InstallationDate: Installed on 2016-08-09 (41 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1625324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619901] Re: links to local files are always processed as relative paths
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1619901 Title: links to local files are always processed as relative paths Status in evince package in Ubuntu: Expired Bug description: When I create a pdf with a link to an absolute path (e.g. /home/me/link.pdf) and open it in evince it tries to read it as relative to the path of the opened pdf, e.g. if I open /home/me/doc.pdf and click on the preceding link evince tries to open /home/me/home/me/link.pdf. It should open /home/me/link.pdf, otherwise the user is unable to link to files outside the local directory Ubuntu 16.04.1 Evince 3.18.2-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1619901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1753966] Re: apparmor interfers with saving of PDF from evince
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1753966 Title: apparmor interfers with saving of PDF from evince Status in evince package in Ubuntu: Expired Bug description: While trying to save an open PDF from evince, I clicked on the "create folder" button in the save dialog. Apparmor prevented directory creation in the respective directory. Saving within my "home" directory works. I consider this a bug. In my case, all user data resides in a separate data partition. With the current apparmor profiles, saving to this partition is hindered. Syslog contains: Mar 7 10:29:33 xxx kernel: [ 4569.159240] audit: type=1400 audit(1520414973.202:39): apparmor="DENIED" operation="mkdir" profile="/usr/bin/evince" name="x" pid=5393 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 More generally, this seems to apply to a whole set of apparmor profiles that were updated or added recently... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apparmor-profiles (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 7 10:32:37 2018 InstallationDate: Installed on 2017-12-01 (95 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=5c73304c-cd10-4645-99c9-2cf07aa48894 ro nosplash SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1753966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762425] Re: removing keyboard causes a restart
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1762425 Title: removing keyboard causes a restart Status in evince package in Ubuntu: Expired Bug description: removing keyboard,which is being used,in region and language settings causes soft restart. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 19:21:48 2018 InstallationDate: Installed on 2018-04-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1762425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831588] Re: Slow photo saving from Evince to my folder in Nautilus
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1831588 Title: Slow photo saving from Evince to my folder in Nautilus Status in evince package in Ubuntu: Expired Bug description: Details in my video: https://photos.app.goo.gl/gouJpQSqS5QoXqFB6 Characteristics of my laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 128 GB SSD, 4 GB DDR3, Ubuntu 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 12:39:02 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(903, 495)' InstallationDate: Installed on 2019-05-31 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1831588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856479] Re: Document Viewer displays the first page on the right side instead of the left when I select "Dual" in the view menu, despite the PDF being multiple pages (more tha
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1856479 Title: Document Viewer displays the first page on the right side instead of the left when I select "Dual" in the view menu, despite the PDF being multiple pages (more than 2) Status in evince package in Ubuntu: Expired Bug description: When I opened a PDF in Document Viewer, and then set the view mode to "dual", I noticed how the pdf application put the first page on the right side, which does not look as good as putting the page on the left side and page 2 on the right side. Steps to Reproduce: 1. Open the attached PDF in Document Viewer 2. Set the view to Dual 3. Notice the odd number page is to the right when it should be to the left by default. Description: Ubuntu 19.10 Release: 19.10 evince: Installed: 3.34.1-1 Candidate: 3.34.1-1 Version table: *** 3.34.1-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: evince 3.34.1-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 15 14:42:04 2019 InstallationDate: Installed on 2019-11-20 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1856479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763564] Re: ubuntu suddently crash (stuck and nothing work) without reason
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1763564 Title: ubuntu suddently crash (stuck and nothing work) without reason Status in evince package in Ubuntu: Expired Bug description: it crash many time after using for less than 1h ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 10:52:26 2018 InstallationDate: Installed on 2018-04-12 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1763564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755694] Re: evince crashed with SIGSEGV in IA__FcConfigSubstituteWithPat()
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1755694 Title: evince crashed with SIGSEGV in IA__FcConfigSubstituteWithPat() Status in evince package in Ubuntu: Expired Bug description: Crashed while opening a pdf file. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evince 3.27.92-1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 14 12:04:07 2018 ExecutablePath: /usr/bin/evince ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed root=UUID=84d82523-78c3-487a-8680-e0b89e49e2c8 ro GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait acpi=force acpi_enforce_resources=lax vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_IN:en PATH=(custom, user) LANG=en_IN SegvAnalysis: Segfault happened at: 0x7f665f71322c : mov(%rax,%rbx,8),%rax PC (0x7f665f71322c) ok source "(%rax,%rbx,8)" (0x5604cbb5af70) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: evince StacktraceTop: FcConfigSubstituteWithPat () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 pango_itemize_with_base_dir () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 Title: evince crashed with SIGSEGV in FcConfigSubstituteWithPat() UpgradeStatus: Upgraded to bionic on 2018-03-09 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1755694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876491] Re: Ubuntu 20.04 Freezes
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1876491 Title: Ubuntu 20.04 Freezes Status in gdm3 package in Ubuntu: Expired Bug description: I am running into full system freezes while using 20.04, i did a clean install and the issue is still there it will randomly freeze the whole system sometimes the mouse pointer is moving. Ends up hard resetting by holding the power button to restart the pc. I am using AMD Ryzen 5 2500U , and while it boots up it has showed some gpu error while booting ubuntu. Some error realating to kernel is showed , amd gpu kernel like that. So i think its kernel related issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1876491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1690341] Re: evince does not change timestamp of pdf forms
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1690341 Title: evince does not change timestamp of pdf forms Status in evince package in Ubuntu: Expired Bug description: After filling in a pdf-form and "Save a copy ..." the mtime of the filled in form is the same as that of the original form. Observed with: evince 3.10.3 on 14.04 LTS evince 3.18.2 on 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1690341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1661760] Re: Evince does not print pdf.
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1661760 Title: Evince does not print pdf. Status in evince package in Ubuntu: Expired Bug description: The print job is sent but is stopped shortly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 3 20:19:29 2017 InstallationDate: Installed on 2017-02-03 (0 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1661760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785060] Re: Evince cannot open cbr-files based on rar v5
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Expired Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862018] Re: Auto-refresh does not work
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1862018 Title: Auto-refresh does not work Status in evince package in Ubuntu: Expired Bug description: PDFs are not automatically refreshed when they change, e.g. when working on a latex document. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1862018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736583] Re: Evince annotations lost on save
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1736583 Title: Evince annotations lost on save Status in evince package in Ubuntu: Expired Bug description: I used Evince to annotate a ~70 page PDF. Over a few hours I added a handful of annotations to each page. After every 5th page or so I would "Save a Copy" in a new file name (same filename on every save). When I finished editing the document I saved and noticed that the modified time was not updating on the file. When opening the copy, no annotations were present. I tried saving as different file names and the same thing occurred. Then, stupidly, I opened the original file and it closed the file I had open with the hundreds of annotations and now no files have the annotations. My computer is currently at this state. I would really like to be able to recover the annotations if they happen to be in a cache file somewhere. Secondly, this seems to be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732038] Re: evince spams stderr with messages about "Allocating size to EvWindow"
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1732038 Title: evince spams stderr with messages about "Allocating size to EvWindow" Status in evince package in Ubuntu: Expired Bug description: Open a PDF and search it, for instance for the letter 'e'. evince prints numerous error messages to stderr of the form: (evince:30830): Gtk-WARNING **: Allocating size to EvWindow 0x559a7c972f10 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? The more common the search term, the more errors. There is also always one similar error about EvSidebar every time evince starts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 14 09:54:55 2017 InstallationDate: Installed on 2016-12-02 (345 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) KernLog: SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-12 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1732038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760866] Re: evince crashed with SIGSEGV
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1760866 Title: evince crashed with SIGSEGV Status in evince package in Ubuntu: Expired Bug description: Occured after updating Ubuntu 16.04 to Ubuntu 18.04 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evince 3.28.0-1 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 15:48:35 2018 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2017-04-07 (360 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) KernLog: ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=ca55c159-bb62-4dd8-b07c-62b6ef55e404 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x5650d6d0e82d:mov0x38(%r13),%rax PC (0x5650d6d0e82d) ok source "0x38(%r13)" (0x0038) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 start_thread (arg=0x7f24b5b97700) at pthread_create.c:463 Title: evince crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-03-29 (4 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1760866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743244] Re: Keyboard autorepeat does not work after latest update
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1743244 Title: Keyboard autorepeat does not work after latest update Status in evince package in Ubuntu: Expired Bug description: After latest update, keyboard autorepeat has stopped working. I can confirm that the problem is related to the peaq-wmi module having been recently whitelisted as using modprobe to remove peaq-wmi fixes the problem. Workaround: Blacklist the peaq-wmi module I really think the peaq-wmi module should be re-blacklised by default until the bugs can be worked out. Running Xubuntu, version 16.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jan 14 12:56:53 2018 InstallationDate: Installed on 2017-12-18 (27 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893601] Re: 4k not working
Please try: 1. Selecting 'Ubuntu on Wayland' from the login screen. Do you now get 4K modes offered in Settings? 2. Run: grep . /sys/class/drm/*/modes > kernel-modes.txt and then attach the resulting text file here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893601 Title: 4k not working Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p114 dmi.product.sku: X6F90AA#ABA 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893601] Re: 4k not working
Yes it looks like either the kernel driver or Xorg driver is failing to expose 4K modes, which definitely should be available: EDID version: 1.3 Manufacturer: SAM Model 3988 Serial Number 0 Made in week 41 of 2018 Digital display Maximum image size: 70 cm x 39 cm Gamma: 2.20 DPMS levels: Off RGB color display First detailed timing is preferred timing Color Characteristics Red: 0.6513, 0.3398 Green: 0.2998, 0.6230 Blue: 0.1494, 0.0712 White: 0.3125, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48066.667 Hz 4:335.000 kHz 30.240 MHz (Apple) 640x48072.809 Hz 4:337.861 kHz 31.500 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60056.250 Hz 4:335.156 kHz 36.000 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60072.188 Hz 4:348.077 kHz 50.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 832x62474.551 Hz 4:349.726 kHz 57.284 MHz (Apple) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76870.069 Hz 4:356.476 kHz 75.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) 1152x87075.062 Hz 192:145 68.681 kHz 100.000 MHz (Apple) Standard Timings 1152x86475.000 Hz 4:367.500 kHz 108.000 MHz (DMT) 1280x80059.810 Hz 16:10 49.702 kHz 83.500 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1440x90059.887 Hz 16:10 55.935 kHz 106.500 MHz (DMT) 1600x90060.000 Hz 16:960.000 kHz 108.000 MHz (DMT, RB) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) Detailed mode: Clock 594.000 MHz, 697 mm x 392 mm 3840 4016 4104 4400 (176 88 296) 2160 2168 2178 2250 ( 8 10 72) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 135.000 kHz Display Range Limits Monitor ranges (GTF): 24-75 Hz V, 30-135 kHz H, max dotclock 600 MHz Display Product Name: U32R59x Display Product Serial Number: H1AK50 Has 1 extension block Checksum: 0x46 CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 0 native detailed modes 48 bytes of CTA data blocks Video Data Block 3840x2160 60.000 Hz 16:9 135.000 kHz 594.000 MHz (VIC 97) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 1920x1080 24.000 Hz 16:927.000 kHz 74.250 MHz (VIC 32) 1920x1080 30.000 Hz 16:933.750 kHz 74.250 MHz (VIC 34) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16) 3840x2160 30.000 Hz 16:967.500 kHz 297.000 MHz (VIC 95) 3840x2160 50.000 Hz 16:9 112.500 kHz 594.000 MHz (VIC 96) 3840x2160 24.000 Hz 16:954.000 kHz 297.000 MHz (VIC 93) 3840x2160 25.000 Hz 16:956.250 kHz 297.000 MHz (VIC 94) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Vendor-Specific Data Block, OUI 0x000c03 (HDMI) Source physical address 1.0.0.0 Supports_AI DC_36bit DC_30bit DC_Y444 Maximum TMDS clock: 300 MHz Extended HDMI video details: HDMI VICs: 3840x2160 30.000 Hz 16:967.500 kHz 297.000 MHz (HDMI VIC 1) 3840x2160 25.000 Hz 16:956.250 kHz 297.000 MHz (HDMI VIC 2) 3840x2160 24.000 Hz 16:954.000 kHz 297.000 MHz (HDMI VIC 3) Vendor-Specific Data Block, OUI 0xc45dd8 (HDMI Forum) Version: 1 Maximum TMDS Character Rate: 600 MHz SCDC Present Supports 12-bits/component Deep Color 4:2:0 Pixel Encoding Supports 10-bits/component Deep Color 4:2:0 Pixel Encoding Extended tag: YCbCr 4:2:0 Capability Map Data Block 3840x2160 60.000 Hz 16:9 135.000 kHz 594.000 MHz (VIC 97) 3840x2160 50.000 Hz 16:9 112.500 kHz 594.000 MHz (VIC 96) Detailed mode: Clock 148.500 MHz, 697 mm x 392 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Detailed mode: Clock 148.500 MHz, 697 mm x 392 mm 1920 2448 2492 2640 (528 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
hey guys there is a new thread on official lenovo forum about this. let's make them hear our voice! https://forums.lenovo.com/t5/Gaming-Laptops/Lenovo-Legion-5-15ARH05 -Touchpad-not-working-in-any-Linux/m-p/5035512 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5
[Desktop-packages] [Bug 1893601] [NEW] 4k not working
Public bug reported: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p114 dmi.product.sku: X6F90AA#ABA 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893601 Title: 4k not working Status in xorg package in Ubuntu: New Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/201
[Desktop-packages] [Bug 1892973] Re: gnome-session fails, and fails, and fails yet again
Thanks. This appears to be an Nvidia hardware or driver fault. Since this is the first time I've ever seen this (other Nvidia users don't seem to encounter the same issue) I would suggest the simplest solution would be to change the graphics card. Otherwise you will need to seek support from Nvidia themselves. The recurring problems are: Aug 28 09:42:35 greystone /usr/lib/gdm3/gdm-x-session[2279]: (WW) NVIDIA(0): WAIT (2-S, 17, 0x00e4, 0x3fb8, 0x4a1c) Aug 28 09:42:42 greystone /usr/lib/gdm3/gdm-x-session[2279]: (WW) NVIDIA(0): WAIT (1-S, 17, 0x00e4, 0x3fb8, 0x4a1c) Aug 28 09:42:45 greystone /usr/lib/gdm3/gdm-x-session[2279]: (WW) NVIDIA(0): WAIT (2-S, 17, 0x00e4, 0x3fb8, 0x4a1c) and Aug 28 09:08:05 greystone /usr/lib/gdm3/gdm-x-session[1681]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x09a8, 0x1f44) Aug 28 09:08:12 greystone /usr/lib/gdm3/gdm-x-session[1681]: (EE) NVIDIA(GPU-0): WAIT (1, 8, 0x8000, 0x09a8, 0x1f44) Aug 28 09:08:19 greystone kernel: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x); continuing. Aug 28 09:08:33 greystone kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x917d:0:0:954 Aug 28 09:08:44 greystone /usr/lib/gdm3/gdm-x-session[1681]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x09a8, 0x1f4c) Aug 28 09:08:51 greystone /usr/lib/gdm3/gdm-x-session[1681]: (EE) NVIDIA(GPU-0): WAIT (1, 8, 0x8000, 0x09a8, 0x1f4c) Aug 28 09:10:03 greystone kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x917d:0:0:954 Aug 28 09:12:54 greystone rsyslogd[1394]: -- MARK -- Aug 28 09:13:04 greystone kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x917d:0:0:954 Aug 28 09:16:05 greystone kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x917d:0:0:954 ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gnome-session fails, and fails, and fails yet again + [nvidia] Repeated screen freezes with GeForce GT 640 (GK107) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892973 Title: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107) Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily wo
[Desktop-packages] [Bug 1893572] Re: this webm video makes Totem's window flicker
It looks like your graphics driver is probably relevant because with an Intel GPU and the same software the problem does not occur. ** Tags added: focal nvidia ** Summary changed: - this webm video makes Totem's window flicker + Transparent pixels are rendered incorrectly by Totem (leave garbage) on the Nvidia driver. ** Changed in: totem (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1893572 Title: Transparent pixels are rendered incorrectly by Totem (leave garbage) on the Nvidia driver. Status in totem package in Ubuntu: New Bug description: The attached webm video causes rendering bugs on my desktop when opened with the Totem video player. Ubuntu 20.04.1 LTS totem 3.34.1 graphics card: Geforce GTX 1050 Ti video driver: proprietary, nvidia-driver-440 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1893572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893520] Re: screen auto scroll
Please attach a video of the issue so we can see what you mean. Please also tell us if the problem affects all apps or only some. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893520 Title: screen auto scroll Status in Ubuntu: Incomplete Bug description: screen auto scroll , mouse is ok. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Sat Aug 29 19:58:28 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-115-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1777 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard 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 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 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: Wed Aug 26 19:22:07 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893568] Re: Screen brightness missing
Please tell us the model of machine this is. Please also tell us what files, if any, you can find in /sys/class/backlight/ ** Package changed: gnome-control-center (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1893568 Title: Screen brightness missing Status in linux package in Ubuntu: Incomplete Bug description: gnome-control-center - power - Screen brightness is missing. also on top bar Screen brightness control appears but does nothing. the problem does not happen on same PC, different partition with Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 19:47:23 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893509] Re: llvmpipe instead of intel graphics or amd graphics
** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893509 Title: llvmpipe instead of intel graphics or amd graphics Status in Ubuntu: Invalid Bug description: I dont see my monitor detected in monitor settings. I see duplicated display with low res. I have intel integrated and amd radeon graphics. In the inxi -G i see those cards, but the driver says : N/A in the about computer - the graphics is llvmpipe Something is totally wrong, please help! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Sat Aug 29 14:45:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c] InstallationDate: Installed on 2020-06-12 (77 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20351 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b6c37141-5b45-4f4d-8eec-c4e3187dcf66 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893509] Re: llvmpipe instead of intel graphics or amd graphics
You have disabled the graphics drivers with the 'nomodeset' kernel parameter. Please remove that from /etc/default/grub and then run: sudo update-grub and reboot. If then problem persists after that then please open a new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893509 Title: llvmpipe instead of intel graphics or amd graphics Status in xorg package in Ubuntu: New Bug description: I dont see my monitor detected in monitor settings. I see duplicated display with low res. I have intel integrated and amd radeon graphics. In the inxi -G i see those cards, but the driver says : N/A in the about computer - the graphics is llvmpipe Something is totally wrong, please help! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Sat Aug 29 14:45:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c] InstallationDate: Installed on 2020-06-12 (77 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20351 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b6c37141-5b45-4f4d-8eec-c4e3187dcf66 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893478] Re: Wireless mouse not working
When the mouse is *not* working please run: lsusb > lsusb.txt journalctl -b0 > journal.txt and then attach the resulting text files here. ** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1893478 Title: Wireless mouse not working Status in xorg-server package in Ubuntu: Incomplete Bug description: This might be link to gdm3 Running Ubuntu 20.04.1 Wireless mouse stop working after fresh install of Ubuntu 20.04 and after upgrade to 20.04 on another computer. The usb dongle is detected according to lsusb Bus 001 Device 023: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse When booting if I select recovery mode and then choose resume, everything works fine for this session, but as soon as I reboot then mouse stop working again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 28 15:30:34 2020 InstallationDate: Installed on 2020-05-15 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2020-08-28T11:40:26.503109 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1893478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
Rocko, Please report the issue to the developers at either: https://gitlab.gnome.org/GNOME/mutter/-/issues https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues and then tell us the new issue ID(s). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Status in ubuntu-meta source package in Focal: Fix Committed Status in base-files source package in Groovy: Fix Released Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the motd-news-config package when it is installed, otherwise this SRU would jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's configure case. b) /e/d/motd-news config file was *removed* while it belonged to base-files. In such a case, a normal upgrade of the package (base-files in this example) would not reinstate the file. Much less this upgrade here, which has an explicit rm_conffile maintscript-helper for it. But the motd-news-config package that could be installed in the transaction would place the default config file back, and the default is ENABLED=1. Thus, a system that had motd-news disabled via removing the config file would now have it re-enabled after the upgrade. This was trickier to handle, and we do it in base-files's postinst and motd-news-config's postinst. The drawback is th
[Desktop-packages] [Bug 1882023] Re: Notifications are pointlessly truncated even on ultrawide monitors
This appears to be a duplicate of bug 1871868. Is it still happening? ** Changed in: gnome-shell (Ubuntu) Status: Expired => New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors Status in gnome-shell package in Ubuntu: Incomplete Bug description: I tried to use ubuntu-bug -w to identify the component for this bug by clicking on a notification, but it failed with "xprop failed to determine process ID of the window". Sorry. The bug is that notifications of adding/removing icons to Favorites in the taskbar, are truncated for no good reason. I have a dual monitor setup ridiculous amounts of horizontal space, yet the notification is fixed size - which is fine, if it wrapped the text inside it. But it doesn't. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (109 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885393] Re: Dark theme
You need to install the 'user-theme' extension, which is part of this package: sudo apt install gnome-shell-extensions ** Changed in: gnome-control-center (Ubuntu) Status: Expired => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1885393 Title: Dark theme Status in gnome-control-center package in Ubuntu: Invalid Bug description: Je n'arrive pas à mettre le dark theme avec l'onglet apparence, et je ne peut pas changer le theme du shell (pour yaru-dark) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 20:35:00 2020 InstallationDate: Installed on 2019-12-23 (187 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-06-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1885393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer
Looks like it is a kernel driver's problem. Could you install the 18.04's kernel under 20.04 to test? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1887210 Title: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing the same issue with the same device described in this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1267866/comments/26 The device works as expected with Windows 10 and macOS no drivers required. However, the device is not an option from Ubuntu's sound settings. It is visible in alsamixer, however, it crashes immediately upon selection with 'cannot load mixer controls: Broken pipe'. Here's some more debug information. Let me know if there is anymore I can provide or feel free to redirect me if there is another place this is better reported. Device: Schiit Audio Fulla 3 USB DAC/AMP Kernel version: 5.4.0-40-generic Ubuntu version: 20.04 Alsa debug output: http://alsa- project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb `dmesg -w` output upon re-plugging in the device: [ 895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd [ 895.739125] usb 3-2.3: New USB device found, idVendor=30be, idProduct=0100, bcdDevice= 1.02 [ 895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 895.739131] usb 3-2.3: Product: I'm Fulla Schiit [ 895.739133] usb 3-2.3: Manufacturer: Schiit Audio [ 896.076914] input: Schiit Audio I'm Fulla Schiit as /devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20 [ 896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3 [ 896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893567] Re: Login name ellipsis/dot-dot-dot in GDM
I'm thinking this could be the result of bug 1892521. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1893567 Title: Login name ellipsis/dot-dot-dot in GDM Status in gnome-shell package in Ubuntu: Incomplete Bug description: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893561] Re: font size
*** This bug is a duplicate of bug 1892440 *** https://bugs.launchpad.net/bugs/1892440 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1892440, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1892440 Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893561 Title: font size Status in xorg package in Ubuntu: New Bug description: Hi, everytime i turn on my pc (connected via HDMI to an AV-ampli sorround system) i have to set the text size to "large" then again "normal" to see the text above the application logo or in the main bar; if not the text are extremely tiny and can't be read. Sorry for my english. Have a good day. Best regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 17:16:35 2020 DistUpgraded: 2020-05-11 23:30:24,176 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed nvidia, 390.138, 5.4.0-42-generic, x86_64: installed nvidia, 390.138, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Point of View BV GF106 [GeForce GTS 450] [1acc:45a1] InstallationDate: Installed on 2020-05-11 (110 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=18184fdf-eea7-4e9d-bf94-7262aee7e822 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-11 (110 days ago) dmi.bios.date: 06/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd06/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLE:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: To be filled by O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893567] Re: Login name ellipsis/dot-dot-dot in GDM
This is probably the result of one of the font size bugs. Have you noticed shell font sizes changed in the past week or two? ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1893567 Title: Login name ellipsis/dot-dot-dot in GDM Status in gnome-shell package in Ubuntu: Incomplete Bug description: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893567] Re: Login name ellipsis/dot-dot-dot in GDM
Reassigned to gnome-shell, since that provides the login screen GUI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1893567 Title: Login name ellipsis/dot-dot-dot in GDM Status in gnome-shell package in Ubuntu: Incomplete Bug description: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726516] Re: no progress bar while copying files
The bug is still present Ubuntu 20.04. When copying files to an external SSD, no progress bar appears, and it misleads me to disconnect the SDD before copying is finished. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726516 Title: no progress bar while copying files Status in nautilus package in Ubuntu: Confirmed Bug description: while copying files, it does not show progress or any copy dialogue at all. also there is no option to create new file while right clicking ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 23:08:22 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Coci, 9 months is not old. And you should be able to change the title/description of this bug if you can think of something better. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425972] Re: Firefox no longer supports -remote parameter
** Changed in: emacs24 (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1425972
Title:
Firefox no longer supports -remote parameter
Status in GNU Emacs:
Unknown
Status in Exo:
Fix Released
Status in Mozilla Firefox:
Fix Released
Status in Python:
New
Status in emacs24 package in Ubuntu:
Fix Released
Status in exo package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in emacs24 source package in Trusty:
Won't Fix
Status in exo source package in Trusty:
Fix Released
Status in firefox source package in Trusty:
Fix Released
Status in emacs24 source package in Utopic:
Won't Fix
Status in exo source package in Utopic:
Won't Fix
Status in firefox source package in Utopic:
Fix Released
Status in exo package in Debian:
Fix Released
Bug description:
[Impact]
As of Firefox version 36, the -remote commandline parameter was dropped.
This parameter is used in versions of exo prior to 0.10.3. Because of this,
opening any URLs via exo-open will cause a new firefox window to launch at the
home screen.
As reported, this affects the terminal, ubuntu-bug, xchat, and
numerous other applications.
[Test Case]
1. Set Firefox as the default web browser in "Preferred Applications".
2. From a terminal, type the following:
exo-open "http://www.xfce.org";
Expected: Firefox opens at http://www.xfce.org
Actual: Firefox opens at the home page.
[Regression Potential]
No regressions by this change. This fixes the application call to correctly
open URLs.
---
[Original Report]
When I click a link from an email it does not work any more.
Instead of opening the link in a new tab, Firefox opens a new empty
window and does not follow the link.
If I change the default browser for my desktop from Firefox to Chrome,
then Chrome can open the link fine.
I have started seeing this today since firefox was upgraded from v35
to 36.
My email client is Mozilla thunderbird at the latest stable version.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 36.0+build2-0ubuntu0.14.10.4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpottage 3729 F pulseaudio
BuildID: 20150224133805
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Feb 26 14:30:41 2015
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2013-07-02 (604 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64
(20130423.1)
IpRoute:
default via 192.168.1.254 dev eth0 proto static
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric
1
MostRecentCrashID: bp-86a16931-63d2-435e-8324-421212140304
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so
(browser-plugin-libreoffice)
Java(TM) Plug-in 11.25.2 -
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=36.0/20150224133805 (In use)
RelatedPackageVersions: browser-plugin-libreoffice 1:4.3.3-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-86a16931-63d2-435e-8324-421212140304
UpgradeStatus: Upgraded to utopic on 2014-10-29 (119 days ago)
dmi.bios.date: 11/23/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0XR1GT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnVostro270:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 270
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/1425972/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 353877] Re: FF doesn't render the properties and the styles of tags
** Changed in: firefox-3.0 (Ubuntu) Status: Triaged => Won't Fix ** Package changed: firefox-3.0 (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/353877 Title: FF doesn't render the properties and the styles of tags Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Won't Fix Bug description: Binary package hint: firefox-3.0 Accordingly to the standard (http://www.w3.org/TR/html401/index/attributes.html), both the "width" and the "align" attributes can be defined into a tag. After all, this is one of the reasons why the tag exists at all: to define properties related to columns. What instead happens with Firefox 3 is that the "width" property gets honoured and rendered, while the "align" is not. Disappointingly, Microsoft Internet Explorer v7 does it right! ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0.8+nobinonly-0ubuntu0.8.10.2 ProcEnviron: LC_COLLATE=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.27-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/353877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 18995] Re: Firefox should use the GNOME application chooser
** No longer affects: iceweasel (Debian) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/18995 Title: Firefox should use the GNOME application chooser Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Bug description: When choosing to open a file in Firefox, an "Open With" dialog appears. You can choose to save the file or open it with a program from the list. However, if the desired program to open the file with is NOT listed, the user must navigate the filesystem to /usr/bin (or wherever) and select the appropriate program. A more user-friendly way would be to list all of the known programs installed that are available to open files with, and then have an "Other..." or "Advanced..." button for the user who would rather navigate the filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/18995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl
Please plug in the headphone, then run alsa-info.sh and upload the alsa- info.txt BTW, what do you mean "Sound works for a while, then breaks"? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893566 Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl Status in alsa-driver package in Ubuntu: New Bug description: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 353877] [NEW] FF doesn't render the properties and the styles of tags
You have been subscribed to a public bug: Binary package hint: firefox-3.0 Accordingly to the standard (http://www.w3.org/TR/html401/index/attributes.html), both the "width" and the "align" attributes can be defined into a tag. After all, this is one of the reasons why the tag exists at all: to define properties related to columns. What instead happens with Firefox 3 is that the "width" property gets honoured and rendered, while the "align" is not. Disappointingly, Microsoft Internet Explorer v7 does it right! ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0.8+nobinonly-0ubuntu0.8.10.2 ProcEnviron: LC_COLLATE=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.27-14-generic x86_64 ** Affects: firefox Importance: Medium Status: Won't Fix ** Affects: firefox (Ubuntu) Importance: Medium Status: Won't Fix ** Tags: apport-bug -- FF doesn't render the properties and the styles of tags https://bugs.launchpad.net/bugs/353877 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working
apport information ** Tags added: apport-collected groovy third-party-packages ** Description changed: - The refered key combinations are no longer working on my desktop. The - first one refers to opening the terminal. And the second one should work - in combination with F2 or F3 or some other similars for incresing the - volumen, or modifying brightness. + The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu45 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2020-08-05 (25 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: gnome-terminal 3.36.2-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + Tags: third-party-packages groovy + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1893579/+attachment/5405955/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working Status in gnome-terminal package in Ubuntu: New Bug description: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-05 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-terminal 3.36.2-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: third-party-packages groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893579] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1893579/+attachment/5405956/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working Status in gnome-terminal package in Ubuntu: New Bug description: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-05 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-terminal 3.36.2-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: third-party-packages groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893579] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1893579/+attachment/5405957/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working Status in gnome-terminal package in Ubuntu: New Bug description: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-05 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-terminal 3.36.2-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: third-party-packages groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1893579 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working Status in gnome-terminal package in Ubuntu: New Bug description: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893582] Re: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: sane-backends (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1893582 Title: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in sane-backends package in Ubuntu: Invalid Bug description: package instaLL ERROR ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 30 18:48:34 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-08-27 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: sane-backends Title: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1893582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer
I am able to view the device in Sound Settings, but when it attempts to play any audio, it crashes immediately. In my case I am behind a KVM, but my Windows device and my Ubuntu 18.04 server work perfectly, only my 20.04 desktop crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1887210 Title: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing the same issue with the same device described in this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1267866/comments/26 The device works as expected with Windows 10 and macOS no drivers required. However, the device is not an option from Ubuntu's sound settings. It is visible in alsamixer, however, it crashes immediately upon selection with 'cannot load mixer controls: Broken pipe'. Here's some more debug information. Let me know if there is anymore I can provide or feel free to redirect me if there is another place this is better reported. Device: Schiit Audio Fulla 3 USB DAC/AMP Kernel version: 5.4.0-40-generic Ubuntu version: 20.04 Alsa debug output: http://alsa- project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb `dmesg -w` output upon re-plugging in the device: [ 895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd [ 895.739125] usb 3-2.3: New USB device found, idVendor=30be, idProduct=0100, bcdDevice= 1.02 [ 895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 895.739131] usb 3-2.3: Product: I'm Fulla Schiit [ 895.739133] usb 3-2.3: Manufacturer: Schiit Audio [ 896.076914] input: Schiit Audio I'm Fulla Schiit as /devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20 [ 896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3 [ 896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1887210 Title: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing the same issue with the same device described in this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1267866/comments/26 The device works as expected with Windows 10 and macOS no drivers required. However, the device is not an option from Ubuntu's sound settings. It is visible in alsamixer, however, it crashes immediately upon selection with 'cannot load mixer controls: Broken pipe'. Here's some more debug information. Let me know if there is anymore I can provide or feel free to redirect me if there is another place this is better reported. Device: Schiit Audio Fulla 3 USB DAC/AMP Kernel version: 5.4.0-40-generic Ubuntu version: 20.04 Alsa debug output: http://alsa- project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb `dmesg -w` output upon re-plugging in the device: [ 895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd [ 895.739125] usb 3-2.3: New USB device found, idVendor=30be, idProduct=0100, bcdDevice= 1.02 [ 895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 895.739131] usb 3-2.3: Product: I'm Fulla Schiit [ 895.739133] usb 3-2.3: Manufacturer: Schiit Audio [ 896.076914] input: Schiit Audio I'm Fulla Schiit as /devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20 [ 896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3 [ 896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893582] Re: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1893582 Title: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in sane-backends package in Ubuntu: New Bug description: package instaLL ERROR ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 30 18:48:34 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-08-27 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: sane-backends Title: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1893582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893582] [NEW] package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: package instaLL ERROR ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 30 18:48:34 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-08-27 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: sane-backends Title: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1893582 Title: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in sane-backends package in Ubuntu: New Bug description: package instaLL ERROR ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 30 18:48:34 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-08-27 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: sane-backends Title: package libsane 1.0.29-0ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1893582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893579] [NEW] Ctrl + Alt + T and Fn keys not working
Public bug reported: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working Status in gnome-terminal package in Ubuntu: New Bug description: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893572] Re: this webm video makes Totem's window flicker
The problem actually seems to occur with any video that contains transparent pixels. Here is for example a VP8-encoded fully transparent video with which I can reproduce the problem. The video displays perfectly fine in vlc, mpv, and firefox (the transparent pixels are simply displayed in black). ** Attachment added: "transparent-vp8.webm" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1893572/+attachment/5405893/+files/transparent-vp8.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1893572 Title: this webm video makes Totem's window flicker Status in totem package in Ubuntu: New Bug description: The attached webm video causes rendering bugs on my desktop when opened with the Totem video player. Ubuntu 20.04.1 LTS totem 3.34.1 graphics card: Geforce GTX 1050 Ti video driver: proprietary, nvidia-driver-440 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1893572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893572] Re: this webm video makes Totem's window flicker
This is what the bug looks like. The bug does not appear on screenshots, so I filmed my screen. ** Attachment added: "screen_capture.mp4" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1893572/+attachment/5405892/+files/screen_capture.mp4 ** Package changed: compiz (Ubuntu) => totem (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1893572 Title: this webm video makes Totem's window flicker Status in totem package in Ubuntu: New Bug description: The attached webm video causes rendering bugs on my desktop when opened with the Totem video player. Ubuntu 20.04.1 LTS totem 3.34.1 graphics card: Geforce GTX 1050 Ti video driver: proprietary, nvidia-driver-440 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1893572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893572] [NEW] this webm video makes Totem's window flicker
You have been subscribed to a public bug: The attached webm video causes rendering bugs on my desktop when opened with the Totem video player. Ubuntu 20.04.1 LTS totem 3.34.1 graphics card: Geforce GTX 1050 Ti video driver: proprietary, nvidia-driver-440 ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- this webm video makes Totem's window flicker https://bugs.launchpad.net/bugs/1893572 You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873429] Re: Problem with printing in 20.04 version
I downloaded from the espson support site https://download.ebz.epson.net/dsc/search/01/search/?OSC=LX the latest drive epson-printer-utility_1.1.1-1lsb3.2_amd64.deb installed new printer and it worked! Hope this help... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1873429 Title: Problem with printing in 20.04 version Status in cups package in Ubuntu: Incomplete Bug description: In previous 19.10 my Epson Stylus CX3600 both prints & scans fine. In 20.04 it scans fine, but in print mode the process banners show the job is sent to the printer, then printing is complete. However there is no print output. I reinstalled the Epson print drivers but without success. I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the printing issue is solved. The Epson is recognised and my documents print and scan fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 10:59:10 2020 InstallationDate: Installed on 2019-12-10 (128 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1873429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893568] [NEW] Screen brightness missing
Public bug reported: gnome-control-center - power - Screen brightness is missing. also on top bar Screen brightness control appears but does nothing. the problem does not happen on same PC, different partition with Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 19:47:23 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Screenshot from 2020-08-30 19-57-00.png" https://bugs.launchpad.net/bugs/1893568/+attachment/5405848/+files/Screenshot%20from%202020-08-30%2019-57-00.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1893568 Title: Screen brightness missing Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center - power - Screen brightness is missing. also on top bar Screen brightness control appears but does nothing. the problem does not happen on same PC, different partition with Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 19:47:23 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1893568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893567] [NEW] Login name ellipsis/dot-dot-dot in GDM
Public bug reported: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: ellipsis focal gdm login ** Attachment added: "gdm_username_bug.png" https://bugs.launchpad.net/bugs/1893567/+attachment/5405847/+files/gdm_username_bug.png ** Description changed: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. - GDM here is version 3.34.1-1ubuntu1. No changes to its configuration - were made. + GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No + changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. ** Package changed: alsa-driver (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893567 Title: Login name ellipsis/dot-dot-dot in GDM Status in gdm3 package in Ubuntu: New Bug description: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1893567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873429] Re: Problem with printing in 20.04 version
Same problem to me. EPSON BX305F I scans without problems. I tried to reinstall as new printer and to update the driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1873429 Title: Problem with printing in 20.04 version Status in cups package in Ubuntu: Incomplete Bug description: In previous 19.10 my Epson Stylus CX3600 both prints & scans fine. In 20.04 it scans fine, but in print mode the process banners show the job is sent to the printer, then printing is complete. However there is no print output. I reinstalled the Epson print drivers but without success. I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the printing issue is solved. The Epson is recognised and my documents print and scan fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 10:59:10 2020 InstallationDate: Installed on 2019-12-10 (128 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1873429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893139] Re: Firefox 80 blocks flash
*** This bug is a duplicate of bug 1893021 *** https://bugs.launchpad.net/bugs/1893021 How do I close out a thread that someone has worked upon because this is now a duplicate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1893139 Title: Firefox 80 blocks flash Status in firefox package in Ubuntu: New Bug description: Up until last night I was using Firefox 79.0 on Ubuntu 16.04, I got an update to Firefox 80, now I can no longer play games on Kongregate as it seems all flash is blocked. I can still play Kongregate games in Chrome, but as Firefox is my main browser I wish to enable functionality in it once more or rollback to version 79, can anyone inform me how to go back to 79? I cannot even find my way to the repository for 79, only 80 is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1893139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)
I've received no update thus far, so I tried a re-install and still have no flash in firefox. I am on Ubuntu 16.04.7 LTS Xenial x86_64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1893021 Title: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar) Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: When testing firefox 80.0+build2 on xenial (from https://launchpad.net /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm observing that the flash plugin (installed by flashplugin-installer) doesn't work. This appears to affect only xenial, flash is working in the bionic and focal builds. This is what I'm seeing when launching firefox from a terminal: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar This is most likely caused by this recent upstream change: https://phabricator.services.mozilla.com/D84623 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1893021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893566] [NEW] [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl
Public bug reported: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893566 Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl Status in alsa-driver package in Ubuntu: New Bug description: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International C
[Desktop-packages] [Bug 1893469] Re: Missing pdfnup and other scripts
According to https://github.com/DavidFirth/pdfjam#-wrapper-scripts-no- longer-included-here pdfnup and other scripts got integrated into pdfjam directly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1893469 Title: Missing pdfnup and other scripts Status in texlive-extra package in Ubuntu: New Bug description: texlive-extra package is supposed to provide several scripts in /usr/share/texlive/texmf-dist/scripts/pdfjam/, including pdfnup, pdfnpun, pdfbook, etc. However, the only script present is pdfjam. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: texlive-extra-utils 2019.202000218-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Aug 28 10:31:12 2020 InstallationDate: Installed on 2020-08-04 (23 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-extra UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1893469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893469] Re: Missing pdfnup and other scripts
I can confirm this! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1893469 Title: Missing pdfnup and other scripts Status in texlive-extra package in Ubuntu: New Bug description: texlive-extra package is supposed to provide several scripts in /usr/share/texlive/texmf-dist/scripts/pdfjam/, including pdfnup, pdfnpun, pdfbook, etc. However, the only script present is pdfjam. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: texlive-extra-utils 2019.202000218-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Aug 28 10:31:12 2020 InstallationDate: Installed on 2020-08-04 (23 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-extra UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1893469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893562] [NEW] Second equal USB card reader not detected
Public bug reported: On Ubuntu 18.04.5 LTS, gnome-disks 3.28.3. Two exactly equal USB card readers ( 05e3:0749 genesys logic ) are inserted, each containing a formatted SD card, each with a single partition. Both disk partitions are correctly assigned devices on insertion. Only whichever adapter is inserted first automounts (as checked by mount) and only that adapter is listed in Gnome Disks. Both partitions names are listed in the gnome Places menu. After mounting the second partition via the Places menu, still only the first adapter is listed in Gnome Disks. The error occurs with NTFS, FAT or ext4 SD card partitions. This should be pretty easy to track down, but I can run more tests if required. Cheers! ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1893562 Title: Second equal USB card reader not detected Status in gnome-disk-utility package in Ubuntu: New Bug description: On Ubuntu 18.04.5 LTS, gnome-disks 3.28.3. Two exactly equal USB card readers ( 05e3:0749 genesys logic ) are inserted, each containing a formatted SD card, each with a single partition. Both disk partitions are correctly assigned devices on insertion. Only whichever adapter is inserted first automounts (as checked by mount) and only that adapter is listed in Gnome Disks. Both partitions names are listed in the gnome Places menu. After mounting the second partition via the Places menu, still only the first adapter is listed in Gnome Disks. The error occurs with NTFS, FAT or ext4 SD card partitions. This should be pretty easy to track down, but I can run more tests if required. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1893562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893561] [NEW] font size
Public bug reported: Hi, everytime i turn on my pc (connected via HDMI to an AV-ampli sorround system) i have to set the text size to "large" then again "normal" to see the text above the application logo or in the main bar; if not the text are extremely tiny and can't be read. Sorry for my english. Have a good day. Best regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 17:16:35 2020 DistUpgraded: 2020-05-11 23:30:24,176 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed nvidia, 390.138, 5.4.0-42-generic, x86_64: installed nvidia, 390.138, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Point of View BV GF106 [GeForce GTS 450] [1acc:45a1] InstallationDate: Installed on 2020-05-11 (110 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=18184fdf-eea7-4e9d-bf94-7262aee7e822 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-11 (110 days ago) dmi.bios.date: 06/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd06/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLE:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: To be filled by O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal fonts ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893561 Title: font size Status in xorg package in Ubuntu: New Bug description: Hi, everytime i turn on my pc (connected via HDMI to an AV-ampli sorround system) i have to set the text size to "large" then again "normal" to see the text above the application logo or in the main bar; if not the text are extremely tiny and can't be read. Sorry for my english. Have a good day. Best regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 17:16:35 2020
[Desktop-packages] [Bug 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu (updated: including PCIe Bus Error)
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1891407
Title:
[journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
better uninstall ubuntu (updated: including PCIe Bus Error)
Status in network-manager package in Ubuntu:
New
Bug description:
Ubuntu 20.04.01 LTS (newly installed)
(Moved that device from windows 10, didnt had issue in it)
HP 15T-au000 device.
[lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
PCIe Wireless Network Adapter
[lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI
Express Fast Ethernet controller (rev 0a)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet
controller
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe
Wireless Network Adapter
DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be
Wi-Fi key is correct (i can use internet to visit sites, watch videos in
youtube etc) however randomly disconnect and appear window to re-connect
(sometimes constantly disconnect)
No network related change has made (IPv6 disabled through settings)
Only one SSID is in use: Dialog 4G
I ran `journalctl --follow` and below is the log. let me know if
required to provide further details
~Updated~
There also `PCIe Bus Error: severity=Corrected, type=Physical Layer` occur
due that wifi card - RTL8723BE
It usually appear when boot the device (before login screen) and currently i
suppressed that issue by adding `pci=noaer` to grub (alternative pci=nomsi)
I found https://github.com/rtlwifi-linux/rtlwifi_new and
https://github.com/silenoth/rtlwifi_new-extended it contain
'RTL8723BE' however most people had used them due wifi card does not
display or unable connect but i dont have such issue and users have
reported installation issues then didnt consider to put to my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893555] [NEW] gnome-terminal wrapper doesn't wait for the process to exit
Public bug reported: [ Impact ] Gnome terminal has a wrapper to make it compatible with the x-terminal- emulator (i.e. generic xterm implementation), however, while the arguments mapping is correct, when launching `x-terminal-emulator` the control will return to the caller once the terminal has been dbus- activated. This is not expected by x-terminal-emulator, and so breaks the usage of the terminal as fallback when the X11 session failed on startup. [ Test case ] When gnome-terminal is set as x-terminal-emulator (ensure this with update-alternatives --query x-terminal-emulator), launch (from a terminal): x-terminal-emulator -geometry 80x24+0+0 A terminal emulator should open in the top-left corner, and it should stay open until you don't hit Ctrl+C from the launching terminal. [ Regression potential ] None known, possibly a failing launched X session could stay in black screen instead of returning back to gdm promptly. ** Affects: gnome-terminal (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gnome-terminal (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gnome-terminal (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-terminal (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-terminal (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-terminal (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1893555 Title: gnome-terminal wrapper doesn't wait for the process to exit Status in gnome-terminal package in Ubuntu: In Progress Status in gnome-terminal source package in Focal: In Progress Bug description: [ Impact ] Gnome terminal has a wrapper to make it compatible with the x -terminal-emulator (i.e. generic xterm implementation), however, while the arguments mapping is correct, when launching `x-terminal-emulator` the control will return to the caller once the terminal has been dbus- activated. This is not expected by x-terminal-emulator, and so breaks the usage of the terminal as fallback when the X11 session failed on startup. [ Test case ] When gnome-terminal is set as x-terminal-emulator (ensure this with update-alternatives --query x-terminal-emulator), launch (from a terminal): x-terminal-emulator -geometry 80x24+0+0 A terminal emulator should open in the top-left corner, and it should stay open until you don't hit Ctrl+C from the launching terminal. [ Regression potential ] None known, possibly a failing launched X session could stay in black screen instead of returning back to gdm promptly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893555] Re: gnome-terminal wrapper doesn't wait for the process to exit
I can't reproduce the issue. On my system, x-terminal-emulator is set to /usr/bin/gnome- terminal.wrapper. Is it the wrapper you mentioned? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1893555 Title: gnome-terminal wrapper doesn't wait for the process to exit Status in gnome-terminal package in Ubuntu: In Progress Status in gnome-terminal source package in Focal: In Progress Bug description: [ Impact ] Gnome terminal has a wrapper to make it compatible with the x -terminal-emulator (i.e. generic xterm implementation), however, while the arguments mapping is correct, when launching `x-terminal-emulator` the control will return to the caller once the terminal has been dbus- activated. This is not expected by x-terminal-emulator, and so breaks the usage of the terminal as fallback when the X11 session failed on startup. [ Test case ] When gnome-terminal is set as x-terminal-emulator (ensure this with update-alternatives --query x-terminal-emulator), launch (from a terminal): x-terminal-emulator -geometry 80x24+0+0 A terminal emulator should open in the top-left corner, and it should stay open until you don't hit Ctrl+C from the launching terminal. [ Regression potential ] None known, possibly a failing launched X session could stay in black screen instead of returning back to gdm promptly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893552] [NEW] Use im-config on Wayland without uninstalling IBus
Public bug reported: [Impact] In a Wayland session on Ubuntu 20.04 im-config does not work as intended. To be able to use a non-IBus IM framework you basically need to first uninstall ibus (or 'fake uninstall' by renaming /usr/bin/ibus- daemon). This was fixed in im-config 0.45-1, and the proposed upload includes a patch with a cherry picked Debian commit. [Test case] * Install fcitx and fcitx-libpinyin * Open Language Support and switch to fcitx * Reboot and log in to a Wayland session * Open the fcitx preferences and add fcitx-libpinyin * Switch to fcitx-libpinyin and confirm that you can input Chinese [Regression risk] A similar method for making im-config work with Wayland was used in Ubuntu 17.10, which was shipped with Wayland as default. Since the approach has already been used without reported issues, the regression risk now should be low. ** Affects: im-config (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: im-config (Ubuntu Focal) Importance: Low Assignee: Gunnar Hjalmarsson (gunnarhj) Status: New ** Also affects: im-config (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: im-config (Ubuntu Focal) Importance: Undecided => Low ** Changed in: im-config (Ubuntu Focal) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1893552 Title: Use im-config on Wayland without uninstalling IBus Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Focal: New Bug description: [Impact] In a Wayland session on Ubuntu 20.04 im-config does not work as intended. To be able to use a non-IBus IM framework you basically need to first uninstall ibus (or 'fake uninstall' by renaming /usr/bin /ibus-daemon). This was fixed in im-config 0.45-1, and the proposed upload includes a patch with a cherry picked Debian commit. [Test case] * Install fcitx and fcitx-libpinyin * Open Language Support and switch to fcitx * Reboot and log in to a Wayland session * Open the fcitx preferences and add fcitx-libpinyin * Switch to fcitx-libpinyin and confirm that you can input Chinese [Regression risk] A similar method for making im-config work with Wayland was used in Ubuntu 17.10, which was shipped with Wayland as default. Since the approach has already been used without reported issues, the regression risk now should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082110]
(In reply to Justin L from comment #18) > This has to be a mistake. That bug has nothing to do with endnotes. Must have been confused - sorry. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1082110 Title: [Upstream] Endnote placed at end of document is unmovable Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.6.2~rc2-0ubuntu4 Candidate: 1:3.6.2~rc2-0ubuntu4 Version table: *** 1:3.6.2~rc2-0ubuntu4 0 900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.6.2~rc2-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 3) What is expected to happen in Calc is open a blank document -> type example -> click Insert -> Footnote/Endnote... -> under Numbering click radio button Automatic -> under Type click radio button Endnote -> click button OK and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down, as it does in Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit). 4) What happens instead is the Endnote is placed all the way at the bottom of the document, and is not movable via clicking Del on the keyboard. WORKAROUND: Use AbiWord. apt-cache policy abiword abiword: Installed: 2.9.2+svn20120603-8 Candidate: 2.9.2+svn20120603-8 Version table: *** 2.9.2+svn20120603-8 0 500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages 100 /var/lib/dpkg/status Open a blank document -> type example -> click References -> Insert Endnote and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.4-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Thu Nov 22 09:03:21 2012 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1082110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082110]
*** Bug 129036 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1082110 Title: [Upstream] Endnote placed at end of document is unmovable Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.6.2~rc2-0ubuntu4 Candidate: 1:3.6.2~rc2-0ubuntu4 Version table: *** 1:3.6.2~rc2-0ubuntu4 0 900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.6.2~rc2-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 3) What is expected to happen in Calc is open a blank document -> type example -> click Insert -> Footnote/Endnote... -> under Numbering click radio button Automatic -> under Type click radio button Endnote -> click button OK and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down, as it does in Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit). 4) What happens instead is the Endnote is placed all the way at the bottom of the document, and is not movable via clicking Del on the keyboard. WORKAROUND: Use AbiWord. apt-cache policy abiword abiword: Installed: 2.9.2+svn20120603-8 Candidate: 2.9.2+svn20120603-8 Version table: *** 2.9.2+svn20120603-8 0 500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages 100 /var/lib/dpkg/status Open a blank document -> type example -> click References -> Insert Endnote and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.4-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Thu Nov 22 09:03:21 2012 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1082110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882185] Re: Firefox 78 requires nodejs >= 10.21
This bug was fixed in the package nodejs - 12.18.2~dfsg-1ubuntu2 --- nodejs (12.18.2~dfsg-1ubuntu2) groovy; urgency=medium * debian/patches/3f071e3.patch: * debian/patches/1a9c676a141b32483b48884f8cc0330e64c8e17f.patch: - cherry-pick two upstream changes in v8 to fix a testsuite failure on ppc64el for some sha1 calculation errors (LP: #1887144) -- Gianfranco Costamagna Wed, 19 Aug 2020 20:47:23 +0200 ** Changed in: nodejs (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1882185 Title: Firefox 78 requires nodejs >= 10.21 Status in firefox package in Ubuntu: Triaged Status in nodejs package in Ubuntu: Fix Released Bug description: Firefox 78 RC week starts at 22th June 2020 with a bumped nodejs requirement to 10.21 (https://bugzilla.mozilla.org/show_bug.cgi?id=1641863). https://hg.mozilla.org/releases/mozilla-beta/rev/2e5f70995d3a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1882185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893551] [NEW] Let im-config back off if IBus on GNOME desktops
Public bug reported: Note: Quite a few ibus crash bug reports have been marked as duplicates of this bug. If you find that such a bug was not actually addressed through the fix of this bug, please feel free to comment on the bug report and remove the duplicate link. [Impact] GNOME desktops have built-in mechanisms for launching and configuring IBus. However, up to now im-config has overridden GNOME in this respect, resulting in a slightly different command for launching IBus and a few extra environment variables; most importantly GTK_IM_MODULE has been set to "ibus". This was recently changed via im-config 0.45-1 in groovy, where im- config does not do anything in case of IBus on a GNOME desktop. A positive side effect of the change is that the frequency of IBus crashes has been significantly reduced. No deep analysis has been carried out which explains *how* this change prevents IBus crashes. The basis for the conclusion is instead statistics from errors.ubuntu.com. Some relevant links can be found in this discourse topic: https://discourse.ubuntu.com/t/ibus-no-more-gtk-im-module-ibus/17727 [Test case] We have not been able to reproduce the crashes, so a simple test which verifies the fix can't be accomplished. Instead we need to be attentive to possible regressions. * On an Ubuntu desktop, install ibus-libpinyin and ibus-hangul. * Log out and log in again (to an X session). * Enable Intelligent Pinyin and Hangul (from Settings -> Region & Language) * For each of Intelligent Pinyin, Hangul, and the on screen keyboard: - Confirm that inputting works without hassle - Do so on various apps: FF, TB, gedit, LO. [Regression risk] Even if we have done it differently in Ubuntu (and Debian), the GNOME mechanisms we now let replace im-config with respect to IBus is mature code which has been in use for quite some time on other distros. That speaks for a low regression risk. ** Affects: im-config (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: im-config (Ubuntu Focal) Importance: High Assignee: Gunnar Hjalmarsson (gunnarhj) Status: New ** Also affects: im-config (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: im-config (Ubuntu Focal) Importance: Undecided => High ** Changed in: im-config (Ubuntu Focal) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1893551 Title: Let im-config back off if IBus on GNOME desktops Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Focal: New Bug description: Note: Quite a few ibus crash bug reports have been marked as duplicates of this bug. If you find that such a bug was not actually addressed through the fix of this bug, please feel free to comment on the bug report and remove the duplicate link. [Impact] GNOME desktops have built-in mechanisms for launching and configuring IBus. However, up to now im-config has overridden GNOME in this respect, resulting in a slightly different command for launching IBus and a few extra environment variables; most importantly GTK_IM_MODULE has been set to "ibus". This was recently changed via im-config 0.45-1 in groovy, where im- config does not do anything in case of IBus on a GNOME desktop. A positive side effect of the change is that the frequency of IBus crashes has been significantly reduced. No deep analysis has been carried out which explains *how* this change prevents IBus crashes. The basis for the conclusion is instead statistics from errors.ubuntu.com. Some relevant links can be found in this discourse topic: https://discourse.ubuntu.com/t/ibus-no-more-gtk-im-module-ibus/17727 [Test case] We have not been able to reproduce the crashes, so a simple test which verifies the fix can't be accomplished. Instead we need to be attentive to possible regressions. * On an Ubuntu desktop, install ibus-libpinyin and ibus-hangul. * Log out and log in again (to an X session). * Enable Intelligent Pinyin and Hangul (from Settings -> Region & Language) * For each of Intelligent Pinyin, Hangul, and the on screen keyboard: - Confirm that inputting works without hassle - Do so on various apps: FF, TB, gedit, LO. [Regression risk] Even if we have done it differently in Ubuntu (and Debian), the GNOME mechanisms we now let replace im-config with respect to IBus is mature code which has been in use for quite some time on other distros. That speaks for a low regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchp
[Desktop-packages] [Bug 1892373] Re: Firefox crashes on logout
Thanks for following up! ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1892373 Title: Firefox crashes on logout Status in firefox package in Ubuntu: Invalid Bug description: Every time I logout or shutdown the system with firefox open, it will generate a crash report in about:crashes. However, there is no crash dump in /var/crash. I noticed this before I upgraded from 18.04 LTS recently, and at first I thought the crash went away after the upgrade, but sadly it's not the case. I've tested with a fresh new user, with the same result. I'm running Xubuntu 20.04.1 LTS. This may be the same bug as bug #73536 ( Mozilla Bugzilla #336193), but I can't be sure. To reproduce: Open firefox. Logout with firefox window open. login again and check "about:crashes" in firefox. The output of: lsb_release -a; uname -a; apt-cache policy firefox No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal Linux celia 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux firefox: Installed: 79.0+build1-0ubuntu0.20.04.1 Candidate: 79.0+build1-0ubuntu0.20.04.1 Version table: *** 79.0+build1-0ubuntu0.20.04.1 500 500 http://mirror.csclub.uwaterloo.ca/ubuntu focal-updates/main amd64 Packages 500 http://mirror.csclub.uwaterloo.ca/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 75.0+build3-0ubuntu1 500 500 http://mirror.csclub.uwaterloo.ca/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1892373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890939] Re: [snap] The SUID sandbox helper binary was found, but is not configured correctly.
Thanks for following up! ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1890939 Title: [snap] The SUID sandbox helper binary was found, but is not configured correctly. Status in chromium-browser package in Ubuntu: Fix Released Bug description: The chromium snap version 1260 has the wrong mode for chrome-sandbox, as it happened also in bug #1854091: ``` $ /snap/bin/chromium [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken pipe (32) ``` I have reverted it to the previous version (1244) and this one works (and has the right mode for chromium-sandbox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890939] Re: [snap] The SUID sandbox helper binary was found, but is not configured correctly.
The current version (1284) works OK and the SUID bits are back: ``` $ ls -l /snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox -r-sr-xr-x 1 root root 333952 Aug 29 14:43 /snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 09:06 CEST channels: latest/stable:85.0.4183.83 2020-08-29 (1284) 169MB - latest/candidate: 85.0.4183.83 2020-08-29 (1284) 169MB - latest/beta: 85.0.4183.76 2020-08-24 (1271) 167MB - latest/edge: 86.0.4240.8 2020-08-27 (1278) 168MB - installed: 85.0.4183.83(1284) 169MB - ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1890939 Title: [snap] The SUID sandbox helper binary was found, but is not configured correctly. Status in chromium-browser package in Ubuntu: Incomplete Bug description: The chromium snap version 1260 has the wrong mode for chrome-sandbox, as it happened also in bug #1854091: ``` $ /snap/bin/chromium [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken pipe (32) ``` I have reverted it to the previous version (1244) and this one works (and has the right mode for chromium-sandbox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
