[Desktop-packages] [Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell
The bug persists with accented characters if the dead key is the first character you type. I mean, open the overview, type "á" and you see just "a". Then type another "á" and it shows correctly. Same if you type "lá", the accent shows correctly because the dead key wasn't the first thing you typed. -- 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/1900906 Title: Can't use dead keys or input e.g. Chinese characters in GNOME shell Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. Under X, if I try to input an accentuated character, such as á or ü, in places like the search field in the overview or when writing a folder name in the app grid, nothing appears. Under Wayland, it fails each time on the first input of an accentuated character, then it works. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-01 (174 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Package: ibus PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago) UserGroups: sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1900906/+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 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
same issues happened on my ASUS Zephyrus M. i think it's alc294's problem. as Ian Choy (iancmx) mentioned, 0x21 set as headphone that laptop could detect the headphone when you plug in, but no sound comes from headphone ubunutu 20.04lts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+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 1873052] Re: Showing two cursors after login
The bug's still present, but the fix in #7 works for me too. "as workaround editing /etc/gdm3/custom.conf to uncomment `WaylandEnable=false` should fix this" -- 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/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+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 1912040] [NEW] no driver for HP Laser MFP 135a
Public bug reported: I installed CUPS on Ubuntu based OS (Raspbian) but it does not work with HP Laser MFP 135a apparently it needs ULD drivers. I'm not familiar with CUPS or Printer drivers for that matter so I'm not sure why CUPS does not work with IPP- over-USB printers out of the box lsusb -v | grep -A 3 bInterfaceClass.*7 Couldn't open device, some information will be missing bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 Couldn't open device, some information will be missing -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 Couldn't open device, some information will be missing Couldn't open device, some information will be missing ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1912040 Title: no driver for HP Laser MFP 135a Status in cups package in Ubuntu: New Bug description: I installed CUPS on Ubuntu based OS (Raspbian) but it does not work with HP Laser MFP 135a apparently it needs ULD drivers. I'm not familiar with CUPS or Printer drivers for that matter so I'm not sure why CUPS does not work with IPP-over-USB printers out of the box lsusb -v | grep -A 3 bInterfaceClass.*7 Couldn't open device, some information will be missing bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 Couldn't open device, some information will be missing -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 Couldn't open device, some information will be missing Couldn't open device, some information will be missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1912040/+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 1762397] Re: gnome-shell-extension-prefs crashed with SIGSEGV in gtk_container_real_check_resize()
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1762397 Title: gnome-shell-extension-prefs crashed with SIGSEGV in gtk_container_real_check_resize() Status in gnome-shell package in Ubuntu: Expired Bug description: It was a bit delayed but I think this probably relates to extension gnome-display-switcher, which is probably in need of an update. The configuration dialogue was failing to open either from the extensions site or the tweak-tool extensions tab... then this error appeared. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 12:57:42 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell-extension-prefs InstallationDate: Installed on 2017-08-07 (244 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell-extension-prefs extension:///display-switc...@lucas.diedrich.gmail.com ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6c4aa381c9:callq 0x7f6c4ac54380 PC (0x7f6c4aa381c9) ok source "0x7f6c4ac54380" (0x7f6c4ac54380) ok destination "(%rsp)" (0x7ffc1a53bff0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell-extension-prefs crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to bionic on 2018-03-10 (29 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762397/+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 1769695] Re: Freeze of Surface for 2 Minutes
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1769695 Title: Freeze of Surface for 2 Minutes Status in gnome-shell package in Ubuntu: Expired Bug description: I am using a fresh installed Ubuntu 18.04 on an RX 480 and an i5 7600. 3.28.0-0ubuntu1 is running. Normaly, everything runs fine, but lately when I had some windows open (eclipse, Texmaker, Terminal, Firefox with Youtube and other windows) the system suddenly was nearly frozen, I could move the mouse and change active windows by ctrl+tab but not use the keyboard e.g. for typing into windows or make any actions with the mouse (e.g. open menues, click on menues, ..). When I changed the session by Ctrl+Alt+F3 and then killed firefox, everything worked again. I do not know whether this is a Firefox, a gdm or a graphics driver issue. Since a program should not be able to make the desktop crash at all, I suppose its not Firefox and so I post it here. /var/log/syslog around the time contains the following (even if it contains some device removed code, I did not do anything with the cables and am sure that there isn't a hardware defect with mouse and keyboard): May 7 17:27:40 reichelt-desktop nautilus[3278]: Called "net usershare info" but it failed: Kindprozess »net« konnte nicht ausgeführt werden (No such file or directory) May 7 17:27:53 reichelt-desktop java[11096]: gtk_widget_size_allocate(): attempt to allocate widget with width 12 and height -12 May 7 17:27:53 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar May 7 17:27:53 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton May 7 17:27:53 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton May 7 17:27:53 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4402269 (Run Config) May 7 17:27:54 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton May 7 17:28:15 reichelt-desktop java[11096]: message repeated 2 times: [ gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton] May 7 17:28:18 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x44002d3 (dissworksp) May 7 17:28:18 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4403e58 (Open Resou) May 7 17:28:20 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x44002d3 (dissworksp) May 7 17:28:22 reichelt-desktop java[11096]: gtk_widget_size_allocate(): attempt to allocate widget with width 12 and height -12 May 7 17:28:22 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar May 7 17:28:22 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton May 7 17:28:22 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton May 7 17:28:22 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4404745 (Run Config) May 7 17:28:23 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton May 7 17:28:25 reichelt-desktop java[11096]: message repeated 2 times: [ gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton] May 7 17:28:26 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4405147 (Confirm La) May 7 17:28:27 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4404745 (Run Config) May 7 17:28:27 reichelt-desktop java[11096]: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton May 7 17:29:31 reichelt-desktop java[11096]: message repeated 5 times: [ gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton] May 7 17:29:34 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x44002d3 (dissworksp) May 7 17:29:35 reichelt-desktop
[Desktop-packages] [Bug 1795108] Re: Using the super key spams the syslog with St.Bin has been already deallocated in workspaceThumbnail.js
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1795108 Title: Using the super key spams the syslog with St.Bin has been already deallocated in workspaceThumbnail.js Status in gnome-shell package in Ubuntu: Expired Bug description: All extensions are disabled. All gnome-shell extensions, if enabled, do severe spamming of the syslog. Most errors are related to "st.bin" and/or "st.whatever" has been already deallocated. I.e., at least six popular extensions experience similar crashes after software updates in gnome. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Packages uname -a Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin (0x563811418000), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: == Stack trace for context 0x56380fde1330 == Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #0 0x7ffc8c0b3dd0 b resource:///org/gnome/shell/ui/workspaceThumbnail.js:974 (0x7f8003cf6560 @ 439) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #1 0x7ffc8c0b4ad0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #2 0x56381018ec28 i resource:///org/gnome/shell/ui/workspaceThumbnail.js:884 (0x7f8003cf62b8 @ 390) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #3 0x7ffc8c0b56c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #4 0x7ffc8c0b5780 b self-hosted:916 (0x7f80200f12b8 @ 367) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #5 0x7ffc8c0b5870 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f80200d2230 @ 386) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #6 0x56381018eb90 i resource:///org/gnome/shell/ui/overview.js:568 (0x7f8003ecf890 @ 324) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #7 0x7ffc8c0b64c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #8 0x56381018eb10 i resource:///org/gnome/shell/ui/overview.js:540 (0x7f8003ecf808 @ 109) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #9 0x7ffc8c0b70a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #10 0x56381018ea90 i resource:///org/gnome/shell/ui/overview.js:670 (0x7f8003ecfb38 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #11 0x7ffc8c0b7c80 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #12 0x56381018ea10 i resource:///org/gnome/shell/ui/main.js:197 (0x7f80200da3c8 @ 39) Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin (0x563811418000), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: == Stack trace for context 0x56380fde1330 == Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #0 0x56381018eb70 i resource:///org/gnome/shell/ui/workspaceThumbnail.js:1231 (0x7f8003cf8120 @ 739) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #1 0x7ffc8c0b11a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #2 0x7ffc8c0b1280 b self-hosted:920 (0x7f80200f12b8 @ 428) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #3 0x56381018eaa8 i resource:///org/gnome/shell/ui/overviewControls.js:76 (0x7f8003ecfe68 @ 521) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #4 0x7ffc8c0b3430 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #5 0x7ffc8c0b57a0 b
[Desktop-packages] [Bug 1874299] Re: PC crashes / freezes when removing application icons in created folders
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1874299 Title: PC crashes / freezes when removing application icons in created folders Status in gnome-shell package in Ubuntu: Expired Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: The computer freezes / freezes when several app icons are removed from a created folder, it is necessary to manually disconnect to get back to work. Update I: Bug reproduction: https://streamable.com/mzd6th Resolution: 16:9 (1366x768) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-08-13 (253 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874299/+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 1874299] Re: PC crashes / freezes when removing application icons in created folders
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- 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/1874299 Title: PC crashes / freezes when removing application icons in created folders Status in gnome-shell package in Ubuntu: Expired Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: The computer freezes / freezes when several app icons are removed from a created folder, it is necessary to manually disconnect to get back to work. Update I: Bug reproduction: https://streamable.com/mzd6th Resolution: 16:9 (1366x768) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-08-13 (253 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874299/+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 1904344] Re: Libreoffice window becomes unstable for one or two seconds when it opens
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- 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/1904344 Title: Libreoffice window becomes unstable for one or two seconds when it opens Status in libreoffice package in Ubuntu: Expired Bug description: Every time I open Libreoffice Writer in Ubuntu 20.04, the window of the application becomes unstable for one or two seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904344/+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 1903777] Re: Screen resolution falls back to default (low res) under Ubuntu Budgie 20.10 (Intel/Nvidia)
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1903777 Title: Screen resolution falls back to default (low res) under Ubuntu Budgie 20.10 (Intel/Nvidia) Status in mutter package in Ubuntu: Expired Bug description: Fresh install of Budgie 20.10. Things work normally, but after a reboot the screen resolution goes down to something like 1024x768 (from 1440p) and won't go back. Can't be selected in GUI, grayed out. Issuing a "sudo systemctl restart display-manager" will get things back to 1440p, but kills all my windows etc. Using the latest NVIDIA driver, although this also happened under the previous one. Description: Ubuntu 20.10 Release: 20.10 x@x:~$ apt-cache policy libmutter-7-0 libmutter-7-0: Installed: 3.38.1-1ubuntu1 Candidate: 3.38.1-1ubuntu1 Version table: *** 3.38.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libmutter-7-0 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Nov 10 21:53:32 2020 InstallationDate: Installed on 2020-10-23 (18 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903777/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
I installed the focal-proposed updates yesterday, just checked and I can confirm the background corruption issue is still there, tho it's not as much as before. Before it used to change to a complete grey static, but now the wallpaper is still visible to an extent. I'll attach a screenshot. ** Attachment added: "Screenshot from 2021-01-16 09-44-49.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+attachment/5453618/+files/Screenshot%20from%202021-01-16%2009-44-49.png -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1911934] Re: SRU the current 3.38 stable update
This bug was fixed in the package gnome-desktop3 - 3.38.3-1ubuntu1 --- gnome-desktop3 (3.38.3-1ubuntu1) hirsute; urgency=medium * Merge with Debian. Remaining changes (lp: #1911934) - Add 04_compute_average_color.patch: Compute the avergage color in gnome-desktop itself, not in unity to fix some races (LP #963140) - Add tweak_color_computation.patch, Patch from Gord, no patch header, no bug link. - Add git_revert_draw_background.patch - Add ubuntu_language_list_from_SUPPORTED.patch, Add API to get list of available languages from SUPPORTED file. To be used by gnome 3.8 region panel language installation. - debian/control.in: Build-Depend on language-pack-gnome-he for build tests - debian/libgnome-desktop-3-18.symbols: + Add symbols included in Ubuntu patches gnome-desktop3 (3.38.3-1) unstable; urgency=medium * Team upload * New upstream release - Translation updates gnome-desktop3 (3.38.2-1) unstable; urgency=medium * Team upload * New upstream release - Translation updates * Drop patch for Hebrew translation, applied upstream * Preferentially build-depend on libgdk-pixbuf-2.0-dev. We don't need the deprecated Xlib integration that is also pulled in by the older libgdk-pixbuf2.0-dev package (see #974870). * Standards-Version: 4.5.1 (no changes required) * Backport support for user-specific XKB configuration. This uses the new libxkbregistry to load XKB configuration, instead of parsing it directly, which means we can have per-user keyboard layouts in Wayland sessions (analogous to Xmodmap). (Closes: #974056) gnome-desktop3 (3.38.1-2) unstable; urgency=medium * Team upload * run-with-locales: Use UTF-8 for *.utf8 locales * d/run-with-locales: Move to d/tests/ This improves tab-completion for d/rules. * d/p/Update-Hebrew-translation.patch: Update Hebrew translation from upstream. In particular this fixes an autopkgtest failure where U+2236 RATIO was wrongly translated to U+003A COLON (Closes: #974086), and also fixes the hour and minute in the GNOME Shell clock being reversed in the Hebrew locale. -- Sebastien Bacher Fri, 15 Jan 2021 17:23:56 +0100 ** Changed in: gnome-desktop3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1911934 Title: SRU the current 3.38 stable update Status in gnome-desktop3 package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.38.3 * Regression potential The update has updated translations and version number, translations are part of langpacks and not shipped with the update so it leaves the version string to verify To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1911934/+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 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
Eventually I was able to install 5.4.0-62-generic and the stick is now working. However I'm still seeing updates of 5.8 line with apt update/apt upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I filed bug #1912032 concerning the failure of nvidia drivers to install during a fresh installation of Ubuntu 20.04.1 because when download updates is selected it auto-updates to a 5.8 series kernel during installation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I updated the bug description to better explain why I believe this is a bug, but I left the original content below the break. ** Description changed: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at - downgrading the X stack in 16.04 and 18.04 were always successful! But + downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly
[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I added the packaging tag because this was a packaging error in the 20.04 and 20.04.1 images. ** Tags added: packaging ** Description changed: + Beginning about January 8th Focal users that installed Focal using + either the Ubuntu 20.04 or 20.04.1 installation media began getting + updated to the 5.8 series linux kernel. Those who had installed using + the Ubuntu Focal Beta were not effected. This is because Focal Beta was + properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images + were built with ‘linux-generic-hwe-20.04‘. This can be easily verified + by looking at the iso manifest: + + https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- + amd64.manifest + + Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be + downloaded here: + + https://old-releases.ubuntu.com/releases/20.04/ + + The expected behavior is for Ubuntu Focal users to remain on the 5.4 + series kernel unless they install with 20.04.2 or later images as + indicated here: + + https://wiki.ubuntu.com/Kernel/LTSEnablementStack + + While not entirely updated it says “if one wants to remain on the + original GA (General Availability) stacks, the options [include]; + Install from a previous + 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point + release and update”. + + Jump just below that to the Focal specific notes and it says “The + 20.04.2 and newer point releases will ship with an updated kernel and X + stack by default for the desktop”. Since 20.04.2 is not even due for + release until next month it makes no sense for updates to the 5.8 series + kernel to be occurring unless the focal-proposed repos are enabled even + if HWE protocols had been changed. + + It’s also worth noting that thankfully no accompanying HWE X stack is + yet available in the repos. I say thankfully because my efforts at + downgrading the X stack in 16.04 and 18.04 were always successful! But + the lack of a matching X stack may explain the many complaints on the + forums about broken graphics??? + + It’s also worth noting that even the release notes say that “Ubuntu + 20.04 LTS is based on the long-term supported Linux release series 5.4“. + + https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel + + Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are + supposed to be supported with the 5.4 series kernel for the entire 5 + year life span: + + https://ubuntu.com/kernel/lifecycle + + The other flavors’ 20.04 and 20.04.1 images were all built correctly + with ‘linux-generic’ with the possible exception of Ubuntu Studio which + uses a kernel stack I’m not familiar with. I’m also uncertain about + Ubuntu server because I’m simply not familiar with it. + + Original bug description below: + + ## + Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with
[Desktop-packages] [Bug 1903805] Re: Thunderbird snap keeps asking to be the default email client
Launchpad has imported 23 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1680527.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2020-12-03T16:18:39+00:00 Sebastien Bacher wrote:
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:83.0)
Gecko/20100101 Firefox/83.0
Steps to reproduce:
The bug was reported against the snap on
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903805
' Thunderbird snap keeps asking to be the default email client '
The issue is similar to firefox bug 512305 , the approach for writing to
~/.local/share/applications directly isn't going to work for confined
applications
Actual results:
Thunderbird changes the default mimetype association in its private snap
directory
Expected results:
The default is changed in the real user directory. Calling xdg-settings
is proxyed to snapd and leads to the correct result
Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903805/comments/2
On 2020-12-03T16:22:03+00:00 Sebastien Bacher wrote:
Created attachment 9191065
thunderbird-xdg-settings.patch
The attached patch is similar to what firefox has been doing in
https://hg.mozilla.org/releases/mozilla-release/rev/74e95f9fb43e (the
snap env detection has been updated to be similar to what firefox is
currently doing which is a bit different from what first landed)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903805/comments/3
On 2020-12-05T23:02:13+00:00 Rob Lemley wrote:
It looks reasonable enough and applied cleanly to current Daily code. I
started up a try (Daily version) build with it applied. Any chance of
getting a proper patch with the a checkin comment and author information
included?
Try build: https://treeherder.mozilla.org/jobs?repo=try-comm-
central=FlDpf85IR6C3AvUa4Cl4UQ.0=8c6b6907e248c88ad5f0bcb3001d5d6c882a2d0c
Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903805/comments/4
On 2020-12-08T10:07:20+00:00 Sebastien Bacher wrote:
Thanks for the review, I'll update the patch in the next days as
requested, I just need to figure out the proper mercurial workflow
Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903805/comments/5
On 2020-12-08T20:58:40+00:00 Mkmelin+mozilla wrote:
Please see https://developer.thunderbird.net/thunderbird-
development/fixing-a-bug
For patches, it's what `hg export` gives you, not `hg diff` (and do set
your name/addr up in hg)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903805/comments/6
On 2020-12-09T19:58:58+00:00 Sebastien Bacher wrote:
Created attachment 9192263
Use xdg-settings in the snap to set default
Thanks for the pointer, I had read that documentation but got lost in
the queues details. I've screwed my checkout but I'm adding one with the
author/description at least, if that's not enough to commit let me know
and I will try to do again a proper checkout to have the right commit id
reference
Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903805/comments/7
On 2020-12-10T00:11:37+00:00 Rob Lemley wrote:
I built a Snap package with this applied (Thunderbird Daily) and it
didn't work. I'll try applying it to 78.6 tomorrow and see if it fares
better. (Using Ubuntu's snap sources and a build I ran on try-c-c.)
xdg-settings reports that Thunderbird is the default mail client, but I
keep getting the popup when I start it. I checked for the SNAP_NAME
environment variable on the process and it is set to "thunderbird".
Test system is Ubuntu LTS (20.04.1).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903805/comments/8
On 2020-12-10T12:07:04+00:00 Mkmelin+mozilla wrote:
Comment on attachment 9192263
Use xdg-settings in the snap to set default
Review of attachment 9192263:
-
::: mail/components/shell/nsGNOMEShellService.cpp
@@ +241,5 @@
> + }
> + if (strcmp(output, "thunderbird.desktop\n") == 0) {
> + g_free(output);
> + return true;
> + }
This part doesn't seem to follow what firefox currently has..?
Reply at:
[Desktop-packages] [Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2
1.8.5 has landed in hirsute now, so marking hirsute as fixed released. ** Changed in: flatpak (Ubuntu Hirsute) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1911473 Title: Update for ghsa-4ppf-fxf6-vxg2 Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Bionic: New Status in flatpak source package in Focal: In Progress Status in flatpak source package in Groovy: New Status in flatpak source package in Hirsute: Fix Released Bug description: [Links] Upstream Advisory: https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-fxf6-vxg2 Debian: https://security-tracker.debian.org/tracker/CVE-2021-21261 DSA: https://security-tracker.debian.org/tracker/DSA-4830-1 [Impact] Versions in Ubuntu right now: Hirsute: 1.8.4-2 Groovy: 1.8.2-1 Focal: 1.6.5-0ubuntu0.1 Bionic: 1.0.9-0ubuntu0.1 Affected versions: >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5 Patched versions: Expected to be >= 1.9.4, 1.8.x >= 1.8.5 There are also branches with patches for 1.6.x (Ubuntu 20.04), but nothing available yet for 1.0.x (Ubuntu 18.04). [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Simon McVittie discovered a bug in the flatpak-portal service that can allow sandboxed applications to execute arbitrary code on the host system (a sandbox escape). The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox to launch their own subprocesses in a new sandbox instance, either with the same security settings as the caller or with more restrictive security settings. For example, this is used in Flatpak-packaged web browsers such as Chromium to launch subprocesses that will process untrusted web content, and give those subprocesses a more restrictive sandbox than the browser itself. In vulnerable versions, the Flatpak portal service passes caller- specified environment variables to non-sandboxed processes on the host system, and in particular to the flatpak run command that is used to launch the new sandbox instance. A malicious or compromised Flatpak app could set environment variables that are trusted by the flatpak run command, and use them to execute arbitrary code that is not in a sandbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+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 1871471] Re: flash end of life soon, suggest remove from hirsute and also handle stable releases
A transition of pepperflashplugin-nonfree to a dummy package will happen via bug #1911463. Debian will keep the dummy in Bullseye, and drop it from the archive only in bookworm. Probably it's preferable also for us to wait with removing it until after the 21.04 release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute and also handle stable releases Status in OEM Priority Project: Triaged Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Status in adobe-flashplugin source package in Xenial: Fix Released Status in flashplugin-nonfree source package in Xenial: Fix Released Status in pepperflashplugin-nonfree source package in Xenial: Triaged Status in adobe-flashplugin source package in Bionic: Fix Released Status in flashplugin-nonfree source package in Bionic: Fix Released Status in pepperflashplugin-nonfree source package in Bionic: Triaged Status in adobe-flashplugin source package in Focal: Fix Released Status in flashplugin-nonfree source package in Focal: Fix Released Status in pepperflashplugin-nonfree source package in Focal: Triaged Status in adobe-flashplugin source package in Groovy: Fix Released Status in pepperflashplugin-nonfree source package in Groovy: Triaged Status in adobe-flashplugin source package in Hirsute: Fix Released Status in pepperflashplugin-nonfree source package in Hirsute: Confirmed Status in pepperflashplugin-nonfree package in Debian: Unknown Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+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 1911918] Re: SRU the current 3.38 stable update
This bug was fixed in the package gnome-control-center - 1:3.38.3-1ubuntu1 --- gnome-control-center (1:3.38.3-1ubuntu1) hirsute; urgency=medium * New upstream version based on Debian (lp: #1911918) * debian/patches/0016-diagnostics-Add-Whoopsie-support.patch: - display the whoopsie status to 'autoreport' if the corresponding key is set to true even if report=false (see lp #1906877) gnome-control-center (1:3.38.3-1) unstable; urgency=medium * Team upload * New upstream release * Use upstream/3.38.x branch for packaging * Standards-Version: 4.5.1 (no changes required) gnome-control-center (1:3.38.2-2) unstable; urgency=medium * debian/control.in: Explicitly add libgoa-backend-1.0-dev to the BD * debian/control.in: Explicitly add libsoup2.4-dev to the BD -- Sebastien Bacher Fri, 15 Jan 2021 15:10:51 +0100 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1911918 Title: SRU the current 3.38 stable update Status in gnome-control-center package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential The changes are small fixes but ensure each page of the setting is still loading, also check that the printing panel layout is still correct and that the sound panel works correctly since that's where the less trivial changes have been commited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1911918/+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 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
Do you have clean sound from HDMI1, if Linux PC is used? Today I discovered it is garbled, need to know if it is my or everyone problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Bug description: [Impact] nvidia-340 dkms fails to build against the current HWE kernel in focal, regressing the user experience. [Test case] Install the update, check that the dkms builds and works. [Where things could go wrong] The changes only add support for newer kernels so that the module can build, and it's identical to what's in groovy. In theory it could break the build against 5.4 but that's highly unlikely. -- Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H 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.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H 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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology
[Desktop-packages] [Bug 1911998] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-com
Public bug reported: mmm ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 15 19:39:33 2021 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-460 460.32.03-0ubuntu0.20.04.1 InstallationDate: Installed on 2021-01-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-460 460.32.03-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1911998 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-460 460.32.03-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: mmm ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 15 19:39:33 2021 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-460 460.32.03-0ubuntu0.20.04.1 InstallationDate: Installed on 2021-01-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-460 460.32.03-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1911998/+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 1876991] Re: Touchpad started appearing both as a touchpad and as a mouse input devices after upgrade to 20.04
Hi Guys,
I am facing the same issue. My laptop is T440p. The touchpad does not
work after the login screen.
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ Microsoft Microsoft Nano Transceiver 1.1 Consumer Control id=12 [slave
pointer (2)]
⎜ ↳ Microsoft Microsoft Nano Transceiver 1.1 id=14 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPadid=16 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]
↳ Power Button id=6[slave keyboard (3)]
↳ Video Bus id=7[slave keyboard (3)]
↳ Sleep Button id=8[slave keyboard (3)]
↳ Integrated Camera: Integrated C id=9[slave keyboard (3)]
↳ Microsoft Microsoft Nano Transceiver 1.1 id=10 [slave keyboard (3)]
↳ Microsoft Microsoft Nano Transceiver 1.1 id=11 [slave keyboard (3)]
↳ Microsoft Microsoft Nano Transceiver 1.1 System Control id=13 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
↳ ThinkPad Extra Buttonsid=18 [slave keyboard (3)]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1876991
Title:
Touchpad started appearing both as a touchpad and as a mouse input
devices after upgrade to 20.04
Status in xserver-xorg-input-synaptics package in Ubuntu:
Confirmed
Bug description:
It was working perfectly on 18.04 with 5.3 kernel but after upgrade to
20.04 it's becoming disabled because there is a "mouse" attached which
is the same touchpad detected incorrectly, xinput --list showing both
⎜ ↳ MSFT0001:00 06CB:7E7E Mouse id=11 [slave pointer (2)]
⎜ ↳ MSFT0001:00 06CB:7E7E Touchpadid=12 [slave pointer (2)]
The first line was definitely not present before, I know it because I
use it when in openbox session.
There is also a number of questions on AskUbuntu that look like results of
the same problem at first glance:
https://askubuntu.com/q/1231873/20275
https://askubuntu.com/q/1235067/20275
https://askubuntu.com/q/1234975/20275
and two global search results for the same touchpad model ("MSFT0001:00
06CB:7E7E Mouse") that show the same problem in unrelated contexts:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953405
https://bbs.archlinux.org/viewtopic.php?id=240723
I also have these errors in kernel log, may be related, weren't present
previously:
psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
psmouse serio1: Failed to enable mouse on isa0060/serio1
psmouse serio1: Failed to disable mouse on isa0060/serio1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed May 6 00:09:45 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc.
Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 5471
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic
root=/dev/mapper/ocz-root ro quiet libata.force=1.00:noncq
resume=/dev/mapper/ocz-swap_1 crashkernel=384M-2G:128M,2G-:256M
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.0
dmi.board.name: 05F5VX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: Zahoriya
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.9.0:bd07/25/2018:svnDellInc.:pnVostro5471:pvr:rvnDellInc.:rn05F5VX:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5471
dmi.product.sku: 0830
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Desktop-packages] [Bug 1908167] Please test proposed package
Hello Hui, or anyone else affected, Accepted pulseaudio into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
Hello Hui, or anyone else affected, Accepted pulseaudio into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.2-1ubuntu2.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-groovy ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
For the record, I talked to Robie who is on the SRU team, and he said: « IMHO, I think that breaking the other packages to bump Thunderbird is inevitable. Technically I don't think that's within the remit of the SRU team - it's a TB thing. I think we should figure out how to mitigate as much as possible, document and publicise the breakage as best as we can, then break it. » We went on to discuss how "apt upgrade" would behave (vs "apt dist-upgrade"), I tested and I observed that "apt upgrade" wouldn't proceed to the upgrade as it doesn't remove broken packages. The "Software Updater" GUI however does the right thing, even if the UX will be slightly unusual for most users (assuming they have tinyjsd or jsunit installed): it will first warn that "Not all updates can be installed", and propose a partial upgrade, which does the right thing, warning that it's going to remove two packages (tinyjsd and jsunit) and upgrade 5 packages (thunderbird*), and offering to proceed. We agreed that I would bring up the topic with the technical board on their mailing list. -- 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/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
@therealsujitk @ubuntu-iremonger Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Bug description: [Impact] nvidia-340 dkms fails to build against the current HWE kernel in focal, regressing the user experience. [Test case] Install the update, check that the dkms builds and works. [Where things could go wrong] The changes only add support for newer kernels so that the module can build, and it's identical to what's in groovy. In theory it could break the build against 5.4 but that's highly unlikely. -- Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H 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.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H 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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
Does anyone know if an update of the libx11 package for lubuntu 18.04 will be released? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Confirmed Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+subscriptions -- Mailing list: https://launchpad.net/~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 1911921] Re: gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL)
Only tested on hirsute, no idea if it happens on groovy or focal too. -- 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/1911921 Title: gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) Status in gnome-shell package in Ubuntu: New Bug description: As in bug 1864052, putting a Chrome video into PiP mode crashes gnome- shell, although this time, in a different location. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6 Uname: Linux 5.10.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 15 16:04:30 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-14 (1037 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911921/+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 1911921] Re: gnome-shell crashed with SIGABRT
Full stack trace, seems retracing failed. Oh well. ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911921/+attachment/5453545/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911921/+attachment/5453519/+files/CoreDump.gz ** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with SIGABRT + gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) -- 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/1911921 Title: gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) Status in gnome-shell package in Ubuntu: New Bug description: As in bug 1864052, putting a Chrome video into PiP mode crashes gnome- shell, although this time, in a different location. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6 Uname: Linux 5.10.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 15 16:04:30 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-14 (1037 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911921/+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 1911934] [NEW] SRU the current 3.38 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.38.3 * Regression potential The update has updated translations and version number, translations are part of langpacks and not shipped with the update so it leaves the version string to verify ** Affects: gnome-desktop3 (Ubuntu) Importance: Low Status: Fix Committed ** Changed in: gnome-desktop3 (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-desktop3 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1911934 Title: SRU the current 3.38 stable update Status in gnome-desktop3 package in Ubuntu: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.38.3 * Regression potential The update has updated translations and version number, translations are part of langpacks and not shipped with the update so it leaves the version string to verify To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1911934/+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 1900679] Re: [snap] chromium spams dmesg
The relevant syscall is `sched_setaffinity`, which when used with a first argument of `0` is allowed in the default policy. Can someone who is experiencing this bug run an strace to determine what argument chromium is trying to use with sched_setaffinity ? We allow any sched_setaffinity arguments with the process-control interface, but if this denial is not breaking the application then perhaps it should just be silenced in the policy instead. ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg Status in chromium-browser package in Ubuntu: New Status in snapd package in Ubuntu: Incomplete Bug description: [T okt 20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 Things like these just get repeated endlessly and very often, making any potential debugging very annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+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 1903805] Re: Thunderbird snap keeps asking to be the default email client
The issue is fixed now in thunderbird 78.6.1 (but it requires the core18 snap from the candidate channel) ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Committed ** Bug watch added: Mozilla Bugzilla #1680527 https://bugzilla.mozilla.org/show_bug.cgi?id=1680527 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1680527 Importance: Unknown Status: Unknown -- 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/1903805 Title: Thunderbird snap keeps asking to be the default email client Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Fix Committed Bug description: Thunderbird snap 78.4.1 2020-11-09 (93) running on Ubuntu 20.04.1 LTS The latest version keeps asking at every start whether I want to "Use Thunderbird as the default client". I do. So I keep "Email" and "Always perform this check when starting Thunderbird" checked and click "Set as Default". When I quit and restart Thunderbird I'm prompted the same question again. I would expect Thunderbird to set itself as default and no longer ask this question. Instead, Thunderbird either fails to set itself as default or it asks the question despite being the default (not sure how to distinguish). To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1903805/+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 1800925] Re: can't print pdf files with evince, printer dcp 1510. Message is printer complete but no printed page comes out.
In 21.04 the printmenu from evince stops the whole programm and can only be killed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1800925 Title: can't print pdf files with evince, printer dcp 1510. Message is printer complete but no printed page comes out. Status in evince package in Ubuntu: Confirmed Bug description: can't print pdf on a dcp 1510. I removed than re-instalaled printer, test page prints ok. however when attempted to print pdf file, i get the message print completed but actually nothing comes out of the printer. That is not an issue with libreoffice documents. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 08:13:15 2018 InstallationDate: Installed on 2018-05-12 (171 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1800925/+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 1800925] Re: can't print pdf files with evince, printer dcp 1510. Message is printer complete but no printed page comes out.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1800925 Title: can't print pdf files with evince, printer dcp 1510. Message is printer complete but no printed page comes out. Status in evince package in Ubuntu: Confirmed Bug description: can't print pdf on a dcp 1510. I removed than re-instalaled printer, test page prints ok. however when attempted to print pdf file, i get the message print completed but actually nothing comes out of the printer. That is not an issue with libreoffice documents. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 08:13:15 2018 InstallationDate: Installed on 2018-05-12 (171 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1800925/+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 1809685] Re: The evince application often freezes
Evince also stops while trying to print in Ubuntu 21.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1809685/+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 1906877] Re: diagnostics panel can leave automatic crash reporting enabled
** Changed in: gnome-control-center (Ubuntu Groovy) Status: Incomplete => Fix Committed ** Changed in: gnome-control-center (Ubuntu Groovy) Importance: Undecided => High -- 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/1906877 Title: diagnostics panel can leave automatic crash reporting enabled Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Incomplete Status in gnome-control-center source package in Focal: Incomplete Status in gnome-control-center source package in Groovy: Fix Committed Status in gnome-control-center source package in Hirsute: Fix Released Bug description: * Impact If one selects "Automatic" in the "Send error reports to Canonical" portion of "Problem Reporting" the file /var/lib/apport/autoreport is created. However, if you later switch to "Never" the file is not removed but the panel continues to show "Never". * Test case - change the automatic report option in settings to automatic and then to never, the /var/lib/apport/autoreport file should be removed * Regression potential The patch modifies the whoopsie configuration, check that the service status is right for the 3 auto/manual/never options ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 4 12:38:37 2020 InstallationDate: Installed on 2016-01-22 (1778 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) 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/1906877/+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 362359] Re: Focus gets stuck to a window - impossible to select other windows
but it reappeared after some time -- 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/362359 Title: Focus gets stuck to a window - impossible to select other windows Status in xorg-server package in Ubuntu: Fix Released Bug description: Alright, terribly annoying bug that gets me to reboot several times a day, but very hard to understand how to trigger it. What happens: after some time of usage, you get "stuck" in a window. Idem est, you can not select another window. You can still click, select and drag in the window that has the focus, but clicking on other windows, or on the panel, just doesn't work. Notes: - With window I don't mean "application window". For example it can only be the page view in firefox, and you won't be able to click the buttons or the URL field. It can also be the main text window in xchat, and you wont be able to click in the user list or to change the chatroom. - The click seems to be grabbed by the window having the focus, even if you click outside of it. For example, using xchat, if the main text window has focus, clicking and dragging in the user list will actually select text in the main text window. - Using xev, it seems that clics do not get passed to the correct window at all (nothing received) - I have no idea what triggers this as sometimes it will trigger alone - pc works, I leave it for an hour, I come back, the problem is triggered - Curious effect now: dragging and dropping to another window gives focus to the window, and seems to be the only way to do so. For example if in firefox the main page view window has the focus and I cant click the buttons, drag and dropping text to the buttons gives the focus to the buttons, and I can't clic the page view window anymore. Drag and dropping a button to the page view window gives it its focus back Additional info: * Compiz disabled * Intel graphic card * Ubuntu jaunty - latest patches * Using a laptop, with an USB mouse HAL, xserver, I have no idea where to file this bug into. I hope it will be fixed before the release, it is really terribly annoying :s Please tell me if there is any other detail I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+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 362359] Re: Focus gets stuck to a window - impossible to select other windows
I experienced the same issue but it dissappeared after i purged my xorg installation and reinstalled it from root shell(ctrl+alt+F4). i think main issue was with libinput in my case. just thought to provide this information -- 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/362359 Title: Focus gets stuck to a window - impossible to select other windows Status in xorg-server package in Ubuntu: Fix Released Bug description: Alright, terribly annoying bug that gets me to reboot several times a day, but very hard to understand how to trigger it. What happens: after some time of usage, you get "stuck" in a window. Idem est, you can not select another window. You can still click, select and drag in the window that has the focus, but clicking on other windows, or on the panel, just doesn't work. Notes: - With window I don't mean "application window". For example it can only be the page view in firefox, and you won't be able to click the buttons or the URL field. It can also be the main text window in xchat, and you wont be able to click in the user list or to change the chatroom. - The click seems to be grabbed by the window having the focus, even if you click outside of it. For example, using xchat, if the main text window has focus, clicking and dragging in the user list will actually select text in the main text window. - Using xev, it seems that clics do not get passed to the correct window at all (nothing received) - I have no idea what triggers this as sometimes it will trigger alone - pc works, I leave it for an hour, I come back, the problem is triggered - Curious effect now: dragging and dropping to another window gives focus to the window, and seems to be the only way to do so. For example if in firefox the main page view window has the focus and I cant click the buttons, drag and dropping text to the buttons gives the focus to the buttons, and I can't clic the page view window anymore. Drag and dropping a button to the page view window gives it its focus back Additional info: * Compiz disabled * Intel graphic card * Ubuntu jaunty - latest patches * Using a laptop, with an USB mouse HAL, xserver, I have no idea where to file this bug into. I hope it will be fixed before the release, it is really terribly annoying :s Please tell me if there is any other detail I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+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 1909763] Re: Shell stuck forever spewing syslog
*** This bug is a duplicate of bug 1908429 *** https://bugs.launchpad.net/bugs/1908429 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1909763 Title: Shell stuck forever spewing syslog Status in gnome-shell package in Ubuntu: Confirmed Bug description: Filling syslog with Dec 31 12:17:04 gg-pc gnome-shell[1934]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Dec 31 12:17:04 gg-pc gnome-shell[1934]: The offending callback was SourceFunc(). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 31 12:23:35 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-10 (234 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909763/+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 1864052] Re: gnome-shell crashed with SIGABRT in src/core/window.c:1591:meta_window_unmanage: assertion failed: (g_list_find (workspace->windows, window) == NULL)
Found another crash the same way in bug 1911921
--
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/1864052
Title:
gnome-shell crashed with SIGABRT in
src/core/window.c:1591:meta_window_unmanage: assertion failed:
(g_list_find (workspace->windows, window) == NULL)
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Released
Status in mutter source package in Groovy:
Fix Released
Bug description:
https://errors.ubuntu.com/problem/3e51baba6960038ed185034581cb83e4dd4776e6
---
gnome-shell crashes whenever in CHrome you pop out a video into a
floating video, or close the floating video (move the video back into
the main window).
To test, you can use
javascript:document.getElementsByTagName('video')[0].requestPictureInPicture();
to make a video float on any site, even if the site does not have a
button for it. I only tested Netflix.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 20 15:36:33 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-03-14 (707 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: Upgraded to focal on 2019-11-25 (87 days ago)
UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild
sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1864052/+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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
This affected me too - it broke the Ubuntu version of Virtualbox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: New Bug description: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+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 1911918] [NEW] SRU the current 3.38 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential The changes are small fixes but ensure each page of the setting is still loading, also check that the printing panel layout is still correct and that the sound panel works correctly since that's where the less trivial changes have been commited ** Affects: gnome-control-center (Ubuntu) Importance: Low Status: Fix Committed ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed -- 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/1911918 Title: SRU the current 3.38 stable update Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-38/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential The changes are small fixes but ensure each page of the setting is still loading, also check that the printing panel layout is still correct and that the sound panel works correctly since that's where the less trivial changes have been commited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1911918/+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 1907470] Re: Thunderbird latest/stable snap's release note shows 'Daily build' instead
** Changed in: thunderbird (Ubuntu) Status: Fix Committed => 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/1907470 Title: Thunderbird latest/stable snap's release note shows 'Daily build' instead Status in thunderbird package in Ubuntu: Fix Released Bug description: Hello there! Under Ubuntu 20.04, with Thunderbird installed using snap (latest/stable: 78.5.1 2020-12-02), the release note shows up as `daily build` with a tab navigating to https://start.thunderbird.net /en-US/daily/?uri=/thunderbird/releasenotes/=en- US=78.5.1=release-cck- ubuntu=Linux=20201130232704 The expected behavior is that the release note should show up as Thunderbird stable build. I have asked in the snapcraft forum and one member have also confirmed this issue (https://forum.snapcraft.io/t/question-regarding-the- thunderbird-snap-latest-stable-release-note/21496). Thank you for your help and hope you have a great day! Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1907470/+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 1908500] Re: libxslt.a missing from libxslt1-dev
** Changed in: libxslt (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxslt in Ubuntu. https://bugs.launchpad.net/bugs/1908500 Title: libxslt.a missing from libxslt1-dev Status in libxslt package in Ubuntu: Invalid Bug description: The libxslt.a file is missing from 1.1.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1908500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1908500] Re: libxslt.a missing from libxslt1-dev
Mattia Rizzolo writes: > Could you please describe: > > * Which release you are basing this bug on? Buster > * Describe why you'd want the static library? My mistake, I had gotten confused while trying to fix a broken build with a libxslt dependency and thought I needed it. You can close this issue, apologies for wasting your time. ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: h...@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam] The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxslt in Ubuntu. https://bugs.launchpad.net/bugs/1908500 Title: libxslt.a missing from libxslt1-dev Status in libxslt package in Ubuntu: Incomplete Bug description: The libxslt.a file is missing from 1.1.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1908500/+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 1911903] [NEW] Auto-reconnection of wifi doesn't work
Public bug reported: Hi everyone :) It's a problem that occurs without any possible correlation with other event (wake up, sleep etc). In the middle of a session the Wi-Fi simply stop working and not only the system doesn't reconnect automatically, but you need to turn off and back on the Wi-Fi to be able to continue your activities. IDK if it's related, but sometimes also happens that the other Wi-Fi networks around me are not visible in the setting. If I can help in any way with logs of any other information please contact me Antonio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 12:56:08 2021 InstallationDate: Installed on 2020-11-03 (73 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.178.1 dev wlp2s0b1 proto dhcp metric 20600 169.254.0.0/16 dev br-90c79c39374f scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-90c79c39374f proto kernel scope link src 172.18.0.1 linkdown 192.168.178.0/24 dev wlp2s0b1 proto kernel scope link src 192.168.178.52 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1911903 Title: Auto-reconnection of wifi doesn't work Status in network-manager package in Ubuntu: New Bug description: Hi everyone :) It's a problem that occurs without any possible correlation with other event (wake up, sleep etc). In the middle of a session the Wi-Fi simply stop working and not only the system doesn't reconnect automatically, but you need to turn off and back on the Wi-Fi to be able to continue your activities. IDK if it's related, but sometimes also happens that the other Wi-Fi networks around me are not visible in the setting. If I can help in any way with logs of any other information please contact me Antonio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 12:56:08 2021 InstallationDate: Installed on 2020-11-03 (73 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.178.1 dev wlp2s0b1 proto dhcp metric 20600 169.254.0.0/16 dev br-90c79c39374f scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-90c79c39374f proto kernel scope link src 172.18.0.1 linkdown 192.168.178.0/24 dev wlp2s0b1 proto kernel scope link src 192.168.178.52 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1911903/+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 1874689] Re: alsa force-reload needed to fix my sound after upgrade to 20.04
Also affected. Having Ubuntu 20.04 LTS (the default flavor). lspci -v (yes, I have 2 gpus) 04:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) Subsystem: NVIDIA Corporation TU116 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 135 Memory at fa08 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 09:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) Subsystem: NVIDIA Corporation TU116 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 136 Memory at fc08 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Subsystem: Gigabyte Technology Co., Ltd Starship/Matisse HD Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 138 Memory at fc40 (32-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1874689 Title: alsa force-reload needed to fix my sound after upgrade to 20.04 Status in Ubuntu MATE: New Status in alsa-driver package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Mate 18.04 LTS to Ubuntu Mate 20.04 LTS "sudo alsa force-reload" is needed to fix my sound. I upgraded yesterday (23rd) before the official announcements of 20.04 LTS. Using "do-release-upgrade -d". I'm not sure yet how often I have to run "sudo alsa force-reload". When I have no sound a reboot is not a guranteed fix although it worked once. Booting into a Ubuntu Desktop 20.04 LTS gets working sounds each time I tried. Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874689/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1911030] Re: graphical flashes on a raspi 4
Further testing. Using the KMS driver results in mesa defaulting to llvmpipe software rendering making YouTube a painful experience. So the fkms is needed for 3d acceleration but glitchy graphics... ho- hum. On Thu, 14 Jan 2021, 16:34 David Mohammed, wrote: > Do note. > > If I change in /boot/firmware/config.txt the default > > dtoverlay=vc4-fkms-v3d > > To > > dtoverlay=vc4-kms-v3d > > Then the graphical issues disappear. Maybe something to consider? > > On Tue, 12 Jan 2021, 02:25 Daniel van Vugt, <1911...@bugs.launchpad.net> > wrote: > >> ** Tags added: raspi raspi-gfx >> >> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) >> >> ** Also affects: mesa (Ubuntu) >>Importance: Undecided >>Status: New >> >> ** Summary changed: >> >> - graphical flashes on a raspi 4 >> + Graphical flashes on a raspi 4 >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1911030 >> >> Title: >> Graphical flashes on a raspi 4 >> >> Status in mesa package in Ubuntu: >> New >> Status in xorg-server package in Ubuntu: >> New >> >> Bug description: >> Using gnome-shell - activities - see attached video >> >> Graphics flash - more prominent with more than one app running. >> >> If you install ubuntu-budgie-desktop and simply move through the menu >> categories the flashing is even more prominent. >> >> I'm guessing this is xorg related - but I do note the recent mesa >> uplift has made things worse >> >> ProblemType: Bug >> DistroRelease: Ubuntu 21.04 >> Package: xorg 1:7.7+19ubuntu15 >> ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18 >> Uname: Linux 5.8.0-1011-raspi aarch64 >> ApportVersion: 2.20.11-0ubuntu55 >> Architecture: arm64 >> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >> CasperMD5CheckResult: skip >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Mon Jan 11 16:49:14 2021 >> DistUpgraded: Fresh install >> DistroCodename: hirsute >> DistroVariant: ubuntu >> ExtraDebuggingInterest: Yes >> GraphicsCard: >> >> ImageMediaBuild: 20201225 >> Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 >> USB 3.0 Host Controller >> ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 >> snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 >> snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 >> smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 >> vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 >> root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet >> splash >> SourcePackage: xorg >> UpgradeStatus: No upgrade log present (probably fresh install) >> acpidump: >> >> version.compiz: compiz N/A >> version.libdrm2: libdrm2 2.4.103-2 >> version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 >> version.libgl1-mesa-glx: libgl1-mesa-glx N/A >> version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 >> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A >> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 >> version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A >> 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/mesa/+bug/1911030/+subscriptions >> > -- 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/1911030 Title: Graphical flashes on a raspi 4 Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Using gnome-shell - activities - see attached video Graphics flash - more prominent with more than one app running. If you install ubuntu-budgie-desktop and simply move through the menu categories the flashing is even more prominent. I'm guessing this is xorg related - but I do note the recent mesa uplift has made things worse ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu55 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 16:49:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ImageMediaBuild: 20201225 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60
[Desktop-packages] [Bug 1586822]
The bug is not yet actionable, because a decision was not achieved yet. The team working on 2020H2 bookmarks improvements wanted to complete collecting users feedback and telemetry before evaluating further steps. Thus, while I'm in favor of this change, we should at least wait the end of that project. Fwiw, there is already browser.bookmarks.defaultLocation, but that is updated to the last used folder as a consequence of bug 1432604. So the work here would pretty much introduce a pref to disable the behavior from bug 1432604 (don't remember the last used folder). -- 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/1586822 Title: Ability to set default save destination for new bookmarks Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Though I can understand the rationale for making all new bookmarks go into an "Unsorted Bookmarks" area, I think that it would be good if Firefox provided an option to allow the user to change the default save location for new bookmarks, because I for one don't want to have to move every new bookmark I make to the "Bookmarks Toolbar", I would like to be able to have them just go there automatically, but I can't currently so it would be good if there were an option to change the default save location of bookmarks. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1586822/+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 1911379] Re: [SRU] Avoid error message when the file doesn't exist
Upload to H and SRU to G ** Changed in: wslu (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: wslu (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: wslu (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: wslu (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] Avoid error message when the file doesn't exist Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Groovy: Fix Committed Status in wslu source package in Hirsute: Fix Committed Bug description: [Impact] this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+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 1911887] [NEW] Xorg freeze
Public bug reported: I just installed Ubuntu 20.04. but sometimes, the screen is freezing. This is very very bothering me. Please help me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 03:37:42 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GT218 [GeForce G210] [10de:0a60] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2021-01-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Onda technology corporation ONDA H110S QG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d1643fe1-2ea9-43a9-bce2-476592a525ca ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 2016/04/29 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: ONDA H110S QG dmi.board.vendor: Onda technology corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd2016/04/29:svnOndatechnologycorporation:pnONDAH110SQG:pvrDefaultstring:rvnOndatechnologycorporation:rnONDAH110SQG:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ONDA H110S QG dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Onda technology corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~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 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/1911887 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I just installed Ubuntu 20.04. but sometimes, the screen is freezing. This is very very bothering me. Please help me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version
[Desktop-packages] [Bug 1911857] Re: cant tell whats wrong
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! Possibly related - https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911858 -- 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/1911857 Title: cant tell whats wrong Status in xorg package in Ubuntu: New Bug description: cant tell whats wrong ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 15 12:30:06 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2017-03-15 (1401 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=a024a4c4-d7d6-404c-be82-173672511ace ro acpi_rev_override alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2017 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 01HYMY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01HYMY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Wed Jan 13 10:43:27 2021 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.9-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911857/+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 1911858] Re: i am not aware what are these errors
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! Possibly related - https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911857 -- 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/1911858 Title: i am not aware what are these errors Status in xorg package in Ubuntu: New Bug description: cant tell what are these errors releted too... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 15 12:32:10 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2017-03-15 (1401 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=a024a4c4-d7d6-404c-be82-173672511ace ro acpi_rev_override alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2017 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 01HYMY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01HYMY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Wed Jan 13 10:43:27 2021 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.9-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
