[Desktop-packages] [Bug 1924217] Re: bluetoothd segfaults when Trackpoint II keyboard connects
Actually upstream bug report https://github.com/bluez/bluez/issues/112 confirms the symptoms. ** Summary changed: - bluetoothd segfaults when Trackpoint II keyboard connects + bluetoothd segfaults when Trackpoint II keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed ** Description changed: + https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 + + --- + bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 - [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] + [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/zsh + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 - UP RUNNING - RX bytes:267050 acl:16636 sco:0 events:966 errors:0 - TX bytes:28087 acl:371 sco:0 commands:388 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 + UP RUNNING + RX bytes:267050 acl:16636 sco:0 events:966 errors:0 + TX bytes:28087 acl:371 sco:0 commands:388 errors:0 ** Also affects: bluez via https://github.com/bluez/bluez/issues/112 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-5.57 fixed-upstream ** Summary changed: - bluetoothd segfaults when Trackpoint II keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] + bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- You
[Desktop-packages] [Bug 1924220] [NEW] bluetoothd crashed with SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()
*** This bug is a duplicate of bug 1924217 *** https://bugs.launchpad.net/bugs/1924217 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.56-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924220 Title: bluetoothd crashed with SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach() Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.56-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1924220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924217] [NEW] bluetoothd segfaults when Trackpoint II keyboard connects
Public bug reported: bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd segfaults when Trackpoint II keyboard connects Status in bluez package in Ubuntu: New Bug description: bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem
[Desktop-packages] [Bug 1921465] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_scale() from shell_blur_effect_paint() from clutter_actor_continue_paint() from clutter_paint_node_paint
** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1921465 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_scale() from shell_blur_effect_paint() from clutter_actor_continue_paint() from clutter_paint_node_paint() from clutter_actor_paint() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.3-2ubuntu0.20.10.2, the problem page at https://errors.ubuntu.com/problem/885f3e0d59a980a433c60d937eee546b035951d3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1921465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922539] Re: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
** Changed in: mutter (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1922539 Title: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. Status in mutter package in Ubuntu: Fix Committed Bug description: Hi, I see this warning message in the logs: # journalctl | grep -e -listen Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Apr 5 10:07:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1922539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915080]
Created attachment 171194 45386_example.doc: the document mentioned in comment 0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/915080 Title: [Upstream] Column formatting not honored saving to .doc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915080/+attachment/2685315/+files/Blocco%20schizzi%20botanico.doc -O example.doc && lowriter -nologo example.doc Click Format -> Sections... -> highlight Section1 -> click button Remove -> highlight Section3 -> click button Remove -> button OK -> Format -> Columns... -> change combobox Columns to 2 -> button OK -> Save, close, reopen and the column formatting remains as in the screenshot https://launchpadlibrarian.net/91366200/Schermata-L%27arte%20del%20disegno%20botanico.doc2%20-%20LibreOffice%20Writer.png . 4) What happens instead is the column formatting changes back to the way it was before making the above changes. A screenshot of this https://launchpadlibrarian.net/91366199/Schermata-L%27arte%20del%20disegno%20botanico.doc1%20-%20LibreOffice%20Writer.png . WORKAROUND: Save as .odt as the column formatting is preserved. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 Architecture: i386 Date: Wed Jan 11 23:50:02 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=it_IT:en LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-10-17 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/915080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915080]
repro 7.2+. Also true for DOCX. A TableOfContents is a semi-section in Writer, so probably that is throwing things off during export. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/915080 Title: [Upstream] Column formatting not honored saving to .doc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915080/+attachment/2685315/+files/Blocco%20schizzi%20botanico.doc -O example.doc && lowriter -nologo example.doc Click Format -> Sections... -> highlight Section1 -> click button Remove -> highlight Section3 -> click button Remove -> button OK -> Format -> Columns... -> change combobox Columns to 2 -> button OK -> Save, close, reopen and the column formatting remains as in the screenshot https://launchpadlibrarian.net/91366200/Schermata-L%27arte%20del%20disegno%20botanico.doc2%20-%20LibreOffice%20Writer.png . 4) What happens instead is the column formatting changes back to the way it was before making the above changes. A screenshot of this https://launchpadlibrarian.net/91366199/Schermata-L%27arte%20del%20disegno%20botanico.doc1%20-%20LibreOffice%20Writer.png . WORKAROUND: Save as .odt as the column formatting is preserved. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 Architecture: i386 Date: Wed Jan 11 23:50:02 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=it_IT:en LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-10-17 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/915080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915080] Re: [Upstream] Column formatting not honored saving to .doc
** Changed in: df-libreoffice Importance: Medium => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/915080 Title: [Upstream] Column formatting not honored saving to .doc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915080/+attachment/2685315/+files/Blocco%20schizzi%20botanico.doc -O example.doc && lowriter -nologo example.doc Click Format -> Sections... -> highlight Section1 -> click button Remove -> highlight Section3 -> click button Remove -> button OK -> Format -> Columns... -> change combobox Columns to 2 -> button OK -> Save, close, reopen and the column formatting remains as in the screenshot https://launchpadlibrarian.net/91366200/Schermata-L%27arte%20del%20disegno%20botanico.doc2%20-%20LibreOffice%20Writer.png . 4) What happens instead is the column formatting changes back to the way it was before making the above changes. A screenshot of this https://launchpadlibrarian.net/91366199/Schermata-L%27arte%20del%20disegno%20botanico.doc1%20-%20LibreOffice%20Writer.png . WORKAROUND: Save as .odt as the column formatting is preserved. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 Architecture: i386 Date: Wed Jan 11 23:50:02 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=it_IT:en LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-10-17 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/915080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924190] Re: Display is wrong resolution, aspect ratio, and size
It appears you have a manually installed Nvidia driver, which is not supported, and it stopped working around the time of the kernel update from 5.8.0-48 to 5.8.0-49. Please uninstall the NVIDIA driver you have and in future only install NVIDIA drivers using the 'Additional Drivers' app so as to ensure they will keep working with future kernel updates. ** Package changed: xorg (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924190 Title: Display is wrong resolution, aspect ratio, and size Status in linux-hwe-5.8 package in Ubuntu: Invalid Bug description: So last night (April 13th), I installed an update from Canonical that popped up in a GUI, it said something about a security update (I didn't look at it too hard). Since then I've rebooted my machine and now the display is the wrong resolution (it ought to be 3840 x 2160, 597mm x 336mm, 60fps [monitor](https://www.lg.com/us/monitors/lg- 27UD58-B-4k-uhd-led-monitor)). I'm presently on Ubuntu 20.04.2 LTS. ``` $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected primary 1024x768+0+0 0mm x 0mm 1024x768 76.00* ``` ``` $ inxi -G Graphics: Device-1: NVIDIA GM107GL [Quadro K2200] driver: N/A Display: x11 server: X.Org 1.20.9 driver: fbdev,nouveau unloaded: modesetting,vesa resolution: 1024x768~76Hz OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.2.6 ``` I've tried unplugging and replugging the monitor, rebooting several times, adding an xrandr modeline, and changing `/etc/default/grub` to have `GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"` (where it was `"quiet splash"` before). None of these have led to any success. My feeling is that there's some graphics driver issue (that the renderer is llvmpipe doesn't seem right). I guess there's also a confounding factor in that I'm running the display through a [KVM switch](https://www.tripplite.com/2-port- displayport-usb-kvm-switch-4k-60-hz-hdr%7EB005DPUA4), but I really hope that's not the problem. I've been using it for a while anyway with no issue, the Windows 10 partition of this machine renders fine, and I have another machine running 18.04 that gets the resolution just fine. I tried booting into recovery mode, which was no dice (also tried cleaning up `dpkg` through the recovery interface). While I was in the GRUB menu, I noticed that it defaults to the kernel version 5.8.0-49, but that I also had 5.8.0-48 installed. Boothing into the older kernel, everything worked. Curious, I checked the logs. ``` $ cat /var/log/dpkg.log | grep linux-image 2021-04-13 23:15:01 install linux-image-5.8.0-49-generic:amd64 5.8.0-49.55~20.04.1 ``` And that lines up with when I did that update. So it seems that the new kernel version somehow made it so xrandr couldn't detect any of the modes on my monitor and just defaulted to some default. So the workaround presently is just boot with 5.8.0-48. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 17:21:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2021-02-15 (58 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=babb99d2-0867-4673-b5ec-2cce0643eaa2 ro quiet splash i915.alpha_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string
[Desktop-packages] [Bug 1923910] Re: Some mouse buttons not working
** Package changed: xorg (Ubuntu) => xserver-xorg-input-libinput (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1923910 Title: Some mouse buttons not working Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I have a Jelly Comb mouse, connected with a wireless USB dongle. It has two main buttons, a clickable scrollwheel, and another button behind the scrollwheel. XEV does not detect clicks from the scrollwheel, or the additional button behind the scrollwheel. Attached is a xev report where all the buttons are activated. Button 1 is left click, Button 3 is right click, Button 4 is scroll up and Button 5 is scroll down. I am using Ubuntu 20.04.2 LTS xmodmap-pp gives the following: There are 10 pointer buttons defined. PhysicalButton Button Code 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 06:24:04 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:0962] InstallationDate: Installed on 2020-07-18 (270 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=20970931-2eaa-4849-82b5-1932983e40fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0YRRCV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/09/2020:br1.5:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0YRRCV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1923910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923840] Re: Xorg freeze
Do you need this bug reopened? Is it still a problem? ** Package changed: xorg (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Summary changed: - Xorg freeze + Boots to black screen with 5.8.0-49, but 5.8.0-48 boots fine -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923840 Title: Boots to black screen with 5.8.0-49, but 5.8.0-48 boots fine Status in linux-hwe-5.8 package in Ubuntu: Invalid Bug description: After booting there is only a black screen showing a blinking _ in the top left corner. Nothing happens anymore. It only happens with Linux version 5.8.0-49-generic. Linux version 5.8.0-48-generic boots fine. Description:Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 14:25:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116 [GeForce GTX 1660 SUPER] [103c:8789] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87d6] InstallationDate: Installed on 2021-02-27 (45 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Pavilion Gaming Desktop TG01-1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2020 dmi.bios.release: 15.16 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.name: 87D6 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 103.9 dmi.modalias: dmi:bvnAMI:bvrF.10:bd11/19/2020:br15.16:efr103.9:svnHP:pnHPPavilionGamingDesktopTG01-1xxx:pvr:rvnHP:rn87D6:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Gaming Desktop TG01-1xxx dmi.product.sku: 27Y73EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1923840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923885] Re: refresh the screen in loop
Can you please reword that and/or attach a video or photo of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923885 Title: refresh the screen in loop Status in Ubuntu: Incomplete Bug description: Ubuntu refresh gnome s untimely since the last update today ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 14:13:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:196f] InstallationDate: Installed on 2020-11-09 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=f1803267-7782-45d5-b32e-439833ebf772 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.release: 15.6 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 196F dmi.board.vendor: Hewlett-Packard dmi.board.version: 95.19 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.25 dmi.modalias: dmi:bvnInsyde:bvrF.06:bd05/28/2013:br15.6:efr95.25:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr088310305B1620100:rvnHewlett-Packard:rn196F:rvr95.19:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: E0M66UA#ABL dmi.product.version: 088310305B1620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105+git2104141700.67a64b~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2104140600.165a69~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
I've subscribed Timo who should know why Ubuntu still prefers 'radeon' and 'amdgpu' Xorg drivers. But also I am only guessing that my recommended config changes will fix the issue. It would be useful to test them too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: In Progress Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923840] Re: Xorg freeze
** Changed in: xorg (Ubuntu) Status: New => Fix Released ** Changed in: xorg (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923840 Title: Xorg freeze Status in xorg package in Ubuntu: Invalid Bug description: After booting there is only a black screen showing a blinking _ in the top left corner. Nothing happens anymore. It only happens with Linux version 5.8.0-49-generic. Linux version 5.8.0-48-generic boots fine. Description:Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 14:25:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116 [GeForce GTX 1660 SUPER] [103c:8789] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87d6] InstallationDate: Installed on 2021-02-27 (45 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Pavilion Gaming Desktop TG01-1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2020 dmi.bios.release: 15.16 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.name: 87D6 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 103.9 dmi.modalias: dmi:bvnAMI:bvrF.10:bd11/19/2020:br15.16:efr103.9:svnHP:pnHPPavilionGamingDesktopTG01-1xxx:pvr:rvnHP:rn87D6:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Gaming Desktop TG01-1xxx dmi.product.sku: 27Y73EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924190] [NEW] Display is wrong resolution, aspect ratio, and size
Public bug reported: So last night (April 13th), I installed an update from Canonical that popped up in a GUI, it said something about a security update (I didn't look at it too hard). Since then I've rebooted my machine and now the display is the wrong resolution (it ought to be 3840 x 2160, 597mm x 336mm, 60fps [monitor](https://www.lg.com/us/monitors/lg-27UD58-B-4k- uhd-led-monitor)). I'm presently on Ubuntu 20.04.2 LTS. ``` $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected primary 1024x768+0+0 0mm x 0mm 1024x768 76.00* ``` ``` $ inxi -G Graphics: Device-1: NVIDIA GM107GL [Quadro K2200] driver: N/A Display: x11 server: X.Org 1.20.9 driver: fbdev,nouveau unloaded: modesetting,vesa resolution: 1024x768~76Hz OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.2.6 ``` I've tried unplugging and replugging the monitor, rebooting several times, adding an xrandr modeline, and changing `/etc/default/grub` to have `GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"` (where it was `"quiet splash"` before). None of these have led to any success. My feeling is that there's some graphics driver issue (that the renderer is llvmpipe doesn't seem right). I guess there's also a confounding factor in that I'm running the display through a [KVM switch](https://www.tripplite.com/2-port- displayport-usb-kvm-switch-4k-60-hz-hdr%7EB005DPUA4), but I really hope that's not the problem. I've been using it for a while anyway with no issue, the Windows 10 partition of this machine renders fine, and I have another machine running 18.04 that gets the resolution just fine. I tried booting into recovery mode, which was no dice (also tried cleaning up `dpkg` through the recovery interface). While I was in the GRUB menu, I noticed that it defaults to the kernel version 5.8.0-49, but that I also had 5.8.0-48 installed. Boothing into the older kernel, everything worked. Curious, I checked the logs. ``` $ cat /var/log/dpkg.log | grep linux-image 2021-04-13 23:15:01 install linux-image-5.8.0-49-generic:amd64 5.8.0-49.55~20.04.1 ``` And that lines up with when I did that update. So it seems that the new kernel version somehow made it so xrandr couldn't detect any of the modes on my monitor and just defaulted to some default. So the workaround presently is just boot with 5.8.0-48. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 17:21:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2021-02-15 (58 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=babb99d2-0867-4673-b5ec-2cce0643eaa2 ro quiet splash i915.alpha_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITEWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITEWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1923910] Re: Some mouse buttons not working
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923910 Title: Some mouse buttons not working Status in xorg package in Ubuntu: New Bug description: I have a Jelly Comb mouse, connected with a wireless USB dongle. It has two main buttons, a clickable scrollwheel, and another button behind the scrollwheel. XEV does not detect clicks from the scrollwheel, or the additional button behind the scrollwheel. Attached is a xev report where all the buttons are activated. Button 1 is left click, Button 3 is right click, Button 4 is scroll up and Button 5 is scroll down. I am using Ubuntu 20.04.2 LTS xmodmap-pp gives the following: There are 10 pointer buttons defined. PhysicalButton Button Code 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 06:24:04 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:0962] InstallationDate: Installed on 2020-07-18 (270 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=20970931-2eaa-4849-82b5-1932983e40fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0YRRCV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/09/2020:br1.5:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0YRRCV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923910] [NEW] Some mouse buttons not working
You have been subscribed to a public bug: I have a Jelly Comb mouse, connected with a wireless USB dongle. It has two main buttons, a clickable scrollwheel, and another button behind the scrollwheel. XEV does not detect clicks from the scrollwheel, or the additional button behind the scrollwheel. Attached is a xev report where all the buttons are activated. Button 1 is left click, Button 3 is right click, Button 4 is scroll up and Button 5 is scroll down. I am using Ubuntu 20.04.2 LTS xmodmap-pp gives the following: There are 10 pointer buttons defined. PhysicalButton Button Code 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 06:24:04 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:0962] InstallationDate: Installed on 2020-07-18 (270 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=20970931-2eaa-4849-82b5-1932983e40fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0YRRCV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/09/2020:br1.5:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0YRRCV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Some mouse buttons not working https://bugs.launchpad.net/bugs/1923910 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+
It's still necessary; I've got the changes ready but was holding off as there's possibly another fix that may need to go into this package too (LP: #1900904). But it's getting close to release so I'll push it anyway and deal with the other ticket separately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: New Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924186] [NEW] firefox title bar cannot be turned off in 21.04
Public bug reported: Today a Firefox update was pushed out for 21.04. Not sure if this problem occurred with the update or before, but I just noticed it after the update. Using the Firefox hamburger menu, then selecting Customize toolbar... I arrive at a tab titled Customize Firefox. In the lower left corner of the screen is a checkbox for Titlebar. If that checkbox is checked, the titlebar appears at the top of the window, and below it are all the tabs. If that checkbox is NOT checked, the titlebar remains visible but now the window controls are duplicated on the tabs line (in my case to the left as I have the window control position set to the left). In previous versions of Firefox, it was nice to be able to turn off the titlebar and have the controls move to the tabs line. And in any case, two sets of active window controls, one beneath the other, is not particularly useful. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu64 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: clh1415 F pulseaudio /dev/snd/controlC0: clh1415 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:30:39 2021 ForcedLayersAccel: False InstallationDate: Installed on 2021-04-10 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210408) IpRoute: default via 192.168.1.254 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.13 metric 100 MostRecentCrashID: bp-61d2fae9-da3a-417f-9fe1-917de0180212 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112 (In use) RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12e dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12e:bd03/06/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1924186 Title: firefox title bar cannot be turned off in 21.04 Status in firefox package in Ubuntu: New Bug description: Today a Firefox update was pushed out for 21.04. Not sure if this problem occurred with the update or before, but I just noticed it after the update. Using the Firefox hamburger menu, then selecting Customize toolbar... I arrive at a tab titled Customize Firefox. In the lower left corner of the screen is a checkbox for Titlebar. If that checkbox is checked, the titlebar appears at the top of the window, and below it are all the tabs. If that checkbox is NOT checked, the titlebar remains visible but now the window controls are duplicated on the tabs line (in my case to the left as I have the window control position set to the left). In previous versions of Firefox, it was nice to be able to turn off the titlebar and have the controls move to the tabs line. And in any case, two sets of active window controls, one beneath the other, is not particularly useful. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu64 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: clh1415 F pulseaudio /dev/snd/controlC0: clh1415 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:30:39 2021 ForcedLayersAccel: False
[Desktop-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+
Is this ubuntu-settings task still necessary or should it be closed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: New Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915677] Re: [ snap ] libreoffice-style-* packages are missing ?
It looks very OK ! …except SVG but not the topic here. See picture attached lo_snap_05.jpg It's Ubuntu Budgie 20.04 + vimix-dark-ruby gtk theme ( as a snap ) + LO 7.1 you sent. ** Attachment added: "Breeze Dark + Sifr Dark + both Yaru" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915677/+attachment/5488001/+files/lo_snap_05.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1915677 Title: [ snap ] libreoffice-style-* packages are missing ? Status in libreoffice package in Ubuntu: In Progress Bug description: Hi, trying LibreOffice 7 as a snap on UbuntuBudgie 20.04. I generally use dark gtk theme style system wide - and some are available as snap ( Adapta ). I often use Papirus icons set - and those are also ( partly ) available as snap ( through Adpata gtk theme ). I can't see if the same choice exists while using LO as a snap : I can find some icons theme ( elementary, colibre, breeze, and so on ) but they all look designed for global light gtk themes. In other words icons in my LO are black on black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921931] Re: Opening links results in "Firefox is already running, but is not responding"
** Branch linked: lp:firefox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1921931 Title: Opening links results in "Firefox is already running, but is not responding" Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Since the latest package release enabling wayland, I often get the "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." message when trying to open links from other applications (eg geary, slack) instead of having the link open in the existing firefox window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 829438 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Mar 30 09:14:13 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (591 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago) dmi.bios.date: 07/15/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1921931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923090] Re: autopkgtest fails in hirsute on armhf
And I can confirm that if I spoof the user agent using the "armv7l" token, the google search page is redirected to the consent page, which is consistent with what I'm seeing with firefox on android. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1923090 Title: autopkgtest fails in hirsute on armhf Status in firefox package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/packages/f/firefox/hirsute/armhf https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- hirsute/hirsute/armhf/f/firefox/20210408_154741_90187@/log.gz ... autopkgtest [15:44:53]: test command3: [--- Traceback (most recent call last): File "/tmp/autopkgtest.D3W44g/build.bPt/src/debian/tests/search-engines", line 51, in search URL for Google: https://consent.google.com/ml?continue=https://www.google.com/search%3Fchannel%3Dfs%26client%3Dubuntu%26q%3Dfoobarbaz=GB=1=srp=en=1 assert url.netloc == v['netloc'] AssertionError autopkgtest [15:45:08]: test command3: ---] autopkgtest [15:45:11]: test command3: - - - - - - - - - - results - - - - - - - - - - command3 FAIL non-zero exit status 1 autopkgtest [15:45:12]: test command3: - - - - - - - - - - stderr - - - - - - - - - - Traceback (most recent call last): File "/tmp/autopkgtest.D3W44g/build.bPt/src/debian/tests/search-engines", line 51, in assert url.netloc == v['netloc'] AssertionError ... Most likely an infrastructure proxy/networking error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1923090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923925] [NEW] Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260
Public bug reported: A new bluetooth headset (Teufel Airy True Wireless) cannot be paired on my dell precision 5530 having an intel ac 9260 bluetooth chipset using ubuntu 20.04. Using an ubuntu 18.04 (boot from usb) I was able to connect the headset without any problem. As a workaround I transfering the device info file (/var/lib/bluetooth///info) to 20.04, having it paired this way it works without problems. It was important to reset device list on the hedphones before, it was not connecting in 18.04 after unsuccessfuly trying with 20.04 so maybe there was already a device key stored in the headset. Please let me know if I could give you further debug information. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923925 Title: Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260 Status in bluez package in Ubuntu: New Bug description: A new bluetooth headset (Teufel Airy True Wireless) cannot be paired on my dell precision 5530 having an intel ac 9260 bluetooth chipset using ubuntu 20.04. Using an ubuntu 18.04 (boot from usb) I was able to connect the headset without any problem. As a workaround I transfering the device info file (/var/lib/bluetooth///info) to 20.04, having it paired this way it works without problems. It was important to reset device list on the hedphones before, it was not connecting in 18.04 after unsuccessfuly trying with 20.04 so maybe there was already a device key stored in the headset. Please let me know if I could give you further debug information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923714] Re: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1
Please note that keeping the proposed pocket enabled is not recommended, it may result in broken packages being installed on your system. The recommendation is to enable it only occasionally when you need to test a selected package, and once testing is complete disable it again. ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1923714 Title: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 Status in libreoffice package in Ubuntu: Invalid Bug description: Among other, package *libreoffice* 7.0.5-0ubunt0.20.10.1 is missing in the *groovy-proposed* archives. ``` $ more /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-poli cy" VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy $ apt list --upgradable Listing... Done libreoffice-base-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-calc/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-draw/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gnome/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gtk3/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-impress/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-math/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-writer/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] python3-uno/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] ``` ``` $ apt-cache policy libreoffice-math libreoffice-math: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.5-0ubuntu0.20.10.1 Version table: 1:7.0.5-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com groovy-proposed/main ppc64el Packages *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/main ppc64el Packages $ apt-cache policy libreoffice libreoffice: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.3-0ubuntu0.20.10.1 Version table: *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/universe ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/universe ppc64el Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1923714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923714] Re: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1
Rico is right. I only had the entry below. No idea, if I only added the line below several versions ago or some upgrade changed it. (Probably the former.) deb http://de.ports.ubuntu.com groovy-proposed main restricted Following https://wiki.ubuntu.com/Testing/EnableProposed I added `multiverse universe`, and now the upgrade went through. Sorry for the noise. Please close the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1923714 Title: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 Status in libreoffice package in Ubuntu: Incomplete Bug description: Among other, package *libreoffice* 7.0.5-0ubunt0.20.10.1 is missing in the *groovy-proposed* archives. ``` $ more /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-poli cy" VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy $ apt list --upgradable Listing... Done libreoffice-base-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-calc/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-draw/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gnome/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gtk3/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-impress/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-math/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-writer/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] python3-uno/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] ``` ``` $ apt-cache policy libreoffice-math libreoffice-math: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.5-0ubuntu0.20.10.1 Version table: 1:7.0.5-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com groovy-proposed/main ppc64el Packages *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/main ppc64el Packages $ apt-cache policy libreoffice libreoffice: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.3-0ubuntu0.20.10.1 Version table: *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/universe ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/universe ppc64el Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1923714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915677] Re: [ snap ] libreoffice-style-* packages are missing ?
Currently downloading… Once tested ( and hopefully approved ) how do I remove it ? Just by a snap remove ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1915677 Title: [ snap ] libreoffice-style-* packages are missing ? Status in libreoffice package in Ubuntu: In Progress Bug description: Hi, trying LibreOffice 7 as a snap on UbuntuBudgie 20.04. I generally use dark gtk theme style system wide - and some are available as snap ( Adapta ). I often use Papirus icons set - and those are also ( partly ) available as snap ( through Adpata gtk theme ). I can't see if the same choice exists while using LO as a snap : I can find some icons theme ( elementary, colibre, breeze, and so on ) but they all look designed for global light gtk themes. In other words icons in my LO are black on black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923893] [NEW] After rescheduling an event, calendar alerts appear for the old time
Public bug reported: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1923893 Title: After rescheduling an event, calendar alerts appear for the old time Status in gnome-shell package in Ubuntu: New Bug description: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
*** This bug is a duplicate of bug 1775392 *** https://bugs.launchpad.net/bugs/1775392 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: A Lenovo P53 is installed with ubuntu 18.04.5 LTS. Graphics Intel UHD Graphics 630 (main display), nvidia quadro RTX 5000 also installed but not used for main display. Laptop is domain joined. When logging to the local ubuntu user, there is no problem detected. Then, if we log out and try to login with a domain user, gnome crashes. From what I can see in the logs, the user is authenticated correctly, but then in the instantiation of the session, gnome.shell.desktop faces an unrecoverable failure. From auth.log ``` pam_sss(gdm-password:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=u...@na.cie.com Oct 23 16:27:28 WLLNXPFX gdm-password]: pam_unix(gdm-password:session): session opened for user u...@na.cie.com by (uid=0) Oct 23 16:27:28 WLLNXPFX systemd-logind[1200]: New session 17 of user u...@na.cie.com. ``` From syslog ``` Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: after 21 requests (21 known processed) with 0 events remaining. ``` I will include the full syslog and auth.log to this bug. Please let me know if any other log could be useful to troubleshoot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
nope, sorry -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
Reverting incorrect bug status. Or are you working on that @Luna? ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 76449] Re: Cannot sort static playlists
It's not fixed yet! This bug was reported 15 years ago -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/76449 Title: Cannot sort static playlists Status in One Hundred Papercuts: Confirmed Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Triaged Bug description: Binary package hint: rhythmbox Architecture: i386 Version: 0.9.7-0ubuntu1 Static playlists cannot be sorted by a column. I think this used to work with earlier RB versions. Sorting by column works with "Smart playlists" though. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/76449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923885] [NEW] refresh the screen in loop
Public bug reported: Ubuntu refresh gnome s untimely since the last update today ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 14:13:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:196f] InstallationDate: Installed on 2020-11-09 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=f1803267-7782-45d5-b32e-439833ebf772 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.release: 15.6 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 196F dmi.board.vendor: Hewlett-Packard dmi.board.version: 95.19 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.25 dmi.modalias: dmi:bvnInsyde:bvrF.06:bd05/28/2013:br15.6:efr95.25:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr088310305B1620100:rvnHewlett-Packard:rn196F:rvr95.19:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: E0M66UA#ABL dmi.product.version: 088310305B1620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105+git2104141700.67a64b~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2104140600.165a69~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923885 Title: refresh the screen in loop Status in xorg package in Ubuntu: New Bug description: Ubuntu refresh gnome s untimely since the last update today ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 14:13:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:196f] InstallationDate: Installed on 2020-11-09 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=f1803267-7782-45d5-b32e-439833ebf772 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.release: 15.6 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 196F
[Desktop-packages] [Bug 1735998] Re: [Needs-Packaging]Decouple unity related settings as unity-settings
@jbicha I'm not sure why this package wasn't approved, since the other flavours do have settings packages (such as ubuntustudio-default- settings and lubuntu-default-settings, as well as kubuntu-settings- desktop). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: [Needs-Packaging]Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity-settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906741] Re: Firefox sometimes causes garbled audio
I can add some information to this bug (or what seems to be a bunch of related audio bugs). In my case it is related to my sound card, switching to and from the soundcard audio causes the bug to appear and disappear. Line-Out - Built-in Audio : No bug Digital Output (S/PDIF) - EMU20k2 [Sound Blaster X-Fi Titanium Series] : Occasionally garbled audio I've added more info about my hardware devices and drivers: lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 01:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1) 03:00.0 Audio device: Creative Labs EMU20k2 [Sound Blaster X-Fi Titanium Series] (rev 04) sudo lshw -C sound *-multimedia description: Audio device product: GP102 HDMI Audio Controller vendor: NVIDIA Corporation physical id: 0.1 bus info: pci@:01:00.1 version: a1 width: 32 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:17 memory:fb08-fb083fff *-usb description: Audio device product: HD Webcam C615 vendor: Logitech, Inc. physical id: 2 bus info: usb@1:1.2 version: 0.11 serial: 27A1DFD0 capabilities: usb-2.00 audio-control configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s *-multimedia description: Audio device product: 6 Series/C200 Series Chipset Family High Definition Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@:00:1b.0 version: 05 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:34 memory:f930-f9303fff *-multimedia description: Audio device product: EMU20k2 [Sound Blaster X-Fi Titanium Series] vendor: Creative Labs physical id: 0 bus info: pci@:03:00.0 version: 04 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_ctxfi latency=0 resources: irq:17 memory:f920-f920 memory:f900-f91f memory:f800-f8ff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (1140 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on
[Desktop-packages] [Bug 1923090] Re: autopkgtest fails in hirsute on armhf
In the autopkgtest infrastructure, on armhf the UA string is:
Mozilla/5.0 (X11; Ubuntu; Linux armv7l; rv:88.0) Gecko/20100101
Firefox/88.0
i.e. the difference with my tests in an armhf container is the
architecture ("armv7l" vs "armv8l")
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1923090
Title:
autopkgtest fails in hirsute on armhf
Status in firefox package in Ubuntu:
Confirmed
Bug description:
https://autopkgtest.ubuntu.com/packages/f/firefox/hirsute/armhf
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
hirsute/hirsute/armhf/f/firefox/20210408_154741_90187@/log.gz
...
autopkgtest [15:44:53]: test command3: [---
Traceback (most recent call last):
File "/tmp/autopkgtest.D3W44g/build.bPt/src/debian/tests/search-engines",
line 51, in
search URL for Google:
https://consent.google.com/ml?continue=https://www.google.com/search%3Fchannel%3Dfs%26client%3Dubuntu%26q%3Dfoobarbaz=GB=1=srp=en=1
assert url.netloc == v['netloc']
AssertionError
autopkgtest [15:45:08]: test command3: ---]
autopkgtest [15:45:11]: test command3: - - - - - - - - - - results - - - - -
- - - - -
command3 FAIL non-zero exit status 1
autopkgtest [15:45:12]: test command3: - - - - - - - - - - stderr - - - - -
- - - - -
Traceback (most recent call last):
File "/tmp/autopkgtest.D3W44g/build.bPt/src/debian/tests/search-engines",
line 51, in
assert url.netloc == v['netloc']
AssertionError
...
Most likely an infrastructure proxy/networking error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1923090/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220764] Re: Rhythmbox does not add VBR headers when ripping CDs to MP3
Still exists in 20.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1220764
Title:
Rhythmbox does not add VBR headers when ripping CDs to MP3
Status in rhythmbox package in Ubuntu:
Confirmed
Bug description:
When ripping CDs to MP3 using Rhythmbox, by default they are VBR,
because this is the default preset that is used in
/usr/share/gstreamer-0.10/presets/GstLameMP3Enc.prs (cbr=false). The
problem is that the VBR headers aren't added to the MP3 files, for
example:
$ mp3val 01\ -\ Gregory\ Alan\ Isakov\ -\ Dandelion\ Wine.mp3
Analyzing file "01 - Gregory Alan Isakov - Dandelion Wine.mp3"...
WARNING: "/home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern
Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3": VBR detected, but no
VBR header is present. Seeking may not work properly.
INFO: "/home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern
Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3": 9559 MPEG frames
(MPEG 1 Layer III), +ID3v2, no VBR header
Done!
This causes most programs to report incorrect track lengths, including
Rhythmbox itself and Ubuntu's default Nautilus file manager. This
seems to be a huge oversight considering this is the default behavior
using the default apps. I'm not sure when this started because I only
use the LTS versions of Ubuntu, but I know it wasn't a problem in
10.04, because it was using a gstreamer pipeline with xingmux as
opposed to gstreamer presets, which from what I understand don't
support xingmux (which I believe adds the VBR headers).
I currently have to fix any MP3s that I generate with Rhythmbox like
so:
sudo apt-get install vbrfix
cd /path/to/mp3s
find . -type f -iname '*.mp3' -exec vbrfix {} {} \;
rm vbrfix.log vbrfix.tmp
This bug is related to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/945987
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: rhythmbox-data 2.96-0ubuntu4.3 [modified:
usr/share/gstreamer-0.10/presets/GstLameMP3Enc.prs
usr/share/rhythmbox/rhythmbox.gep]
ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17
Uname: Linux 3.5.0-39-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Wed Sep 4 09:54:54 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-07-09 (12 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Package: rhythmbox 3.0.2-0ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Tags: trusty
Uname: Linux 3.13.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1220764/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923323] Re: Bluetooth will not stay OFF upon resume
Not sure if this is "normal" behavior, but #dbus-monitor --system "path=/org/bluez/hci0" returns some interesting output. When BT is shut-off using the Gnome Settings, an event stream is generated that appears to turn it off..., but at the end, seems to tell something, somewhere that it is on. Pasting from the relevant parts of the output: signal time=1618356308.901616 sender=:1.548 -> destination=(null destination) serial=237 path=/org/bluez/hci0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.bluez.Adapter1" array [ dict entry( string "Class" variant uint32 0 ) dict entry( string "Powered" variant boolean false ) dict entry( string "Discovering" variant boolean false ) ] array [ ] BUT THEN AT THE END OF THE EVENT STREAM... ethod call time=1618356308.915545 sender=:1.545 -> destination=:1.548 serial=148 path=/org/bluez/hci0; interface=org.freedesktop.DBus.Properties; member=Set string "org.bluez.Adapter1" string "Discoverable" variant boolean true method call time=1618356308.916566 sender=:1.545 -> destination=:1.548 serial=149 path=/org/bluez/hci0; interface=org.freedesktop.DBus.Properties; member=Set string "org.bluez.Adapter1" string "DiscoverableTimeout" variant uint32 0 method call time=1618356308.916586 sender=:1.545 -> destination=:1.548 serial=150 path=/org/bluez/hci0; interface=org.bluez.Adapter1; member=StartDiscovery method call time=1618356308.916591 sender=:1.155 -> destination=:1.548 serial=881 path=/org/bluez/hci0; interface=org.freedesktop.DBus.Properties; member=Set string "org.bluez.Adapter1" string "Powered" variant boolean true method call time=1618356308.916599 sender=:1.40 -> destination=:1.548 serial=509 path=/org/bluez/hci0; interface=org.freedesktop.DBus.Properties; member=Set string "org.bluez.Adapter1" string "Powered" variant boolean true -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume Status in gnome-settings-daemon package in Ubuntu: New Bug description: First: apologies for the possibly incorrect package assignment..., but "ubuntu-bug" required I select something. Second..., this is pasted from two postings I made in Ubuntu Forums... --- Thinkpad P15gen1, Ubuntu 20.04: Repeat-by: Enable BT using the top menu bar dropdown and connect with a BT speaker (a BT stereo adapter in this case). Play some music..., whatever. Disable BT using the top menu bar dropdown. Sleep the machine (close the lid). Note: machine is set to suspend and lock screen upon lid closure. Wake the machine (open the lid) and unlock screen. BT is enabled and connects even though it was disabled prior to suspend. Heh, the funny thing is that BT has been very reliable in every other way. How do I get BT to stay OFF when I turn it off? (..., and still have it turn on, and work, when I turn it on ). --- I've spent some time trying to characterize the problem. None of the settings related to power management seemed to relate to the BT failing to stay OFF problem, however..., along the way, I did find another interesting and perhaps related problem: The following setting: "Power"->"Power Saving"->"Bluetooth (Bluetooth can be turned off to save power)"->OFF/ON appears to duplicate the function of the "Bluetooth"->OFF/ON switch setting. They do the EXACT same thing. They mirror each other. E.g., when BT is turned on, the BT power save switch will be on. Turn BT off..., and the BT power save switch will turn off. Now..., turn BT back on, and then turn the BT power save switch off..., the entirety of BT will turn off..., EVEN if there is an active, running connection. Turn the BT power save switch back ON..., and BT will turn back ON. This is bogus. If the mapping of the GUI functionality to BT settings is broken, it's not a long stretch to think some other mapping or use/management of BT settings is broken as well..., especially since it's in the neighborhood of power management. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 10 12:08:47 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi
** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in Dash to dock: Fix Released Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: The syslog is full of these messages, continuously written all day long Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 0x56541fffb220 == Nov 25 07:46:42 pc1 gnome-shell[2980]: #0 7ffddbfa1940 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1839cb6a2420 @ 208) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 07:42:45 2020 InstallationDate: Installed on 2014-06-03 (2366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893101] Re: Thunderbird 78.02.0 Crashes
This is now fixed with the 78.9.1 snap so closing this bug ** Changed in: thunderbird (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1893101 Title: Thunderbird 78.02.0 Crashes Status in thunderbird package in Ubuntu: Fix Released Bug description: Thunderbird just segfaults and crashes on my system when i installed the .deb package --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bittin 4129 F pulseaudio /dev/snd/pcmC1D7p: bittin 4129 F...m pulseaudio /dev/snd/controlC0: bittin 4129 F pulseaudio /dev/snd/pcmC0D0p: bittin 4129 F...m pulseaudio BuildID: 20200821101218 CasperMD5CheckResult: skip Channel: release DistroRelease: Ubuntu 20.10 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-07-29 (28 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200729) IpRoute: default via 192.168.1.1 dev enp4s0 proto dhcp metric 100 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.158 metric 100 Locales: extensions.sqlite corrupt or missing NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thunderbird 1:78.2.0+build1-0ubuntu2 [origin: unknown] PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: /usr/lib/thunderbird/defaults/pref/vendor.js /usr/lib/thunderbird/defaults/pref/syspref.js /usr/lib/thunderbird/defaults/pref/channel-prefs.js prefs.js ProcEnviron: TERM=st-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/usr/bin/fish ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Profiles: Profile0 (Default) - LastVersion=68.10.0/20200629235513 (Out of date) RunningIncompatibleAddons: False Tags: third-party-packages groovy release-channel Themes: extensions.sqlite corrupt or missing Uname: Linux 5.4.0-42-generic x86_64 UnreportableReason: Det här är inte ett officiellt Ubuntu-paket. Ta bort eventuella tredjepartspaket och försök igen. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-Gaming5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-Gaming 5 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.blacklist.d.thunderbird: [deleted] modified.conffile..etc.apport.native-origins.d.thunderbird: [deleted] modified.conffile..etc.thunderbird.syspref.js: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1893101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923841] Re: [SRU] Increase recording quality
The attachment "alsa-utils_1.2.4-1ubuntu3.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in HWE Next: New Status in alsa-utils package in Ubuntu: New Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804333] Re: Cheese detects only low-res YUYV stream from camera
I think https://gitlab.gnome.org/GNOME/cheese/-/issues/28 "Cheese only uses video/x-raw formats, and not image/jpeg" better matches the heading of this issue, so I have added it as a tracked bug. It is fixed, but Ubuntu-20.04 is still affected. Live image with 21.04 fails to boot on the affected laptop (AMD Ryzen), so unsure concerning bug status in the latest distro. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1804333 Title: Cheese detects only low-res YUYV stream from camera Status in Cheese: Unknown Status in cheese package in Ubuntu: Triaged Bug description: Cheese v3.30.0 (3.30.0-0ubuntu1) Xubuntu 18.04 LTS Cheese detects and reports/offers/accesses ONLY the resolutions in the YUYV stream, index 1, which results in low-res video and especially (what I use the cam for) still images. Previously, in 16.04 LTS, everything was working perfectly with Cheese; for example, it offered and accessed the 3264x2448 stream, which is what I'd been using. >>> Currently, guvcview and VLC report/offer/access/display both streams and all resolutions perfectly. = ls /dev/video* /dev/video0 /dev/video1 = v4l2-ctl --list-formats-ext ioctl: VIDIOC_ENUM_FMT Index : 0 Type: Video Capture Pixel Format: 'MJPG' (compressed) Name: Motion-JPEG Size: Discrete 640x480 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 800x600 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 1024x768 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 1280x720 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 1600x1200 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 1920x1080 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 2048x1536 Interval: Discrete 0.067s (15.000 fps) Size: Discrete 2592x1944 Interval: Discrete 0.067s (15.000 fps) Size: Discrete 3264x1836 Interval: Discrete 0.067s (15.000 fps) Size: Discrete 3264x2448 Interval: Discrete 0.067s (15.000 fps) Index : 1 Type: Video Capture Pixel Format: 'YUYV' Name: YUYV 4:2:2 Size: Discrete 640x480 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 800x600 Interval: Discrete 0.040s (25.000 fps) Size: Discrete 1024x768 Interval: Discrete 0.067s (15.000 fps) Size: Discrete 1280x720 Interval: Discrete 0.100s (10.000 fps) Size: Discrete 1600x1200 Interval: Discrete 0.143s (7.000 fps) Size: Discrete 1920x1080 Interval: Discrete 0.200s (5.000 fps) = lsusb returns: Bus 007 Device 002: ID 1778:0221 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x1778 idProduct 0x0221 bcdDevice 10.21 iManufacturer 1 IPEVO Inc. iProduct2 IPEVO Ziggi-HD Plus iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 930 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Association: bLength 8 bDescriptorType11 bFirstInterface 0 bInterfaceCount 2 bFunctionClass 14 Video bFunctionSubClass 3 Video Interface Collection bFunctionProtocol 0 iFunction 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass14 Video bInterfaceSubClass 1 Video Control bInterfaceProtocol 0 iInterface
[Desktop-packages] [Bug 1921583] Re: Can't run System Monitor in Ubuntu Unity 21.04
A new iso of Ubuntu Unity 21.04 has been released today. After testing it i can confirm that System Monitor starts up fine. The issue is solved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1921583 Title: Can't run System Monitor in Ubuntu Unity 21.04 Status in Gnome System Monitor: Unknown Status in gnome-system-monitor package in Ubuntu: Fix Released Bug description: I can't run System Monitor in Ubuntu Unity 21.04. I reported a bug on Ubuntu Unity's tracker, but I've been told to report it here. https://gitlab.com/ubuntu-unity/ubuntu-unity- issues/-/issues/82#note_539356065 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-system-monitor 40.0-1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 27 15:32:16 2021 InstallationDate: Installed on 2021-03-27 (0 days ago) InstallationMedia: Ubuntu Unity 21.04 SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1921583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804333] Re: Cheese detects only low-res YUYV stream from camera
** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #28 https://gitlab.gnome.org/GNOME/cheese/-/issues/28 ** Also affects: cheese via https://gitlab.gnome.org/GNOME/cheese/-/issues/28 Importance: Unknown Status: Unknown ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1804333 Title: Cheese detects only low-res YUYV stream from camera Status in Cheese: Unknown Status in cheese package in Ubuntu: Triaged Bug description: Cheese v3.30.0 (3.30.0-0ubuntu1) Xubuntu 18.04 LTS Cheese detects and reports/offers/accesses ONLY the resolutions in the YUYV stream, index 1, which results in low-res video and especially (what I use the cam for) still images. Previously, in 16.04 LTS, everything was working perfectly with Cheese; for example, it offered and accessed the 3264x2448 stream, which is what I'd been using. >>> Currently, guvcview and VLC report/offer/access/display both streams and all resolutions perfectly. = ls /dev/video* /dev/video0 /dev/video1 = v4l2-ctl --list-formats-ext ioctl: VIDIOC_ENUM_FMT Index : 0 Type: Video Capture Pixel Format: 'MJPG' (compressed) Name: Motion-JPEG Size: Discrete 640x480 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 800x600 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 1024x768 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 1280x720 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 1600x1200 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 1920x1080 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 2048x1536 Interval: Discrete 0.067s (15.000 fps) Size: Discrete 2592x1944 Interval: Discrete 0.067s (15.000 fps) Size: Discrete 3264x1836 Interval: Discrete 0.067s (15.000 fps) Size: Discrete 3264x2448 Interval: Discrete 0.067s (15.000 fps) Index : 1 Type: Video Capture Pixel Format: 'YUYV' Name: YUYV 4:2:2 Size: Discrete 640x480 Interval: Discrete 0.033s (30.000 fps) Size: Discrete 800x600 Interval: Discrete 0.040s (25.000 fps) Size: Discrete 1024x768 Interval: Discrete 0.067s (15.000 fps) Size: Discrete 1280x720 Interval: Discrete 0.100s (10.000 fps) Size: Discrete 1600x1200 Interval: Discrete 0.143s (7.000 fps) Size: Discrete 1920x1080 Interval: Discrete 0.200s (5.000 fps) = lsusb returns: Bus 007 Device 002: ID 1778:0221 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x1778 idProduct 0x0221 bcdDevice 10.21 iManufacturer 1 IPEVO Inc. iProduct2 IPEVO Ziggi-HD Plus iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 930 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Association: bLength 8 bDescriptorType11 bFirstInterface 0 bInterfaceCount 2 bFunctionClass 14 Video bFunctionSubClass 3 Video Interface Collection bFunctionProtocol 0 iFunction 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass14 Video bInterfaceSubClass 1 Video Control bInterfaceProtocol 0 iInterface 0 VideoControl Interface Descriptor: bLength13
[Desktop-packages] [Bug 1866035] Re: [FFe] List and install OEM enablement packages
The grub2 work was descoped. ** Changed in: grub2 (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1866035 Title: [FFe] List and install OEM enablement packages Status in grub2 package in Ubuntu: Won't Fix Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: [ Description ] We have a project underway at the minute to install any hardware- specific tweaks that are needed for the currently running machine, and to select a different kernel on those machines: the OEM kernel. This requires changes in grub, ubiquity and ubuntu-drivers common. We'd like to land those changes. grub On a live session, construct a DMI modalias and match it against the packages on the CD to see if we need to boot the OEM kernel. ubuntu-drivers-common = List the oem-*meta packages which apply to the running machine, and install those with 'install'. ubiquity Use the information that ubuntu-drivers provides to show some UI if there is a matching package, and also install the package if the user selects it. [ Testing ] We have a package "oem-qemu-meta" in Focal which you can use to test this inn a VM. If you're using libvirt, edit the XML for a Focal VM and add In the section: Under : UBUNTUQEMUTEST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1866035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype
As well as in 20.10 (gnome-online-accounts 3.37.90-1ubuntu1). By the way, the upstream bug link is now https://gitlab.gnome.org/GNOME /gnome-online-accounts/-/issues/17 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #17 https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1703377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
@Daniel, u@u-HP-EliteDesk-800-G6-Tower-PC:~$ dpkg -S /usr/share/X11/xorg.conf.d/10-radeon.conf xserver-xorg-video-radeon: /usr/share/X11/xorg.conf.d/10-radeon.conf u@u-HP-EliteDesk-800-G6-Tower-PC:~$ dpkg -S /usr/share/X11/xorg.conf.d/10-amdgpu.conf xserver-xorg-video-amdgpu: /usr/share/X11/xorg.conf.d/10-amdgpu.conf The radeon and amdgpu drivers are came from xserver-xorg-video- radeon/amdgpu. xserver-xorg-video-radeon comes from xserver-xorg-video-ati xserver-xorg-video-ati and xserver-xorg-video-amdgpu comes from xserver-xorg-video-all Do you think we could remove both from xserver-xorg-video-all if the target is to use modesetting for amd gpu? Or anything I can do to help to fix it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: In Progress Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923841] Re: [SRU] Increase recording quality
debdiff for Focal ** Patch added: "alsa-utils_1.2.2-1ubuntu2.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1923841/+attachment/5487832/+files/alsa-utils_1.2.2-1ubuntu2.1.debdiff ** Tags added: oem-priority originate-from-1868034 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in HWE Next: New Status in alsa-utils package in Ubuntu: New Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923841] Re: [SRU] Increase recording quality
debdiff for Groovy ** Patch added: "alsa-utils_1.2.3-1ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1923841/+attachment/5487831/+files/alsa-utils_1.2.3-1ubuntu1.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in HWE Next: New Status in alsa-utils package in Ubuntu: New Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923841] Re: [SRU] Increase recording quality
debdiff for Hirsute ** Patch added: "alsa-utils_1.2.4-1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1923841/+attachment/5487830/+files/alsa-utils_1.2.4-1ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in HWE Next: New Status in alsa-utils package in Ubuntu: New Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1923841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923505] Re: thunderbird 78.9.0 FTBFS on ppc64el
Note that it's not just thunderbird 1:78.9.0+build2-0ubuntu3 in hirsute- proposed that is affected, rebuilding version 1:78.8.1+build1-0ubuntu1 in the release pocket hangs similarly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1923505 Title: thunderbird 78.9.0 FTBFS on ppc64el Status in thunderbird package in Ubuntu: Triaged Bug description: The build hangs forever when compiling the webrender rust crate (see https://launchpad.net/ubuntu/+source/thunderbird/1:78.9.0+build2-0ubuntu3/+build/21368163). I'm attaching the full build log for future reference. This happens when building with rustc 1.50.0+dfsg1+llvm-0ubuntu4 and 1.50.0+dfsg1+llvm-0ubuntu5 (the latter is the version currently in the hirsute release pocket). The build completes when building with rustc 1.50.0+dfsg1+llvm-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1923505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923840] [NEW] Xorg freeze
Public bug reported: After booting there is only a black screen showing a blinking _ in the top left corner. Nothing happens anymore. It only happens with Linux version 5.8.0-49-generic. Linux version 5.8.0-48-generic boots fine. Description:Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 14:25:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116 [GeForce GTX 1660 SUPER] [103c:8789] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87d6] InstallationDate: Installed on 2021-02-27 (45 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Pavilion Gaming Desktop TG01-1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2020 dmi.bios.release: 15.16 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.name: 87D6 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 103.9 dmi.modalias: dmi:bvnAMI:bvrF.10:bd11/19/2020:br15.16:efr103.9:svnHP:pnHPPavilionGamingDesktopTG01-1xxx:pvr:rvnHP:rn87D6:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Gaming Desktop TG01-1xxx dmi.product.sku: 27Y73EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923840 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: After booting there is only a black screen showing a blinking _ in the top left corner. Nothing happens anymore. It only happens with Linux version 5.8.0-49-generic. Linux version 5.8.0-48-generic boots fine. Description:Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM
[Desktop-packages] [Bug 1923841] [NEW] [SRU] Increase recording quality
Public bug reported: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] + https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1923841 Title: [SRU] Increase recording quality Status in alsa-utils package in Ubuntu: New Bug description: [Impact] Audio gets recorded by "arecord" has really bad sound quality when the volume is low. [Fix] https://github.com/alsa-project/alsa-utils/pull/69 Switch the default audio format from 8 bits to 16 bits if hardware supports it. [Test] 1. Plug a microphone. 2. Run `arecord | aplay` and say something to the microphone. 3. Only noise can be heard. With the fix applied, the recording is clear. [Where problems could occur] If there's any hardware falsely advertised to support 16 bits, this change will break them. However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so that's not likely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1923841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923602] Re: Sound "Output" level shows input level
As suggested in #2, I reported a bug upstream:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1324
I corrected the screenshot.
This ticket may be now closed.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1324
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1324
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1923602
Title:
Sound "Output" level shows input level
Status in gnome-control-center package in Ubuntu:
New
Bug description:
In sound setting in the "Output" section there is a dashed line that I
suppose should be the current output level. Instead, it shows input
level, just like the line in the "Input" section.
Clap your hands next to the microphone, and you will see both lines
moving.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 13 12:46:54 2021
InstallationDate: Installed on 2021-04-08 (5 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RebootRequiredPkgs: network-manager
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923602/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923817] Re: The balsa/armhf tests are failing with the hirsute-proposed update
** Changed in: webkit2gtk (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1923817
Title:
The balsa/armhf tests are failing with the hirsute-proposed update
Status in webkit2gtk package in Ubuntu:
Confirmed
Bug description:
The update is failing the balsa tests for some reason.
The failure can be reproduced on ubuntu/ubuntu-hirsute-daily-
arm64-server-20201125-disk1.img small instance on canonistack
$ autopkgtest-build-lxd images:ubuntu/hirsute/armhf
$ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-upgrade
balsa -- lxd autopkgtest/ubuntu/hirsute/armhf
starting the tests manually in the shell opened after failure it
success though...
Getting the balsa source and editing debian/tests/screenshot to add
some debug output
xvfb-run bash -c 'NO_AT_BRIDGE=1 balsa --check-mail & sleep 15 ;
xwininfo -tree -root; xwd -root | gm convert - /tmp/debug.png; xwd
-name balsa | gm convert - /tmp/lower.png; xwd -debug -name Balsa | gm
convert - $workdir/current.png; killall balsa; wait %1; true'
$ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-
upgrade . --no-built-binaries -- lxd autopkgtest/ubuntu/hirsute/armhf
gives
'working directory: /tmp/autopkgtest.Uzr6TF/screenshot-artifacts
xwininfo: Window id: 0x50e (the root window) (has no name)
Root window id: 0x50e (the root window) (has no name)
Parent window id: 0x0 (none)
1 child:
0x21 "balsa": ("balsa" "Balsa") 10x10+10+10 +10+10
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73 (X_GetImage)
Serial number of failed request: 22
Current serial number in output stream: 22
gm convert: Improper image header (/tmp/gmea3yq0).
xwd: error: No window with name Balsa exists!
gm convert: Improper image header (/tmp/gmH5TBcq).
gm compare: Request did not return an image.
autopkgtest [09:50:24]: test screenshot: ---]
autopkgtest [09:50:25]: test screenshot: - - - - - - - - - - results - - - -
- - - - - -
screenshot FAIL non-zero exit status 1
'
doing a ssh -X to the instance it seems to start the right dialog...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1923817/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923714] Re: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1
I would suspect that the universe packages of groovy-proposed are not included by the sources lists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1923714 Title: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 Status in libreoffice package in Ubuntu: Incomplete Bug description: Among other, package *libreoffice* 7.0.5-0ubunt0.20.10.1 is missing in the *groovy-proposed* archives. ``` $ more /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-poli cy" VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy $ apt list --upgradable Listing... Done libreoffice-base-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-calc/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-draw/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gnome/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gtk3/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-impress/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-math/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-writer/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] python3-uno/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] ``` ``` $ apt-cache policy libreoffice-math libreoffice-math: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.5-0ubuntu0.20.10.1 Version table: 1:7.0.5-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com groovy-proposed/main ppc64el Packages *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/main ppc64el Packages $ apt-cache policy libreoffice libreoffice: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.3-0ubuntu0.20.10.1 Version table: *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/universe ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/universe ppc64el Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1923714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 923176]
I don't understand, why tooltip text should honour formatting. Design team: please weigh in on this. Seems like WONTFIX material. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/923176 Title: [Upstream] Footnote Tooltip not honoring Footnote formatting Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages LibreOffice Writer 3.4.5 OOO340m1 (Build:502) 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923176/+attachment/2700678/+files/Untitled%201.odt -O example.odt && lowriter -nologo example.odt place the mouse cursor over the footnote link and the tooltip honors the footnote formatting. 4) What happens instead is the formatting is not honored. A screenshot of this may be found at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923176/+attachment/2699118/+files/footnotebug.png . To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/923176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923602] Re: Sound "Output" level shows input level
No, pavucontrol doesn't have the same issue, but it has something else:
HDMI / DisplayPort 3 (plugged in) shows output level correctly, but
Digital Output (S/PDIF) doesn't move output level at all. (I do switch
output in system settings).
** Attachment added: "Screenshot from 2021-04-14 12-01-51.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923602/+attachment/5487728/+files/Screenshot%20from%202021-04-14%2012-01-51.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1923602
Title:
Sound "Output" level shows input level
Status in gnome-control-center package in Ubuntu:
New
Bug description:
In sound setting in the "Output" section there is a dashed line that I
suppose should be the current output level. Instead, it shows input
level, just like the line in the "Input" section.
Clap your hands next to the microphone, and you will see both lines
moving.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 13 12:46:54 2021
InstallationDate: Installed on 2021-04-08 (5 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RebootRequiredPkgs: network-manager
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923602/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923817] [NEW] The balsa/armhf tests are failing with the hirsute-proposed update
Public bug reported:
The update is failing the balsa tests for some reason.
The failure can be reproduced on ubuntu/ubuntu-hirsute-daily-
arm64-server-20201125-disk1.img small instance on canonistack
$ autopkgtest-build-lxd images:ubuntu/hirsute/armhf
$ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-upgrade
balsa -- lxd autopkgtest/ubuntu/hirsute/armhf
starting the tests manually in the shell opened after failure it success
though...
Getting the balsa source and editing debian/tests/screenshot to add some
debug output
xvfb-run bash -c 'NO_AT_BRIDGE=1 balsa --check-mail & sleep 15 ;
xwininfo -tree -root; xwd -root | gm convert - /tmp/debug.png; xwd -name
balsa | gm convert - /tmp/lower.png; xwd -debug -name Balsa | gm convert
- $workdir/current.png; killall balsa; wait %1; true'
$ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-
upgrade . --no-built-binaries -- lxd autopkgtest/ubuntu/hirsute/armhf
gives
'working directory: /tmp/autopkgtest.Uzr6TF/screenshot-artifacts
xwininfo: Window id: 0x50e (the root window) (has no name)
Root window id: 0x50e (the root window) (has no name)
Parent window id: 0x0 (none)
1 child:
0x21 "balsa": ("balsa" "Balsa") 10x10+10+10 +10+10
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73 (X_GetImage)
Serial number of failed request: 22
Current serial number in output stream: 22
gm convert: Improper image header (/tmp/gmea3yq0).
xwd: error: No window with name Balsa exists!
gm convert: Improper image header (/tmp/gmH5TBcq).
gm compare: Request did not return an image.
autopkgtest [09:50:24]: test screenshot: ---]
autopkgtest [09:50:25]: test screenshot: - - - - - - - - - - results - - - - -
- - - - -
screenshot FAIL non-zero exit status 1
'
doing a ssh -X to the instance it seems to start the right dialog...
** Affects: webkit2gtk (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1923817
Title:
The balsa/armhf tests are failing with the hirsute-proposed update
Status in webkit2gtk package in Ubuntu:
New
Bug description:
The update is failing the balsa tests for some reason.
The failure can be reproduced on ubuntu/ubuntu-hirsute-daily-
arm64-server-20201125-disk1.img small instance on canonistack
$ autopkgtest-build-lxd images:ubuntu/hirsute/armhf
$ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-upgrade
balsa -- lxd autopkgtest/ubuntu/hirsute/armhf
starting the tests manually in the shell opened after failure it
success though...
Getting the balsa source and editing debian/tests/screenshot to add
some debug output
xvfb-run bash -c 'NO_AT_BRIDGE=1 balsa --check-mail & sleep 15 ;
xwininfo -tree -root; xwd -root | gm convert - /tmp/debug.png; xwd
-name balsa | gm convert - /tmp/lower.png; xwd -debug -name Balsa | gm
convert - $workdir/current.png; killall balsa; wait %1; true'
$ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-
upgrade . --no-built-binaries -- lxd autopkgtest/ubuntu/hirsute/armhf
gives
'working directory: /tmp/autopkgtest.Uzr6TF/screenshot-artifacts
xwininfo: Window id: 0x50e (the root window) (has no name)
Root window id: 0x50e (the root window) (has no name)
Parent window id: 0x0 (none)
1 child:
0x21 "balsa": ("balsa" "Balsa") 10x10+10+10 +10+10
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73 (X_GetImage)
Serial number of failed request: 22
Current serial number in output stream: 22
gm convert: Improper image header (/tmp/gmea3yq0).
xwd: error: No window with name Balsa exists!
gm convert: Improper image header (/tmp/gmH5TBcq).
gm compare: Request did not return an image.
autopkgtest [09:50:24]: test screenshot: ---]
autopkgtest [09:50:25]: test screenshot: - - - - - - - - - - results - - - -
- - - - - -
screenshot FAIL non-zero exit status 1
'
doing a ssh -X to the instance it seems to start the right dialog...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1923817/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923602] Re: Sound "Output" level shows input level
Thank you for your bug report. It's not doing that here (and your
screenshot doesn't show an orange bar for output?). Anyway, it might be
specific to the devices selected, it would probably made sense if you or
someone seeing the issue was reporting it directly upstream on
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1923602
Title:
Sound "Output" level shows input level
Status in gnome-control-center package in Ubuntu:
New
Bug description:
In sound setting in the "Output" section there is a dashed line that I
suppose should be the current output level. Instead, it shows input
level, just like the line in the "Input" section.
Clap your hands next to the microphone, and you will see both lines
moving.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 13 12:46:54 2021
InstallationDate: Installed on 2021-04-08 (5 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RebootRequiredPkgs: network-manager
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923602/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923602] Re: Sound "Output" level shows input level
If you try pavucontrol does it have the same issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1923602
Title:
Sound "Output" level shows input level
Status in gnome-control-center package in Ubuntu:
New
Bug description:
In sound setting in the "Output" section there is a dashed line that I
suppose should be the current output level. Instead, it shows input
level, just like the line in the "Input" section.
Clap your hands next to the microphone, and you will see both lines
moving.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 13 12:46:54 2021
InstallationDate: Installed on 2021-04-08 (5 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RebootRequiredPkgs: network-manager
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923602/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923718] Re: Can't rename bookmarks in Nautilus
Thank you for your bug report. Is it doing the same for local ones? To which kind of server are the remote pointing? is the share mounted when you try to rename? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1923718 Title: Can't rename bookmarks in Nautilus Status in nautilus package in Ubuntu: New Bug description: In Nautilus File Manager, when trying to rename the bookmark of a (remote) directory through the context menu, the "rename" option is not clickable. Instead the click activates the option to drag the entry of the bookmark to a different position. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 08:00:42 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 763)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-02 (70 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1923718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923714] Re: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1
libreoffice 1:7.0.5-0ubuntu0.20.10.1 was successfully built and published for ppc64el in groovy-proposed: https://launchpad.net/ubuntu/+source/libreoffice/1:7.0.5-0ubuntu0.20.10.1/+build/21369469 Could it be a problem with the German mirror? If you run "apt update" now, has this changed? ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1923714 Title: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 Status in libreoffice package in Ubuntu: Incomplete Bug description: Among other, package *libreoffice* 7.0.5-0ubunt0.20.10.1 is missing in the *groovy-proposed* archives. ``` $ more /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-poli cy" VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy $ apt list --upgradable Listing... Done libreoffice-base-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-calc/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-draw/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gnome/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gtk3/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-impress/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-math/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-writer/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] python3-uno/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] ``` ``` $ apt-cache policy libreoffice-math libreoffice-math: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.5-0ubuntu0.20.10.1 Version table: 1:7.0.5-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com groovy-proposed/main ppc64el Packages *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/main ppc64el Packages $ apt-cache policy libreoffice libreoffice: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.3-0ubuntu0.20.10.1 Version table: *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/universe ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/universe ppc64el Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1923714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
Recent Bug 1922942 made me aware that this is again showing up in recent versions. Kubuntu 21.04 shows very similar symptoms, but non-KDE systems seem not affected at all. I was able to use it without any trouble on gnome based Ubuntus (Host and Guest). Does any of the involved/subscribed people have a good idea why this might be different for KDE guests? @All - have you recently tried mixed combinations yet of either Host or Guest being non-KDE - What was the result of that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-gtk package in Ubuntu: Fix Released Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-gtk source package in Focal: Triaged Status in spice-protocol source package in Focal: Triaged Status in spice-vdagent source package in Focal: Invalid Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions
Thanks, closing the current serie target then and it means it's ready for sponsoring, I will work on that today or tomorrow ** Changed in: libwacom (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1921991 Title: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions Status in OEM Priority Project: Triaged Status in libwacom package in Ubuntu: Fix Released Bug description: [Impact] * There are lots of stylus couldn't be used on Lenovo's platform, our OEM customer request to support ThinkPad P15 Gen 1, ThinkPad X1 Yoga Gen5, ThinkPad P1 G3. * I reviewed and tested the below patches from upstream. It could support the stylus very well on P15, P1 or X1 Yoga. * a864679 - Add multiple AES stylus definitions I applied into libwacom2 1.3-2ubuntu1, no errors. * 8652aa3 - Add isdv4-aes stylus group to all AES sensors I tried to apply this patch, but there are not 'data/isdv4-48ca.tablet' and 'data/isdv4-48ce.tablet', it failed for these two files. * ba02abf - Add ISDv4 51e9 (Lenovo ThinkPad P15 Gen 1) (#325) [Test Plan] * Need your laptop have AES stylus, check the pen setting at gnome- control-center when the pen touch the screen. It could not set/customize the stylus, such as the second button as right click. * After updated the new packages with these patches, you could customize the stylus at gnome-control-center. [Where problems could occur] * It only changes the data/ parts to support more stylus from upstream, so it's low risk. [Other Info] * Related bug: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914230] Re: On-screen keyboard for Japanese doesn't display Japanese characters, only English
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed ** Tags added: fixed-in-3.38.5 fixed-in-40.1 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914230 Title: On-screen keyboard for Japanese doesn't display Japanese characters, only English Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: This is about touch keyboard. Screen keyboard doesn't display other languages characters, only english characters. I noticed many users concern about that on forums To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1914230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923431] Re: Chrome/Chromium is composited slower without "system title bar and borders"
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1754 https://gitlab.gnome.org/GNOME/mutter/-/issues/1754 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1754 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => Triaged ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1923431 Title: Chrome/Chromium is composited slower without "system title bar and borders" Status in Mutter: Unknown Status in chromium-browser package in Ubuntu: New Status in mutter package in Ubuntu: Triaged Bug description: Chrome/Chromium is composited slower without "system title bar and borders". I had a feeling I could see a difference on my 4K monitor and weak Intel GPU. Enabling "Use system title bar and borders" eliminated stutters and gave me a smoother experience. So now I've taken some measurements from gnome-shell (CLUTTER_SHOW_FPS=1) running Chromium, not stuttering but playing a smoothly rendered video: --- Xorg Use system title bar and borders ON: *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms Use system title bar and borders OFF: *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms --- Xwayland Use system title bar and borders ON: *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms Use system title bar and borders OFF: *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms *** DP-2 frame timings over 1.0s: 59.99 FPS, average: 1.3ms, peak: 2.5ms To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1923431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923718] [NEW] Can't rename bookmarks in Nautilus
Public bug reported: In Nautilus File Manager, when trying to rename the bookmark of a (remote) directory through the context menu, the "rename" option is not clickable. Instead the click activates the option to drag the entry of the bookmark to a different position. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 08:00:42 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 763)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-02 (70 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Screenshot showing the context menu after clicking on "rename"" https://bugs.launchpad.net/bugs/1923718/+attachment/5487662/+files/Screenshot%20from%202021-04-14%2008-16-22.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1923718 Title: Can't rename bookmarks in Nautilus Status in nautilus package in Ubuntu: New Bug description: In Nautilus File Manager, when trying to rename the bookmark of a (remote) directory through the context menu, the "rename" option is not clickable. Instead the click activates the option to drag the entry of the bookmark to a different position. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 08:00:42 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 763)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-02 (70 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1923718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923714] [NEW] groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1
Public bug reported: Among other, package *libreoffice* 7.0.5-0ubunt0.20.10.1 is missing in the *groovy-proposed* archives. ``` $ more /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-poli cy" VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy $ apt list --upgradable Listing... Done libreoffice-base-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-calc/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-draw/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gnome/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gtk3/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-impress/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-math/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-writer/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] python3-uno/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] ``` ``` $ apt-cache policy libreoffice-math libreoffice-math: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.5-0ubuntu0.20.10.1 Version table: 1:7.0.5-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com groovy-proposed/main ppc64el Packages *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/main ppc64el Packages $ apt-cache policy libreoffice libreoffice: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate: 1:7.0.3-0ubuntu0.20.10.1 Version table: *** 1:7.0.3-0ubuntu0.20.10.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy-updates/universe ppc64el Packages 100 /var/lib/dpkg/status 1:7.0.2-0ubuntu1 500 500 http://de.ports.ubuntu.com/ubuntu-ports groovy/universe ppc64el Packages ``` ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Summary changed: - ppc64le: Unable to upgrade + groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1923714 Title: groovy-proposed: Unable to upgrade to 7.0.5-0ubunt0.20.10.1 Status in libreoffice package in Ubuntu: New Bug description: Among other, package *libreoffice* 7.0.5-0ubunt0.20.10.1 is missing in the *groovy-proposed* archives. ``` $ more /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-poli cy" VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy $ apt list --upgradable Listing... Done libreoffice-base-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-calc/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-core/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-draw/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gnome/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-gtk3/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-impress/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-math/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] libreoffice-writer/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] python3-uno/groovy-proposed 1:7.0.5-0ubuntu0.20.10.1 ppc64el [upgradable from: 1:7.0.3-0ubuntu0.20.10.1] ``` ``` $ apt-cache policy libreoffice-math libreoffice-math: Installed: 1:7.0.3-0ubuntu0.20.10.1 Candidate:
[Desktop-packages] [Bug 1919927] Proposed package upload rejected
An upload of gnome-shell-extension-appindicator to focal-proposed has been rejected from the upload queue for the following reason: "Please re-upload without the icon-patch + patch reverting the icon-patch in debian/patches. Otherwise looks ok.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1919927 Title: Wrong (or no) signals are emitted when icons are added / removed Status in gnome-shell-extension-appindicator package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator source package in Focal: In Progress Bug description: [ Impact ] When adding and removing signals the indicators extension should emit signals following the protocol https://www.freedesktop.org/wiki/Specifications/StatusNotifierItem/StatusNotifierWatcher/ So we should emit the service name by default when known [ Test case ] Run dbus-monitor --session "interface='org.kde.StatusNotifierWatcher'" When an indicator is added, signals such as should be emitted: signal time=1616029764.911986 sender=:1.34490 -> destination=(null destination) serial=3905 path=/StatusNotifierWatcher; interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered string ":1.109/org/ayatana/NotificationItem/psensor" signal time=1616029764.928864 sender=:1.34490 -> destination=(null destination) serial=3991 path=/StatusNotifierWatcher; interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered string ":1.34459/StatusNotifierItem" When removed: signal time=1616033768.529066 sender=:1.34490 -> destination=(null destination) serial=8711 path=/StatusNotifierWatcher; interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemUnregistered string ":1.34649/StatusNotifierItem" Removed events should be also emitted when the extension is disabled via gnome-shell-extension-prefs [ Regression potential ] Some clients won't interpret the events correctly causing the indicator not to work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1919927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905370] Proposed package upload rejected
An upload of gnome-shell-extension-appindicator to focal-proposed has been rejected from the upload queue for the following reason: "Please re-upload without the icon-patch + patch reverting the icon-patch in debian/patches. Otherwise looks ok.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1905370 Title: Qt-based tray icons not displayed on start-up Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Confirmed Status in gnome-shell-extension-appindicator source package in Groovy: Won't Fix Status in gnome-shell-extension-appindicator source package in Hirsute: Fix Released Bug description: [ Impact ] My system version is 20.10. I upgraded from 20.04. I found such a problem, the tray icon cannot be displayed when the system is turned on or restarted, but if I kill the process and restart it, it will be fine. I searched on Google and didn't see a similar problem.This is my hardware configuration: CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56 GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 [GeForce 1060] https://i.stack.imgur.com/ybiVj.png [ Test case ] - Install a Qt app with a tray icon that should show on startup - At login the icon should be visible. An example is hp-systray, from the package hplip-gui: - Add it to the autostart (if you don't have HP printers just add the command `hp-systray -x`). Expect the icon to show [ Regression Potential ] No status icon service is ever initialized by the shell and so no app indicator is visible. ProblemType: BugDistroRelease: Ubuntu 20.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 16:34:31 2020 InstallationDate: Installed on 2020-10-24 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-generic linux-baseSourcePackage: meta-gnome3 UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1919924] Proposed package upload rejected
An upload of gnome-shell-extension-appindicator to focal-proposed has been rejected from the upload queue for the following reason: "Please re-upload without the icon-patch + patch reverting the icon-patch in debian/patches. Otherwise looks ok.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1919924 Title: Scrolling on label doesn't work Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Committed Status in gnome-shell-extension-appindicator source package in Focal: In Progress Bug description: [ Impact ] Scrolling on indicator label doesn't cause the scroll appindicator event to be emitted [ Test case ] Using the appindicator test tool: https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js 1. Run it with gjs 2. Show a label 3. Ensure that scroll events are printed in the terminal and that the icon is changed [ Regression potential ] Scroll events on icon doesn't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1919924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
