[Touch-packages] [Bug 1933796] Re: resume from suspend while connected to power results in roaring fans
confirmed: the fan does NOT come up in full power anymore when waking up from suspend. thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933796 Title: resume from suspend while connected to power results in roaring fans Status in systemd package in Ubuntu: Incomplete Bug description: since upgrade to ubuntu 20.10 my thinkpad x1 carbon gen5 resumes from suspend with a roaring fan. i have to make sure to start the resume while the power cord is not connected, let it wake up fully and only then connect the power cord. this is quite an annoying regression, still persisting in ubuntu 21.04, since there is no way to calm the fan noise except to do a complete shutdown and power on cycle (reboot still keeps the fan at max). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Jun 27 18:20:13 2021 InstallationDate: Installed on 2021-05-10 (48 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 1199:9079 Sierra Wireless, Inc. EM7455 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HR0068GE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=6e4248be-ae78-4e70-a7c0-88bada1c53a8 ro mitigations=off quiet SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR0068GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:br1.24:efr1.17:svnLENOVO:pn20HR0068GE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR0068GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR0068GE dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1933796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933796] Re: resume from suspend while connected to power results in roaring fans
give me a day or two to test it. currently i am actually annoyed with another bug: closing the lid does not trigger hibernation anymore; i have to explicitly choose hibernation from the menu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933796 Title: resume from suspend while connected to power results in roaring fans Status in systemd package in Ubuntu: Incomplete Bug description: since upgrade to ubuntu 20.10 my thinkpad x1 carbon gen5 resumes from suspend with a roaring fan. i have to make sure to start the resume while the power cord is not connected, let it wake up fully and only then connect the power cord. this is quite an annoying regression, still persisting in ubuntu 21.04, since there is no way to calm the fan noise except to do a complete shutdown and power on cycle (reboot still keeps the fan at max). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Jun 27 18:20:13 2021 InstallationDate: Installed on 2021-05-10 (48 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 1199:9079 Sierra Wireless, Inc. EM7455 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HR0068GE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=6e4248be-ae78-4e70-a7c0-88bada1c53a8 ro mitigations=off quiet SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR0068GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:br1.24:efr1.17:svnLENOVO:pn20HR0068GE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR0068GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR0068GE dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1933796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
there has been no progress on this issue, it's the same in ubuntu 21.04. the behavior described in #15 is especially annoying since closing the lid by mistake (while eg carrying it around) and opening it immediately does not cancel the suspend, it comes 30s later no matter what one is currently doing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933796] [NEW] resume from suspend while connected to power results in roaring fans
Public bug reported: since upgrade to ubuntu 20.10 my thinkpad x1 carbon gen5 resumes from suspend with a roaring fan. i have to make sure to start the resume while the power cord is not connected, let it wake up fully and only then connect the power cord. this is quite an annoying regression, still persisting in ubuntu 21.04, since there is no way to calm the fan noise except to do a complete shutdown and power on cycle (reboot still keeps the fan at max). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Jun 27 18:20:13 2021 InstallationDate: Installed on 2021-05-10 (48 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 1199:9079 Sierra Wireless, Inc. EM7455 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HR0068GE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=6e4248be-ae78-4e70-a7c0-88bada1c53a8 ro mitigations=off quiet SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR0068GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:br1.24:efr1.17:svnLENOVO:pn20HR0068GE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR0068GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR0068GE dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933796 Title: resume from suspend while connected to power results in roaring fans Status in systemd package in Ubuntu: New Bug description: since upgrade to ubuntu 20.10 my thinkpad x1 carbon gen5 resumes from suspend with a roaring fan. i have to make sure to start the resume while the power cord is not connected, let it wake up fully and only then connect the power cord. this is quite an annoying regression, still persisting in ubuntu 21.04, since there is no way to calm the fan noise except to do a complete shutdown and power on cycle (reboot still keeps the fan at max). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Jun 27 18:20:13 2021 InstallationDate: Installed on 2021-05-10 (48 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 1199:9079 Sierra Wireless, Inc. EM7455 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HR0068GE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=6e4248be-ae78-4e70-a7c0-88bada1c53a8 ro mitigations=off quiet SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR0068GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17
[Touch-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
there has been no progress on this issue, it's the same in ubuntu 21.04. the behavior described in #15 is especially annoying since closing the lid by mistake (while eg carrying it around) and opening it immediately does not cancel the suspend, it comes 30s later no matter what one is currently doing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904616] Re: after upgrade analog audio output vanished
*** This bug is a duplicate of bug 1897965 *** https://bugs.launchpad.net/bugs/1897965 i confirm that purging pipewire solves the issue. the analog audio output is back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1904616 Title: after upgrade analog audio output vanished Status in pulseaudio package in Ubuntu: New Bug description: after an upgrade from 20.04 to 20.10 the analog audio output vanished. in pavucontrol there is no corresponding profile available for the built-in audio in the configuration tab. additional info: > aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 > pacmd list-cards 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb123 irq 140" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "02c8" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 65, available: no) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo (HDMI 4) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) Output (priority 5700, available: no) output:hdmi-stereo-extra4+input:analog-stereo: Digital Stereo (HDMI 5) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra4: Digital Surround 5.1 (HDMI 5) Output (priority 600, available: no) output:hdmi-surround71-extra4: Digital Surround 7.1 (HDMI 5) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: sinks:
[Touch-packages] [Bug 1904616] Re: after upgrade analog audio output vanished
alsa-info can be found at http://alsa- project.org/db/?f=74fbad0c2c33a8e98de238a5cb713a3acdab9eb6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1904616 Title: after upgrade analog audio output vanished Status in pulseaudio package in Ubuntu: New Bug description: after an upgrade from 20.04 to 20.10 the analog audio output vanished. in pavucontrol there is no corresponding profile available for the built-in audio in the configuration tab. additional info: > aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 > pacmd list-cards 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb123 irq 140" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "02c8" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 65, available: no) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo (HDMI 4) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) Output (priority 5700, available: no) output:hdmi-stereo-extra4+input:analog-stereo: Digital Stereo (HDMI 5) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra4: Digital Surround 5.1 (HDMI 5) Output (priority 600, available: no) output:hdmi-surround71-extra4: Digital Surround 7.1 (HDMI 5) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_00_1f.3.hdmi-stereo/#0: Built-in Audio Digital
[Touch-packages] [Bug 1904616] [NEW] after upgrade analog audio output vanished
Public bug reported: after an upgrade from 20.04 to 20.10 the analog audio output vanished. in pavucontrol there is no corresponding profile available for the built-in audio in the configuration tab. additional info: > aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 > pacmd list-cards 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb123 irq 140" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "02c8" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 65, available: no) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo (HDMI 4) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) Output (priority 5700, available: no) output:hdmi-stereo-extra4+input:analog-stereo: Digital Stereo (HDMI 5) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra4: Digital Surround 5.1 (HDMI 5) Output (priority 600, available: no) output:hdmi-surround71-extra4: Digital Surround 7.1 (HDMI 5) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_00_1f.3.hdmi-stereo/#0: Built-in Audio Digital Stereo (HDMI) sources: alsa_output.pci-_00_1f.3.hdmi-stereo.monitor/#0: Monitor of Built-in Audio Digital Stereo (HDMI) ports: analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" hdmi-output-0: HDMI / DisplayPort
[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
indeed, i get a crash if i click on the following fonts: Bitstream Vera Sans Mono, DejaVu Sans Mono, Inconsolata, MathJax_Vector-Bold, and Terminus. note that in the font chooser these font names appear to be rendered not in their particular typeface but with the default system font so is seems there is the bug still lingering somewhere. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Groovy: Fix Committed Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an upstream commit which fixes it. [Test case] * Install the binaries built from gtk+3.0 in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows regular fonts only. [ Regression risk ] The upstream commit was written explicitly to fix this issue, so the regression risk should be low. Please note that the only affected file is gtk/gtkfontchooserwidget.c, so the scope is very limited which in itself ought to limit the regression risk. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
i tested it after installing libgtk-3-0 libgtk-3-common from proposed. i
can confirm that the gnome-terminal settings custom font now shows only
"ubuntu mono" when "ubuntu" is typed into the search box and therefore
solves the issue.
nevertheless, note that this is still different than what we see in
focal, namely typing "ubuntu" into the search shows ubuntu mono
{regular, italics, bold, bold-italics}. it's probably fine to allow
selecting only the regular font since italics is useless as a terminal
font and bold is used for emphasis anyway...
packages installed: libgtk-3-common (3.24.23-1ubuntu1.1) over
(3.24.23-1ubuntu1), libgtk-3-0:amd64 (3.24.23-1ubuntu1.1) over
(3.24.23-1ubuntu1)
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729
Title:
gnome-terminal font settings show only italic version of ubuntu mono
Status in gtk+3.0 package in Ubuntu:
Fix Committed
Status in gtk+3.0 source package in Groovy:
Fix Committed
Bug description:
[Impact]
When you want to select a monospace font in gnome-terminal's profile
editor, it does not always show the regular font but rather an
arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
upstream commit which fixes it.
[Test case]
* Install the binaries built from gtk+3.0 in groovy-proposed
* Relogin
* Open gnome-terminal -> Preferences and open the window for selecting
a custom font for the profile. Find that it shows regular fonts only.
[ Regression risk ]
The upstream commit was written explicitly to fix this issue, so the
regression risk should be low. Please note that the only affected file
is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
itself ought to limit the regression risk.
[Original description]
trying to change the font in gnome-terminal, only the italics version
of the ubuntu mono font is shown, as can be seen in the attachment. on
the other hand, when changing fonts in the appearance settings, i can
see all variants of the ubuntu fonts...
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-terminal 3.38.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Oct 20 16:56:57 2020
InstallationDate: Installed on 2020-10-20 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
interesting observation: if i close the lid for, say, 1 sec, and then open it again, after similar time delay as observed in the previous comment, my thinkpad goes into suspend although i am working in my desktop (obviously with the lid open). the lid close seems to trigger the suspend which comes 30 seconds later, no matter what... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
similar thing happens with my lenovo thinkpad x1 carbon gen5. the time it takes for suspend is excrutiationgly long. it used to be a couple of seconds, at most, now the wait for the red led on top of "i" in ThinkPad logo seems to be taking for ages to start blinking. the output of the loop (suggested by @arighi above) while true ; do echo $(date) $(cat /proc/acpi/button/lid/LID/state) ; done gives the following: Thu 11 Jun 2020 09:36:44 AM CEST state: open Thu 11 Jun 2020 09:36:45 AM CEST state: open Thu 11 Jun 2020 09:36:46 AM CEST state: open <-- close lid Thu 11 Jun 2020 09:36:47 AM CEST state: open Thu 11 Jun 2020 09:36:48 AM CEST state: open Thu 11 Jun 2020 09:36:49 AM CEST state: closed Thu 11 Jun 2020 09:36:50 AM CEST state: closed Thu 11 Jun 2020 09:36:51 AM CEST state: closed Thu 11 Jun 2020 09:36:52 AM CEST state: closed Thu 11 Jun 2020 09:36:53 AM CEST state: closed Thu 11 Jun 2020 09:36:54 AM CEST state: closed Thu 11 Jun 2020 09:36:55 AM CEST state: closed Thu 11 Jun 2020 09:36:56 AM CEST state: closed Thu 11 Jun 2020 09:36:57 AM CEST state: closed Thu 11 Jun 2020 09:36:58 AM CEST state: closed Thu 11 Jun 2020 09:36:59 AM CEST state: closed Thu 11 Jun 2020 09:37:00 AM CEST state: closed Thu 11 Jun 2020 09:37:01 AM CEST state: closed Thu 11 Jun 2020 09:37:02 AM CEST state: closed Thu 11 Jun 2020 09:37:03 AM CEST state: closed Thu 11 Jun 2020 09:37:04 AM CEST state: closed Thu 11 Jun 2020 09:37:05 AM CEST state: closed Thu 11 Jun 2020 09:37:06 AM CEST state: closed Thu 11 Jun 2020 09:37:07 AM CEST state: closed Thu 11 Jun 2020 09:37:08 AM CEST state: closed Thu 11 Jun 2020 09:37:09 AM CEST state: closed Thu 11 Jun 2020 09:37:10 AM CEST state: closed Thu 11 Jun 2020 09:37:11 AM CEST state: closed Thu 11 Jun 2020 09:37:12 AM CEST state: closed Thu 11 Jun 2020 09:37:13 AM CEST state: closed Thu 11 Jun 2020 09:37:14 AM CEST state: closed Thu 11 Jun 2020 09:37:15 AM CEST state: closed Thu 11 Jun 2020 09:37:16 AM CEST state: closed Thu 11 Jun 2020 09:37:17 AM CEST state: closed Thu 11 Jun 2020 09:37:18 AM CEST state: closed 19 <-- power led starts blinking 20 21 22 23 24 25 26 27 28 <-- open lid 29 Thu 11 Jun 2020 09:37:30 AM CEST state: open Thu 11 Jun 2020 09:37:31 AM CEST state: open Thu 11 Jun 2020 09:37:35 AM CEST state: open <-- ctrl-c while-loop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871185] [NEW] urls in ubuntu-bugs dialog not really clickable
Public bug reported: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "ubuntu-bug-dialog.png" https://bugs.launchpad.net/bugs/1871185/+attachment/5347929/+files/ubuntu-bug-dialog.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1871185 Title: urls in ubuntu-bugs dialog not really clickable Status in apport package in Ubuntu: New Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out
the same bug confirmed also on Acer TravelMate 6492 with Intel GM965/GL960 graphics running Ubuntu 16.04.5 LTS. the kernel command-line option above fixes the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789258 Title: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out Status in libdrm package in Ubuntu: New Bug description: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 0769BJG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 0769BJG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out
the solution proposed in https://bugzilla.redhat.com/show_bug.cgi?id=1534300 and https://bugs.freedesktop.org/show_bug.cgi?id=93782 solved the problem. one should add video=SVIDEO-1:d to the kernel parameters, best in /etc/defaults/grub ** Bug watch added: Red Hat Bugzilla #1534300 https://bugzilla.redhat.com/show_bug.cgi?id=1534300 ** Bug watch added: freedesktop.org Bugzilla #93782 https://bugs.freedesktop.org/show_bug.cgi?id=93782 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789258 Title: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out Status in libdrm package in Ubuntu: New Bug description: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 0769BJG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 0769BJG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out
the situation is the same after an upgrade to 18.10. the graphics freezes for about 25 seconds each time one switches from tty to graphical console or when lightdm/gdm starts. i am attaching the dmesg output where several such freezes can be seen. it's all related to a timeout in blanking the screen. ** Attachment added: "dmesg output containing several drm freezes, see "timeout"" https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789258/+attachment/5203280/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789258 Title: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out Status in libdrm package in Ubuntu: New Bug description: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 0769BJG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 0769BJG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1256561] Re: starting mathematica 9 crashes xserver
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid ** Changed in: xorg (Debian) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1256561 Title: starting mathematica 9 crashes xserver Status in xorg package in Ubuntu: Invalid Status in xorg package in Debian: Invalid Bug description: upon starting mathematica 9.0.1 the x server crashes and a login appears. with ubuntu 13.10 this happens on almost all computers to my disposal, with various video cards/drivers (exception being only one netbook with intel graphics). while on other systems the crash does not leave any trail and the log file does not seem to be closed, on this particular system the Xorg.0.log.old contains the following relevant lines: [ 78030.098] (EE) [ 78030.098] (EE) Backtrace: [ 78030.102] (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x7f195a99a02d] [ 78030.103] (EE) 1: /usr/bin/X (0x7f195a7f8000+0x1a5d99) [0x7f195a99dd99] [ 78030.103] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f19598f8000+0xfbb0) [0x7f1959907bb0] [ 78030.103] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7f1958512000+0x40f8c) [0x7f1958552f8c] [ 78030.103] (EE) 4: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/extensions/libglx.so (0x7f19551a8000+0x44b32) [0x7f19551ecb32] [ 78030.103] (EE) 5: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/extensions/libglx.so (0x7f19551a8000+0x1f677) [0x7f19551c7677] [ 78030.103] (EE) 6: /usr/bin/X (0x7f195a7f8000+0x5500e) [0x7f195a84d00e] [ 78030.103] (EE) 7: /usr/bin/X (0x7f195a7f8000+0x4456a) [0x7f195a83c56a] [ 78030.103] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f1958533de5] [ 78030.103] (EE) 9: /usr/bin/X (0x7f195a7f8000+0x448af) [0x7f195a83c8af] [ 78030.103] (EE) [ 78030.103] (EE) Segmentation fault at address 0x0 [ 78030.104] (EE) Fatal server error: [ 78030.104] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 78030.104] (EE) [ 78030.104] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 78030.104] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 78030.104] (EE) [ 78030.104] (II) AIGLX: Suspending AIGLX clients for VT switch [ 78030.105] (II) fglrx(0): Backup framebuffer data. [ 78030.173] (II) fglrx(0): Backup complete. [ 78030.618] (EE) Server terminated with error (1). Closing log file. the crash most probably occurs when mathematica initializes the gl stuff. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: wl fglrx .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 30 20:56:00 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-13-generic, x86_64: installed fglrx-updates, 13.101, 3.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161b] InstallationDate: Installed on 2013-10-31 (30 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ProBook 6560b MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=de3c16e3-d93d-48f5-9c43-fd9bdc9b778e ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.08 dmi.board.name: 1619 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.08:bd08/26/2011:svnHewlett-Packard:pnHPProBook6560b:pvrAC02:rvnHewlett-Packard:rn1619:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6560b dmi.product.version: AC02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out
uninstalling the xserver-xorg-video-intel did not help. the output of tail -f /var/log/kern.log during the switch from graphics to linux console is in the attachment. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789258/+attachment/5181635/+files/1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789258 Title: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out Status in libdrm package in Ubuntu: New Bug description: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 0769BJG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 0769BJG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789258] [NEW] drm:drm_atomic_helper_wait_for_dependencies flip_done timed out
Public bug reported: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 0769BJG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 0769BJG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "system logs get filled with these timeout error messages" https://bugs.launchpad.net/bugs/1789258/+attachment/5181380/+files/dmesg_errors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789258 Title: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out Status in libdrm package in Ubuntu: New Bug description: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia:
[Touch-packages] [Bug 1527147] Re: list of printers in print dialog jumps fast, hard to select a printer
bump. affects all ubuntus from 15.10 to 17.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1527147 Title: list of printers in print dialog jumps fast, hard to select a printer Status in gtk+3.0 package in Ubuntu: New Bug description: when opening a gtk print dialog (evince, firefox etc), the list of printers is jumping up and down when many printers are listed. i am not sure if this is related to cups reporting different number of printers each time asked or is this some kind of a list sorting problem in gnome when repeated sorting is not stable. the behavior is quite annoying since it is very hard to select a particular printer from such a list that changes so fast. the attachment illustrates the issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libgtk-3-0 3.16.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 17 10:01:31 2015 InstallationDate: Installed on 2014-10-21 (421 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to wily on 2015-12-03 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1527147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1527147] Re: list of printers in print dialog jumps fast, hard to select a printer
this has been the same since ages. please see the attached desktop video capture. the list of printers is in my opinion (a) refreshed too fast and (b) whatever is the sort algorithm for the order in the window, it's not stable, ie each time it produces a slightly different list of printers. it's extremely hard to select the correct printer below the point where it starts to deviate by each update. this is agonizing. note that this is not limited to just the evince print dialog, as shown in the attachment. it affects all print dialogs of all the gtk applications. ** Attachment added: "desktop video illustrating the odd behavior." https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1527147/+attachment/523/+files/evince-print_dialog.ogv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1527147 Title: list of printers in print dialog jumps fast, hard to select a printer Status in gtk+3.0 package in Ubuntu: New Bug description: when opening a gtk print dialog (evince, firefox etc), the list of printers is jumping up and down when many printers are listed. i am not sure if this is related to cups reporting different number of printers each time asked or is this some kind of a list sorting problem in gnome when repeated sorting is not stable. the behavior is quite annoying since it is very hard to select a particular printer from such a list that changes so fast. the attachment illustrates the issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libgtk-3-0 3.16.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 17 10:01:31 2015 InstallationDate: Installed on 2014-10-21 (421 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to wily on 2015-12-03 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1527147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1683428] Re: read_csv on bzip2 file unzips only the first block
Furthermore, according to https://bugs.python.org/issue20781 this is in their opinion "not a bug" ie wont-fix. Unfortunately, the bz2 container clearly allows for multiple concatenated streams (blocks) and therefore IMHO this is a bug since a legally formatted bz2 file is not read correctly and is truncated after the first block. ** Bug watch added: Python Roundup #20781 http://bugs.python.org/issue20781 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1683428 Title: read_csv on bzip2 file unzips only the first block Status in pandas package in Ubuntu: New Status in python2.7 package in Ubuntu: New Bug description: It seems that the read_csv() suffers the same symptoms as eg the early boost implementations, see https://svn.boost.org/trac/boost/ticket/3853 for details. The bz2 files can namely be composed of many concatenated bz2 blocks which have to be treated as a continuous stream. How to test: create large csv file, much larger than 900k. Compress with pbzip2 (each process creates one bz2 block). Alternatively create many such csv files, bzip2 them individually and then cat *.bz2 >joined.bz2 read_csv() will uncompress and read only the first block. Note that this is a severe bug since the parallel bzip2 is getting increasingly common on multi-core systems. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: python-pandas 0.17.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 17 18:42:52 2017 InstallationDate: Installed on 2014-10-21 (909 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: pandas UpgradeStatus: Upgraded to yakkety on 2016-10-20 (179 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pandas/+bug/1683428/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612970] Re: after logout from xfce, lightdm greeter has no widgets except accesibility (ie no shutdown etc)
indeed, the issue went away. thanks. ** Changed in: lightdm (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1612970 Title: after logout from xfce, lightdm greeter has no widgets except accesibility (ie no shutdown etc) Status in lightdm package in Ubuntu: Fix Released Bug description: upon a fresh boot or restart the lightdm greeter gtk theme shows network applet and shutdown/reboot button in the upper right corner. nevertheless, after a logout from an xfce session these widgets are missing from the greeter and therefore the machine cannot be shutdown. on some computers i can switch to console (ctrl-alt-f1) and press ctrl-alt-del for a reboot but on some the console also does not appear (ie it's completely black without a login prompt). my /etc/lightdm/lightdm.conf is [SeatDefaults] greeter-session=unity-greeter is it possible this is related to the pam_systemd.so module and/or systemd itself? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 18:35:04 2016 InstallationDate: Installed on 2015-08-23 (356 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-03-17 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1612970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612970] [NEW] after logout from xfce, lightdm greeter has no widgets except accesibility (ie no shutdown etc)
Public bug reported: upon a fresh boot or restart the lightdm greeter gtk theme shows network applet and shutdown/reboot button in the upper right corner. nevertheless, after a logout from an xfce session these widgets are missing from the greeter and therefore the machine cannot be shutdown. on some computers i can switch to console (ctrl-alt-f1) and press ctrl- alt-del for a reboot but on some the console also does not appear (ie it's completely black without a login prompt). my /etc/lightdm/lightdm.conf is [SeatDefaults] greeter-session=unity-greeter is it possible this is related to the pam_systemd.so module and/or systemd itself? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 18:35:04 2016 InstallationDate: Installed on 2015-08-23 (356 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-03-17 (149 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1612970 Title: after logout from xfce, lightdm greeter has no widgets except accesibility (ie no shutdown etc) Status in lightdm package in Ubuntu: New Bug description: upon a fresh boot or restart the lightdm greeter gtk theme shows network applet and shutdown/reboot button in the upper right corner. nevertheless, after a logout from an xfce session these widgets are missing from the greeter and therefore the machine cannot be shutdown. on some computers i can switch to console (ctrl-alt-f1) and press ctrl-alt-del for a reboot but on some the console also does not appear (ie it's completely black without a login prompt). my /etc/lightdm/lightdm.conf is [SeatDefaults] greeter-session=unity-greeter is it possible this is related to the pam_systemd.so module and/or systemd itself? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 18:35:04 2016 InstallationDate: Installed on 2015-08-23 (356 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-03-17 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1612970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594658] Re: diskless setup with nfs mounted home hangs on shutdown/reboot
this appears also on all our desktops in the institute after an upgrade from 14.04 to 16.04. user yp homes are mounted via autofs/am through nfs and the network is setup via dhcp. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1594658 Title: diskless setup with nfs mounted home hangs on shutdown/reboot Status in nfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 fresh install hangs when shutting down. The system is diskless PXE-booted with a couple of nfs mounted directories including homedir. As I have no persistent storage whatsoever, I don't have any logs, but in debug-shell, running journalctl -f I can see that it hangs at [ *] (1 of 2) A stop job running for Raise Network Interfaces (10s / 1min 30s)Jun 20 20:23:05 $hostname kernel: nfs: server $nfs-ip-address not responding, still trying Jun 20 20:23:05 $hostname kernel: nfs: server $nfs-ip-address not responding, still trying Jun 20 20:23:14 $hostname kernel: nfs: server $nfs-ip-address not responding, still trying Jun 20 20:24:08 $hostname kernel: nfs: server $nfs-ip-address not responding, still trying Second job in "(1 of 2)" is thermald, turning it off does not fix the problem. Also, this counter "(10s / 1min 30s)" stops visually updating. server $nfs-ip-address is not responding, because, all network interfaces are already down at this point. I am not exactly sure why this happens. Looks like there is a wrong ordering of shutdown of systemd services, which bring down interfaces before something nfs-related, but I am not sure if that's the reason of hanging. Workaround that fixes the problem: In /lib/systemd/system/networking.service comment following line: ExecStop=/sbin/ifdown -a --read-environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1594658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547373] [NEW] dmesg is full of apparmor denied messages for ntpd
Public bug reported: after several hours of uptime the dmesg contains only lines of this form: [40376.376099] audit: type=1400 audit(1455869426.923:4311): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40376.376128] audit: type=1400 audit(1455869426.923:4312): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40376.376149] audit: type=1400 audit(1455869426.923:4313): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40376.376168] audit: type=1400 audit(1455869426.923:4314): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40376.376187] audit: type=1400 audit(1455869426.923:4315): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40439.376168] audit: type=1400 audit(1455869489.924:4316): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40439.376195] audit: type=1400 audit(1455869489.924:4317): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40439.376215] audit: type=1400 audit(1455869489.924:4318): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40439.376233] audit: type=1400 audit(1455869489.924:4319): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40439.376252] audit: type=1400 audit(1455869489.924:4320): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40502.376094] audit: type=1400 audit(1455869552.926:4321): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40502.376120] audit: type=1400 audit(1455869552.926:4322): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40502.376140] audit: type=1400 audit(1455869552.926:4323): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40502.376158] audit: type=1400 audit(1455869552.926:4324): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40502.376176] audit: type=1400 audit(1455869552.926:4325): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Feb 19 09:10:48 2016 InstallationDate: Installed on 2016-02-17 (1 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed root=UUID=fddff8cb-9428-47b7-a215-034c4b79c0fe ro nomodeset SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to xenial on 2016-02-17 (1 days ago) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1547373 Title: dmesg is full of apparmor denied messages for ntpd Status in apparmor package in Ubuntu: New Bug description: after several hours of uptime the dmesg contains only lines of this form: [40376.376099] audit: type=1400 audit(1455869426.923:4311): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40376.376128] audit: type=1400 audit(1455869426.923:4312): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40376.376149] audit: type=1400 audit(1455869426.923:4313): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40376.376168] audit: type=1400 audit(1455869426.923:4314): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [40376.376187] audit: type=1400 audit(1455869426.923:4315): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=1295
[Touch-packages] [Bug 1527147] [NEW] list of printers in print dialog jumps fast, hard to select a printer
Public bug reported: when opening a gtk print dialog (evince, firefox etc), the list of printers is jumping up and down when many printers are listed. i am not sure if this is related to cups reporting different number of printers each time asked or is this some kind of a list sorting problem in gnome when repeated sorting is not stable. the behavior is quite annoying since it is very hard to select a particular printer from such a list that changes so fast. the attachment illustrates the issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libgtk-3-0 3.16.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 17 10:01:31 2015 InstallationDate: Installed on 2014-10-21 (421 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to wily on 2015-12-03 (14 days ago) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "desktop video of an evince print dialog" https://bugs.launchpad.net/bugs/1527147/+attachment/4536191/+files/evince-print_dialog.avi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1527147 Title: list of printers in print dialog jumps fast, hard to select a printer Status in gtk+3.0 package in Ubuntu: New Bug description: when opening a gtk print dialog (evince, firefox etc), the list of printers is jumping up and down when many printers are listed. i am not sure if this is related to cups reporting different number of printers each time asked or is this some kind of a list sorting problem in gnome when repeated sorting is not stable. the behavior is quite annoying since it is very hard to select a particular printer from such a list that changes so fast. the attachment illustrates the issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libgtk-3-0 3.16.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 17 10:01:31 2015 InstallationDate: Installed on 2014-10-21 (421 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to wily on 2015-12-03 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1527147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1526415] [NEW] after upgrade printer properties not recognized (paper, duplex etc)
Public bug reported: after an upgrade from ubuntu 15.04 to 15.10 the print dialogs (eg in okular, firefox etc) do not display any printer properties and do not allow to change anything. for example, default paper setting for our main printer is now in okular "Letter" while it's clearly an "A4" printer. in okular and firefox one cannot change the duplex options anymore. in short: while remote printers are still recognized and listed, it seems their settings are not. while my clients are version 2.1.0, our institute cups server runs version 1.5.3 and i don't see any easy way we can force them to upgrade it. i tried to force the lower version by stopping both cups services (cups and cups-browsed) and creating an /etc/cups/client.conf with ServerName x.y.z/version=1.1 but it seems this is not supported anymore. lpstat does not see any printers but the "add /version=1.1" message is still issued, although obviously not supported. are these inconsistencies any indication of a possible bug? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CupsErrorLog: CurrentDesktop: XFCE Date: Tue Dec 15 17:06:19 2015 InstallationDate: Installed on 2014-10-21 (420 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: FUJITSU ESPRIMO P920 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=32705539-7b51-428b-ac41-c448145dea7d ro SourcePackage: cups UpgradeStatus: Upgraded to wily on 2015-12-03 (12 days ago) dmi.bios.date: 10/23/2014 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.30.0 for D3222-A1x dmi.board.name: D3222-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3222-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$WX02 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.30.0forD3222-A1x:bd10/23/2014:svnFUJITSU:pnESPRIMOP920:pvr:rvnFUJITSU:rnD3222-A1:rvrS26361-D3222-A1:cvnFUJITSU:ct6:cvrC$WX02: dmi.product.name: ESPRIMO P920 dmi.sys.vendor: FUJITSU ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1526415 Title: after upgrade printer properties not recognized (paper, duplex etc) Status in cups package in Ubuntu: New Bug description: after an upgrade from ubuntu 15.04 to 15.10 the print dialogs (eg in okular, firefox etc) do not display any printer properties and do not allow to change anything. for example, default paper setting for our main printer is now in okular "Letter" while it's clearly an "A4" printer. in okular and firefox one cannot change the duplex options anymore. in short: while remote printers are still recognized and listed, it seems their settings are not. while my clients are version 2.1.0, our institute cups server runs version 1.5.3 and i don't see any easy way we can force them to upgrade it. i tried to force the lower version by stopping both cups services (cups and cups-browsed) and creating an /etc/cups/client.conf with ServerName x.y.z/version=1.1 but it seems this is not supported anymore. lpstat does not see any printers but the "add /version=1.1" message is still issued, although obviously not supported. are these inconsistencies any indication of a possible bug? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CupsErrorLog: CurrentDesktop: XFCE Date: Tue Dec 15 17:06:19 2015 InstallationDate: Installed on 2014-10-21 (420 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: FUJITSU ESPRIMO P920 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=32705539-7b51-428b-ac41-c448145dea7d ro SourcePackage: cups UpgradeStatus: Upgraded to wily on 2015-12-03 (12 days ago) dmi.bios.date: 10/23/2014 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.30.0 for D3222-A1x dmi.board.name: D3222-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3222-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$WX02 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.30.0forD3222-A1x:bd10/23/2014:svnFUJITSU:pnESPRIMOP920:pvr:rvnFUJITSU:rnD3222-A1:rvrS26361-D3222-A1:cvnFUJITSU:ct6:cvrC$WX02: dmi.product.name: ESPRIMO P920 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to:
[Touch-packages] [Bug 1449737] Re: gallery and camera icons turn black after the r21 update
there was a camera update and the icon came back from its transparent death. unfortunately gallery's icon is still empty and fully transparent... is there a way i can rebuild/refresh icons? i guess its the cached bitmap that's broken, original svg might be ok. please help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1449737 Title: gallery and camera icons turn black after the r21 update Status in gallery-app package in Ubuntu: New Bug description: i got the bq ubuntu phone a week ago and did the update immediately. unfortunately this turned the gallery and camera icons in side bar and in the apps scope to black. and they stayed black since then. is there some kind of an icon-update workaround? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1449737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449737] Re: gallery and camera icons turn black after the r21 update
... or run something like dpkg-reconfigure *-icon-theme ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1449737 Title: gallery and camera icons turn black after the r21 update Status in gallery-app package in Ubuntu: New Bug description: i got the bq ubuntu phone a week ago and did the update immediately. unfortunately this turned the gallery and camera icons in side bar and in the apps scope to black. and they stayed black since then. is there some kind of an icon-update workaround? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1449737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449737] Re: gallery and camera icons turn black after the r21 update
in fact, it's quite annoying to have these empty icons lying around... is there something like gtk-update-icon-cache or similar i can run in terminal as root? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1449737 Title: gallery and camera icons turn black after the r21 update Status in gallery-app package in Ubuntu: New Bug description: i got the bq ubuntu phone a week ago and did the update immediately. unfortunately this turned the gallery and camera icons in side bar and in the apps scope to black. and they stayed black since then. is there some kind of an icon-update workaround? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1449737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449737] Re: gallery and camera icons turn black after the r21 update
in fact, the icons became transparent. and it's not only camera and gallery, it's also calculator, music, reminders, twitter, and weather. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1449737 Title: gallery and camera icons turn black after the r21 update Status in system-image package in Ubuntu: New Bug description: i got the bq ubuntu phone a week ago and did the update immediately. unfortunately this turned the gallery and camera icons in side bar and in the apps scope to black. and they stayed black since then. is there some kind of an icon-update workaround? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1449737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449737] [NEW] gallery and camera icons turn black after the r21 update
Public bug reported: i got the bq ubuntu phone a week ago and did the update immediately. unfortunately this turned the gallery and camera icons in side bar and in the apps scope to black. and they stayed black since then. is there some kind of an icon-update workaround? ** Affects: system-image (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1449737 Title: gallery and camera icons turn black after the r21 update Status in system-image package in Ubuntu: New Bug description: i got the bq ubuntu phone a week ago and did the update immediately. unfortunately this turned the gallery and camera icons in side bar and in the apps scope to black. and they stayed black since then. is there some kind of an icon-update workaround? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1449737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449740] [NEW] needs eduroam support (wpa2-peap)
Public bug reported: the network manager needs support for wpa2-peap, ie once the ssid eduroam is selected, an email and password dialog has to appear. workaround: edit the /etc/NetworkManager/system-connections/eduroam as given in http://askubuntu.com/questions/606298/eduroam-on-aquaris-e4-5 -ubuntu-edition ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1449740 Title: needs eduroam support (wpa2-peap) Status in indicator-network package in Ubuntu: New Bug description: the network manager needs support for wpa2-peap, ie once the ssid eduroam is selected, an email and password dialog has to appear. workaround: edit the /etc/NetworkManager/system-connections/eduroam as given in http://askubuntu.com/questions/606298/eduroam-on-aquaris-e4-5 -ubuntu-edition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1449740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
