[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
failed to build on riscv64 pulseaudio 13.99.1: src/test-suite.log # TOTAL: 36 # PASS: 35 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: volume-test = Running suite(s): Volume Attenuation of sample 1 against 32767: -90.3087 dB Smallest possible attenuation > 0 applied to 32767: 0 max deviation: 150895, number of times over 1:10626 0%: Checks: 1, Failures: 1, Errors: 0 tests/volume-test.c:151:F:volume:volume_test:0: Assertion 'md <= 1' failed FAIL volume-test (exit status: 1) -- 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 pulseaudio package in Ubuntu: Fix Committed 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 Committed 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] 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 1908634] [NEW] [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound
Public bug reported: I was playing back from SoundCloud where I pay for Go and use the "High Quality" streaming settings. I'm also working on a react native app and this issue seems to happen after I start the bundle server (react-native start). I can't show you the code because I'm selling it. I connected my headphones through an FX-Audio DAC-X6, a FiiO K3 Type-C USB DAC, and my motherboard and I get the exact same crackling, so it's defiantly a software issue. As for the actual sounds, the popping sound like a momentary drop in all sound, I don't have an oscilloscope but I suspect the pops would look like ~15ish milliseconds of 0 volts right in the middle of the sound wave. Also these pops are repetitive, like there's a pattern to them starting with a big one and then smaller ones at regular intervals leading me to think some number isn't getting processed properly. Now that I think about it I might have been experiencing this bug ever since Ubuntu 19.10 but haven't noticed it up until I got these high impedance headphones and now have to turn up my DAC to twice the gain. It doesn't sound like static, but more like a single clap but slowed down. I have already followed a menagerie of solutions (2 most recent ones): https://wiki.ubuntu.com/Audio/PositionReporting https://itectec.com/ubuntu/ubuntu-annoying-click-popping-sound-on- ubuntu-20-04/ And none of them have made a difference. Appended you will find an audio file where I put my headphones on my condenser mic and played a 440hz tone in an attempt to record the pops. It's alittle quiet, so I'd recommend trying to amplify it. I hoped I could use Audacity to visually identify the pops in the actual waveform but I wasn't sure what I was looking for. I really want this fixed because right now I absolutely can't use my headphones, I literally feel each and every pop and it hurts. If you have any further questions or want to test on my hardware, please call me at +1-201-675-9961 or email me at dan.ha...@gmail.com. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Dec 17 22:49:22 2020 InstallationDate: Installed on 2020-12-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DACX6 failed Symptom_Card: DAC-X6 - DAC-X6 Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GM-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV17.12:bd11/28/2012:svnMSI:pnMS-7641:pvr4.0:rvnMSI:rn760GM-P34(FX)(MS-7641):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7641 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-12-17T22:21:33.927437 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "An attempt at recording the pops" https://bugs.launchpad.net/bugs/1908634/+attachment/5444741/+files/crackle.mp3 -- 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/1908634 Title: [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: I was playing back from SoundCloud where I pay for Go and use the "High Quality" streaming settings. I'm also working on a react native app and this issue seems to happen after I start the bundle server (react-native start). I can't show you the code because I'm selling it. I connected my headphones through an FX-Audio DAC-X6, a FiiO K3 Type-C USB DAC, and my motherboard and I get the exact same crackling, so it's defiantly a software issue. As for the actual sounds, the popping sound like a momentary drop in all sound, I don't have an oscilloscope but I suspect the pops would look like ~15ish milliseconds of 0 volts right in the middle of the sound wave. Also these pops are repetitive, like there's a pattern to them starting with a big one and then smaller ones at regular intervals leading
[Desktop-packages] [Bug 1908559] Re: Steam or discord: "pushModal: invocation of begin_modal failed"
Please try uninstalling/disabling all of these extensions: 'gTile@vibou', 'multi-monitors-add-on@spin83', 'tray-ic...@zhangkaizhao.com', 'topic...@phocean.net' and then log out and in again. Removing extensions from the equation is the first thing we need to try because so many bugs are caused by extensions. -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1908559] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444716/+files/ProcCpuinfoMinimal.txt -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1908559] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444719/+files/monitors.xml.txt -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1908559] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444718/+files/ShellJournal.txt -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1908559] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444717/+files/ProcEnviron.txt -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1908559] Re: Steam or discord: "pushModal: invocation of begin_modal failed"
apport information ** Tags added: apport-collected groovy third-party-packages ** Description changed: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.3 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2018-12-30 (718 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Package: gnome-shell 3.38.1-1ubuntu1.1 + PackageArchitecture: amd64 + RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 + Tags: third-party-packages groovy + Uname: Linux 5.9.12-050912-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444714/+files/Dependencies.txt -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1908559] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444715/+files/GsettingsChanges.txt -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 427168] Re: usb keyboard settings (repeat rate and delay) reset on plugin
@Alexander Adam you can toggle from the cli like so: xset r rate 250 Replace 250 with your desired repeat rate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/427168 Title: usb keyboard settings (repeat rate and delay) reset on plugin Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: I like a fairly fast repeat rate and low delay when typing. In the course of using my laptop (Dell Vostro 1500), I sometimes plug in a USB keyboard. Every time I do this, I notice that the repeat rate and delay on the USB keyboard are way slow and high, while the built-in keyboard repeat rate and delay are as I like them (fast and low). To fix this, every time I plug in the USB keyboard, I have to go to System→Preferences→Keyboard, slightly move the Speed slider, then Close the dialog. (Note that the sliders haven't changed from the last invocation of this application, just that the settings apparently need to be reapplied internally.) I believe that at least these keyboard settings (repeat rate and delay) should be universal for all keyboards. Repeatable: always. How to reproduce: 1. plug in a USB keyboard 2. Note current repeat-rate and delay. 3. Change repeat-rate and delay via System->Preferences->Keyboard 4. Unplug and re-plugin the USB keyboard. 5. Return to step 2. Possibly related bugs: Bug #295990 Bug #426176 $ uname -a Linux hani 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.04 Release: 9.04 Codename: jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/427168/+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 1908608] Re: Crash to login screen when plugging in/out external monitor
It may also help to try uninstalling these extensions: 'nightthemeswitc...@romainvigier.fr', 'd...@rastersoft.com' ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1908608 Title: Crash to login screen when plugging in/out external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: This matches the title of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I don't want to assume it is the same considering that was allegedly fixed three years ago. journal: dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8 dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 10 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 7 dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6 - bcm5974: client bug: event processing lagging behind by 42ms, your system is too slow dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 8 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 15 dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine nitrokey failed to change udev device /sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice: dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device dec 17 23:12:53 computer-name fwupd[3384]: Flags:none dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 0x55db60db91a0 == dec 17 23:13:06 computer-name nautilus[3814]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3089]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name org.kde.kdeconnect.daemon.desktop[3092]: The Wayland connection broke. Did the Wayland compositor die? dec 17 23:13:06 computer-name gsd-power[3032]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name polkitd(authority=local)[738]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.82, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale sv_SE.UTF-8) (disconnected from bus) dec 17 23:13:06 computer-name unknown[3020]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3031]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3030]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3064]: Error reading events from display: Brutet rör dec 17
[Desktop-packages] [Bug 1908608] Re: Crash to login screen when plugging in/out external monitor
I don't think that assertion is fatal so it's not what's crashing. This however is fatal: dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 0x55db60db91a0 == If you have already reported a crash file then please check /var/crash to see if a new supplementary file has been created in that directory, which contains a short ID. Please tell us that ID string. Alternatively look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. -- 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/1908608 Title: Crash to login screen when plugging in/out external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: This matches the title of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I don't want to assume it is the same considering that was allegedly fixed three years ago. journal: dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8 dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 10 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 7 dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6 - bcm5974: client bug: event processing lagging behind by 42ms, your system is too slow dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 8 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 15 dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine nitrokey failed to change udev device /sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice: dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device dec 17 23:12:53 computer-name fwupd[3384]: Flags:none dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 0x55db60db91a0 == dec 17 23:13:06 computer-name nautilus[3814]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3089]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name org.kde.kdeconnect.daemon.desktop[3092]: The Wayland connection broke. Did the Wayland compositor die? dec 17 23:13:06 computer-name gsd-power[3032]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name polkitd(authority=local)[738]: Unregistered Authentication Agent for unix-session:2
[Desktop-packages] [Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
bug was hardware - bad usb port! hardware is hilarious. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1908535] Re: Xorg crash after clean Ubuntu 20.10 install on Intel system
More likely that you will find it is the 'gnome-shell' process crashing. -- 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/1908535 Title: Xorg crash after clean Ubuntu 20.10 install on Intel system Status in xorg-server package in Ubuntu: Incomplete Bug description: Intel Core i5/8GB/256GB. Each time a minute or so after I boot into the system, I get a system error, but there are no useful details. The only thing I found is a crash log: https://pastebin.com/W54KDMGE Since there does not seem to be much readible stuff in there for a common person, I cannot determine whether or not this bug has been reported already. How can I prevent this bug from happening? I also tried to run sudo ubuntu-bug xorg. That did not work: $ sudo ubuntu-bug xorg cat: /var/log/lightdm/x-0-greeter.log: No such file or directory cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908535/+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 1908476] Re: Memory leaks in Xorg
The 'intel' driver isn't really being maintained anymore. So it sounds unlikely this will be fixed. Unfortunately the supported 'modesetting' driver doesn't have a TearFree option yet: https://gitlab.freedesktop.org/xorg/xserver/-/issues/244 But the good news is that it still doesn't tear for most people. The 'modesetting' driver will only tear if you have multiple monitors or enable fractional scaling. In both of those cases you can avoid all tearing by logging into 'Ubuntu on Wayland' instead. ** Tags added: focal ** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Summary changed: - Memory leaks in Xorg + Memory leak in Xorg when TearFree is enabled on xserver-xorg-video-intel ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #244 https://gitlab.freedesktop.org/xorg/xserver/-/issues/244 -- 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/1908476 Title: Memory leak in Xorg when TearFree is enabled on xserver-xorg-video- intel Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Memory leaks in Xorg Hi, Everyone. I'm working software developer. I'm having a problem right now. Continuing to decode H.264 using ffmeg and libva causes a memory leak in Xorg. This is especially likely to occur when the resolution is scaled (both UP and Down). The settings of 20-intel.conf are as follows. [20-intel.conf] -- Section "Device" Identifier "Card0" Driver "intel" BusID "PCI:0:2:0" Option "AccelMethod" "sna" Option "SwapbuffersWait" "False" Option "TearFree" "True" EndSection -- If you do not set TearFree, memory leaks will not occur, but tearing will occur. It does not occur on Ubuntu 16.04 with the same settings. Is there a way to eliminate the memory leak and prevent screen tearing? [TOP Command Result] -- DATETME PR NI VIRTRES SHR S %CPU%MEM TIME+ COMMAND 10:34:44 20 0 553532 36340 21692 S 20.00.5 4:33.33 Xorg 10:34:49 20 0 553724 36340 21692 S 20.20.5 4:34.34 Xorg 10:34:54 20 0 553724 36340 21692 S 20.10.5 4:35.35 Xorg 10:34:59 20 0 554112 36340 21692 S 20.10.5 4:36.36 Xorg 10:35:05 20 0 554112 36496 21756 S 20.20.5 4:37.38 Xorg 10:35:10 20 0 554112 36496 21756 S 20.10.5 4:38.39 Xorg 10:35:15 20 0 554112 36496 21756 S 20.00.5 4:39.39 Xorg 10:35:20 20 0 554368 36496 21756 S 20.20.5 4:40.40 Xorg 10:35:25 20 0 554368 36496 21756 S 20.10.5 4:41.41 Xorg 10:35:30 20 0 554368 36496 21756 S 20.70.5 4:42.45 Xorg 10:35:35 20 0 555076 36660 21800 S 19.80.5 4:43.45 Xorg 10:35:40 20 0 555076 36660 21800 S 20.00.5 4:44.45 Xorg 10:35:45 20 0 555076 36660 21800 S 20.10.5 4:45.46 Xorg 10:35:50 20 0 555076 36660 21800 S 20.10.5 4:46.47 Xorg 10:35:55 20 0 555076 36808 21860 S 19.80.5 4:47.47 Xorg 10:36:00 20 0 554692 36700 21748 S 19.80.5 4:48.46 Xorg 10:36:05 20 0 554824 36700 21748 S 19.70.5 4:49.46 Xorg 10:36:10 20 0 554824 36700 21748 R 20.50.5 4:50.49 Xorg 10:36:15 20 0 554824 36700 21748 S 19.70.5 4:51.48 Xorg 10:36:20 20 0 554824 36844 21812 S 20.00.5 4:52.49 Xorg 10:36:25 20 0 554312 36812 21748 S 19.90.5 4:53.49 Xorg 10:36:30 20 0 554312 36812 21748 S 20.00.5 4:54.49 Xorg 10:36:35 20 0 555400 36948 21856 S 20.10.5 4:55.51 Xorg 10:36:40 20 0 32 36948 21856 S 19.90.5 4:56.51 Xorg 10:36:45 20 0 32 36948 21856 S 19.80.5 4:57.50 Xorg 10:36:50 20 0 32 36948 21856 S 20.40.5 4:58.53 Xorg 10:36:55 20 0 555020 37004 21820 S 19.90.5 4:59.53 Xorg 10:37:00 20 0 555020 37004 21820 S 19.70.5 5:00.52 Xorg 10:37:05 20 0 555020 37004 21820
[Desktop-packages] [Bug 1908535] Re: Xorg crash after clean Ubuntu 20.10 install on Intel system
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: groovy ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1908535 Title: Xorg crash after clean Ubuntu 20.10 install on Intel system Status in xorg-server package in Ubuntu: Incomplete Bug description: Intel Core i5/8GB/256GB. Each time a minute or so after I boot into the system, I get a system error, but there are no useful details. The only thing I found is a crash log: https://pastebin.com/W54KDMGE Since there does not seem to be much readible stuff in there for a common person, I cannot determine whether or not this bug has been reported already. How can I prevent this bug from happening? I also tried to run sudo ubuntu-bug xorg. That did not work: $ sudo ubuntu-bug xorg cat: /var/log/lightdm/x-0-greeter.log: No such file or directory cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908535/+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 1907870] Re: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9
** No longer affects: mutter (Ubuntu) ** No longer affects: gnome-control-center (Ubuntu) ** Summary changed: - HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9 + Samsung SMBX2250 monitor detected but black screen (has a preferred mode but no current mode set) -- 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/1907870 Title: Samsung SMBX2250 monitor detected but black screen (has a preferred mode but no current mode set) Status in xorg-server package in Ubuntu: New Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.32
[Desktop-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
*** This bug is a duplicate of bug 1797002 *** https://bugs.launchpad.net/bugs/1797002 Hmm, maybe it depends on which project the bug is assigned to. Certainly I and other people do see plenty of private bugs. But we can't prove that we see all private bugs. -- 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/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms. Speakers work in Windows 10 / macOS 10.14+ running on same hardware. Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware. Remote control commands work (play/pause button on speakers). Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username3486 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 13:49:26 2020 InstallationDate: Installed on 2020-10-30 (45 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Crossbeat Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Crossbeat, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 264.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.family: MacBook Air dmi.product.name: MacBookAir5,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+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 1908563] Re: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 Either way, the fix is coming in gnome-shell update 3.38.2 -- 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/1908563 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() Status in gnome-shell package in Ubuntu: New Bug description: - ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 21:17:56 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-10-07 (1167 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=uk_UA.UTF-8 PATH=(custom, user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2020-12-10T13:54:45.232978 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908563/+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 1906977] Re: moving cursor to dock causes desktop-icons graphic garbage
All sounds clean and normal. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1906977 Title: moving cursor to dock causes desktop-icons graphic garbage Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: More generally, desktop mis-displays 3 Variations: a) 0) open a window/app 1) minimise a window/application, causing Desktop to be visible 2) move cursor to dock (to open new app) As soon as cursor hits dock, the graphic of the minimised window (graphic that would be shown by activating "Activities") appears. It can be cleared by sweeping a window over the desktop. It only happens once, once for every time you minimise a window. b) Click "Acivities" - then click again to restore view As soon as cursor hits dock, desktop goes corrupt (large parts blank out) c) Close window As b) By attempting to move an icon on the Desktop, or pressing PrntScrn key, the Desktop repairs itself. Ubuntu 20.04.1 LTS Gnome 3.36.3 64-bit nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 12:11:40 2020 InstallationDate: Installed on 2016-09-01 (1556 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago) usr_lib_nautilus: dropbox 2018.11.08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906977/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
I doubt kernel 5.8.0-33 is the problem, because that was released in December but this bug has been reported since at least July. If anyone can reproduce this bug at all then please follow the steps in comment #11. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1908563] Re: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 That's the wrong bug. This is more likely bug 1898910 or bug 1898005. ** This bug is no longer a duplicate of bug 1867763 gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: assertion failed: (priv->child == NULL) ** This bug has been marked a duplicate of bug 1898005 gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] -- 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/1908563 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() Status in gnome-shell package in Ubuntu: New Bug description: - ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 21:17:56 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-10-07 (1167 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=uk_UA.UTF-8 PATH=(custom, user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2020-12-10T13:54:45.232978 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908563/+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 1908559] Re: Steam or discord: "pushModal: invocation of begin_modal failed"
Please run this command to collect more system info: apport-collect 1908559 See also; similar sounding bug 1824874. ** Package changed: steam (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1908559] [NEW] Steam or discord: "pushModal: invocation of begin_modal failed"
You have been subscribed to a public bug: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- Steam or discord: "pushModal: invocation of begin_modal failed" https://bugs.launchpad.net/bugs/1908559 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908617] [NEW] Scaling doesn't adjust when moved across Monitors with Different DPis
Public bug reported: When the window is moved across two monitors with different DPIs, the window inherits the scaling of the monitor it's opened in and doesn't readjust when it moves across the other monitor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: emacs (not installed) ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 18:52:52 2020 InstallationDate: Installed on 2020-11-18 (29 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1908617 Title: Scaling doesn't adjust when moved across Monitors with Different DPis Status in emacs package in Ubuntu: New Bug description: When the window is moved across two monitors with different DPIs, the window inherits the scaling of the monitor it's opened in and doesn't readjust when it moves across the other monitor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: emacs (not installed) ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 18:52:52 2020 InstallationDate: Installed on 2020-11-18 (29 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1908617/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Reverted mutter to focal-updates stock, rebooted into 5.8.0-33, repro'd again :( so we're back to the hypothesis that there's something wrong in 5.8.0-33. Sorry for the noise, I'm trying to debug this as best as I can. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Never mind, I think mutter 3.36.6-1ubuntu0.20.04.2+lizf1 is busted, please disregard :) on the plus side I have a reliable trigger. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Started seeing this recently with 5.8.0-33 after a few minutes logged into either Wayland or X11 session, regardless of other activity on system, but does not repro once I downgrade kernel to 5.8.0-31. Gnome shell version 3.36.4-1ubuntu1~20.04.2 has been the same throughout. Mutter likewise on 3.36.6-1ubuntu0.20.04.2 throughout. I did recompile mutter with pipewire support, no other changes, (https://launchpad.net/~lizthegrey/+archive/ubuntu/freedesktop/+sourcepub/11932034 /+listing-archive-extra), it was working fine, but is now triggering this. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1908608] Re: Crash to login screen when plugging in/out external monitor
I also ran 'ubuntu-bug /var/crash/_my_crash_report.crash' for my crash report, and was led to believe that a new bug would be created as a result (in another issue I was there told to "tell us the ID of the newly-created bug" after running that command), but I was given no information by the time the command finished. Did I miss a step in order to receive an ID? -- 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/1908608 Title: Crash to login screen when plugging in/out external monitor Status in gnome-shell package in Ubuntu: New Bug description: This matches the title of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I don't want to assume it is the same considering that was allegedly fixed three years ago. journal: dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8 dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 10 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 7 dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6 - bcm5974: client bug: event processing lagging behind by 42ms, your system is too slow dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 8 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 15 dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine nitrokey failed to change udev device /sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice: dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device dec 17 23:12:53 computer-name fwupd[3384]: Flags:none dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 0x55db60db91a0 == dec 17 23:13:06 computer-name nautilus[3814]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3089]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name org.kde.kdeconnect.daemon.desktop[3092]: The Wayland connection broke. Did the Wayland compositor die? dec 17 23:13:06 computer-name gsd-power[3032]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name polkitd(authority=local)[738]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.82, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale sv_SE.UTF-8) (disconnected from bus) dec 17 23:13:06 computer-name unknown[3020]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3031]: Error reading events from display: Brutet rör dec 17 23:13:06
[Desktop-packages] [Bug 1908608] Re: Crash to login screen when plugging in/out external monitor
When trying to mark this bug as private I get the message "The bug will become invisible because there is no-one with permissions to see Private bugs". Is that a mistake? Shouldn't someone be able to see it? -- 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/1908608 Title: Crash to login screen when plugging in/out external monitor Status in gnome-shell package in Ubuntu: New Bug description: This matches the title of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I don't want to assume it is the same considering that was allegedly fixed three years ago. journal: dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8 dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 10 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 7 dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6 - bcm5974: client bug: event processing lagging behind by 42ms, your system is too slow dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 8 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 15 dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine nitrokey failed to change udev device /sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice: dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device dec 17 23:12:53 computer-name fwupd[3384]: Flags:none dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 0x55db60db91a0 == dec 17 23:13:06 computer-name nautilus[3814]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3089]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name org.kde.kdeconnect.daemon.desktop[3092]: The Wayland connection broke. Did the Wayland compositor die? dec 17 23:13:06 computer-name gsd-power[3032]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name polkitd(authority=local)[738]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.82, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale sv_SE.UTF-8) (disconnected from bus) dec 17 23:13:06 computer-name unknown[3020]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3031]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3030]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3064]: Error reading events from display: Brutet rör
[Desktop-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
*** This bug is a duplicate of bug 1797002 *** https://bugs.launchpad.net/bugs/1797002 Thank you for the suggestion. I tried what you suggested in another bug (for gnome-shell) and got the message "The bug will become invisible because there is no-one with permissions to see Private bugs" -- is that option really a solution? Sounds like reports become pointless if that option is activated. -- 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/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms. Speakers work in Windows 10 / macOS 10.14+ running on same hardware. Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware. Remote control commands work (play/pause button on speakers). Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username3486 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 13:49:26 2020 InstallationDate: Installed on 2020-10-30 (45 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Crossbeat Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Crossbeat, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 264.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.family: MacBook Air dmi.product.name: MacBookAir5,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+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 1908608] [NEW] Crash to login screen when plugging in/out external monitor
Public bug reported: This matches the title of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I don't want to assume it is the same considering that was allegedly fixed three years ago. journal: dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8 dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 10 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 7 dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6 - bcm5974: client bug: event processing lagging behind by 42ms, your system is too slow dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 8 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 15 dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine nitrokey failed to change udev device /sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice: dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device dec 17 23:12:53 computer-name fwupd[3384]: Flags:none dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 0x55db60db91a0 == dec 17 23:13:06 computer-name nautilus[3814]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3089]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name org.kde.kdeconnect.daemon.desktop[3092]: The Wayland connection broke. Did the Wayland compositor die? dec 17 23:13:06 computer-name gsd-power[3032]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name polkitd(authority=local)[738]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.82, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale sv_SE.UTF-8) (disconnected from bus) dec 17 23:13:06 computer-name unknown[3020]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3031]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3030]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3064]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name systemd[2728]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE dec 17 23:13:06 computer-name systemd[2728]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV dec 17 23:13:06 computer-name systemd[2728]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE dec 17 23:13:06 computer-name systemd[2728]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE dec 17 23:13:06
[Desktop-packages] [Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/577 https://gitlab.gnome.org/Community/Ubuntu/gnome-software/-/merge_requests/33 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+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 1908278] Re: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed
** Summary changed: - [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed + Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed -- 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/1908278 Title: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As suggested by moderator Daniel van Vugt (vanvugt) I opened this new bug report: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.10 is available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Thanks for your great contribution to community and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908278/+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 1875717] Re: Opening file from Samba share results in Document in Use
I think you meant to link to the section about platform compatibility on Linux and how file:/// links are no longer silently treated as smb:/// links: https://wiki.documentfoundation.org/ReleaseNotes/7.0#Linux I am pretty sure that's a non-issue in PCManFM-Qt. -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
The cause is `gs_plugin_add_alternates` doesn't set the `snap::confinement` metadata item, so the channels other than the default aren't detected as classic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+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 1875717] Re: Opening file from Samba share results in Document in Use
I'm not entirely surprised at the read only thing (see https://ask.libreoffice.org/en/question/3827/doc-files-open-as-read- only/) though I'm a little surprised about the inconsistent behavior that under some file managers that happens and under others, it doesn't. That's not really relevant here, but may be worth some investigating. My past experience tells me that the dialog about the file being locked for editing comes up when someone using the share has the file open and someone else tries to open it. Another possibility is if someone has it open and then their system/LibreOffice crashes. I haven't investigated this but I suspect a lock file is being used to indicate whether or not it's being used. The output from PCManFM-Qt is actually quite useful. Those "file monitor cannot be created" warnings originate from some SMB-specific code. It would be interesting to compare this to what Thunar is doing, so if you could test it, that would be great. As always, thank you, Leó! -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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 1875717] Re: Opening file from Samba share results in Document in Use
Digging a bit deeper - checked out the release notes and known bugs at Libre Office and found this bit of info: Check the link below comments on Linux https://wiki.documentfoundation.org/ReleaseNotes/7.0#Configuration_changes And known bugs - https://bugs.documentfoundation.org/show_bug.cgi?id=115747 ** Bug watch added: Document Foundation Bugzilla #115747 https://bugs.documentfoundation.org/show_bug.cgi?id=115747 -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
** Changed in: snap-store-desktop Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snap-store-desktop Importance: High => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+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 1871009] Re: Firefox doesn't restart after update
Alas when updating to 84.0+build3-0ubuntu0.20.04.1 -- 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/1871009 Title: Firefox doesn't restart after update Status in firefox package in Ubuntu: Confirmed Bug description: After upgrading to firefox amd64 74.0.1+build1-0ubuntu0.18.04.1 (using apt-get), a message appeared in the running Firefox session: 'Firefox needs to be restarted' (as usual, nothing wrong with that). After clicking ok (or 'do it now' or what the exact message was), Firefox terminates. Expected behaviour: Firefox actually restarts Experienced behaviour: Nothing seemed to happen. Firefox terminated but never came back. (Starting Firefox again by hand worked flawlessly.) I have no profiles defined. I don't usually pass any options when starting Firefox. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 74.0.1+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fab3616 F pulseaudio /dev/snd/controlC1: fab3616 F pulseaudio BrokenPermissions: saved-telemetry-pings/a1103722-309c-47da-b9da-2bc9411237b9 (0o600, wrong owner) saved-telemetry-pings/e1cac187-9dd1-48b9-bb99-8c67374c7212 (0o600, wrong owner) saved-telemetry-pings/fbf7331c-39a9-4539-97fa-280e7d343563 (0o600, wrong owner) BuildID: 20200403064753 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 03:13:58 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-04-27 (1805 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.23.1 dev eth0 proto dhcp metric 100 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.23.0/24 dev eth0 proto kernel scope link src 192.168.23.136 metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-f8832267-2764-4f52-b9df-136771180712 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0.1/20200403064753 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-f8832267-2764-4f52-b9df-136771180712 bp-f03b7d3e-1a66-441d-be5d-cedc11180201 bp-610fb53c-4664-4692-8e37-62c501180107 bp-708689c3-ba2d-427e-a43b-605df2141112 bp-b2e12bb9-63b8-494d-9390-f5d722140521 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-08-18 (596 days ago) dmi.bios.date: 08/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P 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.:bvrF1:bd08/06/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871009/+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 1908563] Re: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1867763 *** https://bugs.launchpad.net/bugs/1867763 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1867763, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1908563/+attachment/5444630/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1908563/+attachment/5444632/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1908563/+attachment/5444636/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1908563/+attachment/5444637/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1908563/+attachment/5444638/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1908563/+attachment/5444640/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1908563/+attachment/5444641/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1867763 gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: assertion failed: (priv->child == NULL) ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1908563 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() Status in gnome-shell package in Ubuntu: New Bug description: - ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 21:17:56 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-10-07 (1167 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=uk_UA.UTF-8 PATH=(custom, user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2020-12-10T13:54:45.232978 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908563/+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 1908559] [NEW] Steam or discord: "pushModal: invocation of begin_modal failed"
Public bug reported: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` ** Affects: steam (Ubuntu) Importance: Undecided Status: New ** Package changed: mutter (Ubuntu) => ubuntu ** Description changed: - TBD + Roughly every 10 minutes two entries of the heading is printed to the logs + ``` + $ journalctl -b | grep "pushModal: invocation of begin_modal failed" + des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + ``` + + I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission + ``` + ps -ef | grep 8626 + centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell + centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim + centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox + centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam + ``` ** Package changed: ubuntu => steam (Ubuntu) -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in steam package in Ubuntu: New Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1908559/+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 1905054] Re: Firefox 83 Breaks WebGL
Setting gfx.webrender.all as recommended in the upstream bug makes it work. It seems some detection code is broken. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054] Re: Firefox 83 Breaks WebGL
Can anyone point me to where I can find the Firefox 82 debs? They seem to have disappeared from /var/cache/apt/archives, and I really need them. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
This bug was fixed in the package gnome-shell - 3.38.2-1ubuntu1 --- gnome-shell (3.38.2-1ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release (LP: #1908161): - Fixed crash in meta_window_actor_thaw (LP: #1897765) - Fixed crash in st_bin_destroy (LP: #1898005) * debian/patches: - Refreshed - Revert-appDisplay-baseAppView-Cleanup-animate.patch: + Revert a 3.38.2 change that proved to cause regressions - screenshot-Grab-screenshot-during-paint-on-X11.patch: + Correctly take screenshots for fullscreen games (LP: #1908164) * Remaining changes with debian: - Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming - Update debian/gbp.conf with Ubuntu settings - gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - optional-hot-corner.patch + enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch: + Fix crash on theme changes - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814) gnome-shell (3.38.2-1) unstable; urgency=medium * Team upload * New upstream release - Improve app picker spacing on larger resolutions - Don't add dialogs to the window preview more than once - Avoid cursor visibility changes on startup - Remove dead code in StButton, StEntry - Make FocusApp D-Bus method more reliable - Fix crashes with the desktop-icons extension (LP: #1898005, LP: #1898910) - Silence some warnings - Update translations: nb, zh_CN - Otherwise functionally equivalent to 3.38.1-3 * Drop patches that were included in the new upstream release * d/gbp.conf: Use upstream 3.38.x branch. Version 40~alpha was already released, so it's misleading to say that 3.38.x is the latest. * Standards-Version: 4.5.1 (no changes required) * Update Lintian overrides * Release to unstable gnome-shell (3.38.1-3) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-19-ge93b8263b - Fix a crash with message "Error in freeze/thaw accounting" - Don't crash if taking a per-window screenshot fails - Align audio device selection icons better - Fix typing replies into Telepathy notifications - Fix some memory leaks - Show screen-recorder indication, even in Xorg - Don't play message sounds when "Do not disturb" is enabled - Don't allow adding apps to favorites if they would be hidden anyway - Update translations: bn_IN, es, fur, pt gnome-shell (3.38.1-2) unstable; urgency=medium * debian/patches/modemManager_Add-property-getters.patch: - Cherry picked upstream commit to fix issue with missing "Mobile Broadband" item in the system menu (closes: #971511). [ Simon McVittie ] * d/control.in: Depend on gir1.2-gstreamer-1.0 (closes: #973463) -- Marco Trevisan (Treviño) Tue, 15 Dec 2020 02:42:26 +0100 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification
[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2
This bug was fixed in the package gnome-shell - 3.38.2-1ubuntu1 --- gnome-shell (3.38.2-1ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release (LP: #1908161): - Fixed crash in meta_window_actor_thaw (LP: #1897765) - Fixed crash in st_bin_destroy (LP: #1898005) * debian/patches: - Refreshed - Revert-appDisplay-baseAppView-Cleanup-animate.patch: + Revert a 3.38.2 change that proved to cause regressions - screenshot-Grab-screenshot-during-paint-on-X11.patch: + Correctly take screenshots for fullscreen games (LP: #1908164) * Remaining changes with debian: - Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming - Update debian/gbp.conf with Ubuntu settings - gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - optional-hot-corner.patch + enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch: + Fix crash on theme changes - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814) gnome-shell (3.38.2-1) unstable; urgency=medium * Team upload * New upstream release - Improve app picker spacing on larger resolutions - Don't add dialogs to the window preview more than once - Avoid cursor visibility changes on startup - Remove dead code in StButton, StEntry - Make FocusApp D-Bus method more reliable - Fix crashes with the desktop-icons extension (LP: #1898005, LP: #1898910) - Silence some warnings - Update translations: nb, zh_CN - Otherwise functionally equivalent to 3.38.1-3 * Drop patches that were included in the new upstream release * d/gbp.conf: Use upstream 3.38.x branch. Version 40~alpha was already released, so it's misleading to say that 3.38.x is the latest. * Standards-Version: 4.5.1 (no changes required) * Update Lintian overrides * Release to unstable gnome-shell (3.38.1-3) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-19-ge93b8263b - Fix a crash with message "Error in freeze/thaw accounting" - Don't crash if taking a per-window screenshot fails - Align audio device selection icons better - Fix typing replies into Telepathy notifications - Fix some memory leaks - Show screen-recorder indication, even in Xorg - Don't play message sounds when "Do not disturb" is enabled - Don't allow adding apps to favorites if they would be hidden anyway - Update translations: bn_IN, es, fur, pt gnome-shell (3.38.1-2) unstable; urgency=medium * debian/patches/modemManager_Add-property-getters.patch: - Cherry picked upstream commit to fix issue with missing "Mobile Broadband" item in the system menu (closes: #971511). [ Simon McVittie ] * d/control.in: Depend on gir1.2-gstreamer-1.0 (closes: #973463) -- Marco Trevisan (Treviño) Tue, 15 Dec 2020 02:42:26 +0100 ** Changed in: gnome-shell (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug
[Desktop-packages] [Bug 1898910] Re: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from Des
This bug was fixed in the package gnome-shell - 3.38.2-1ubuntu1 --- gnome-shell (3.38.2-1ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release (LP: #1908161): - Fixed crash in meta_window_actor_thaw (LP: #1897765) - Fixed crash in st_bin_destroy (LP: #1898005) * debian/patches: - Refreshed - Revert-appDisplay-baseAppView-Cleanup-animate.patch: + Revert a 3.38.2 change that proved to cause regressions - screenshot-Grab-screenshot-during-paint-on-X11.patch: + Correctly take screenshots for fullscreen games (LP: #1908164) * Remaining changes with debian: - Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming - Update debian/gbp.conf with Ubuntu settings - gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - optional-hot-corner.patch + enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch: + Fix crash on theme changes - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814) gnome-shell (3.38.2-1) unstable; urgency=medium * Team upload * New upstream release - Improve app picker spacing on larger resolutions - Don't add dialogs to the window preview more than once - Avoid cursor visibility changes on startup - Remove dead code in StButton, StEntry - Make FocusApp D-Bus method more reliable - Fix crashes with the desktop-icons extension (LP: #1898005, LP: #1898910) - Silence some warnings - Update translations: nb, zh_CN - Otherwise functionally equivalent to 3.38.1-3 * Drop patches that were included in the new upstream release * d/gbp.conf: Use upstream 3.38.x branch. Version 40~alpha was already released, so it's misleading to say that 3.38.x is the latest. * Standards-Version: 4.5.1 (no changes required) * Update Lintian overrides * Release to unstable gnome-shell (3.38.1-3) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-19-ge93b8263b - Fix a crash with message "Error in freeze/thaw accounting" - Don't crash if taking a per-window screenshot fails - Align audio device selection icons better - Fix typing replies into Telepathy notifications - Fix some memory leaks - Show screen-recorder indication, even in Xorg - Don't play message sounds when "Do not disturb" is enabled - Don't allow adding apps to favorites if they would be hidden anyway - Update translations: bn_IN, es, fur, pt gnome-shell (3.38.1-2) unstable; urgency=medium * debian/patches/modemManager_Add-property-getters.patch: - Cherry picked upstream commit to fix issue with missing "Mobile Broadband" item in the system menu (closes: #971511). [ Simon McVittie ] * d/control.in: Depend on gir1.2-gstreamer-1.0 (closes: #973463) -- Marco Trevisan (Treviño) Tue, 15 Dec 2020 02:42:26 +0100 ** Changed in: gnome-shell (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug
[Desktop-packages] [Bug 1905054] Re: Firefox 83 Breaks WebGL
The Firefox 84 WebGL section looks a lot like the v83 section: HW_COMPOSITING available by default blocked by env: Acceleration blocked by platform OPENGL_COMPOSITING unavailable by default: Hardware compositing is disabled WEBRENDER available by default disabled by env: Not qualified WEBRENDER_QUALIFIED available by default denied by env: Not on allowlist WEBRENDER_COMPOSITOR disabled by default: Disabled by default WEBRENDER_ANGLE available by default unavailable by env: OS not supported WEBRENDER_DCOMP_PRESENT available by default disabled by user: User disabled via pref unavailable by env: Requires Windows 10 or later unavailable by runtime: Requires ANGLE WEBRENDER_SOFTWARE available by default denied by env: Not on allowlist OMTP available by default WEBGPU disabled by default: Disabled by default blocked by runtime: WebGPU can only be enabled in nightly -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1905054] Re: Firefox 83 Breaks WebGL
Despite it working in The Firefox 84 beta, the Ubuntu build that came out does not work. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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 1908161] Re: Update to 3.38.2
This bug was fixed in the package gnome-shell - 3.38.2-1ubuntu1 --- gnome-shell (3.38.2-1ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release (LP: #1908161): - Fixed crash in meta_window_actor_thaw (LP: #1897765) - Fixed crash in st_bin_destroy (LP: #1898005) * debian/patches: - Refreshed - Revert-appDisplay-baseAppView-Cleanup-animate.patch: + Revert a 3.38.2 change that proved to cause regressions - screenshot-Grab-screenshot-during-paint-on-X11.patch: + Correctly take screenshots for fullscreen games (LP: #1908164) * Remaining changes with debian: - Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming - Update debian/gbp.conf with Ubuntu settings - gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - optional-hot-corner.patch + enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch: + Fix crash on theme changes - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814) gnome-shell (3.38.2-1) unstable; urgency=medium * Team upload * New upstream release - Improve app picker spacing on larger resolutions - Don't add dialogs to the window preview more than once - Avoid cursor visibility changes on startup - Remove dead code in StButton, StEntry - Make FocusApp D-Bus method more reliable - Fix crashes with the desktop-icons extension (LP: #1898005, LP: #1898910) - Silence some warnings - Update translations: nb, zh_CN - Otherwise functionally equivalent to 3.38.1-3 * Drop patches that were included in the new upstream release * d/gbp.conf: Use upstream 3.38.x branch. Version 40~alpha was already released, so it's misleading to say that 3.38.x is the latest. * Standards-Version: 4.5.1 (no changes required) * Update Lintian overrides * Release to unstable gnome-shell (3.38.1-3) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-19-ge93b8263b - Fix a crash with message "Error in freeze/thaw accounting" - Don't crash if taking a per-window screenshot fails - Align audio device selection icons better - Fix typing replies into Telepathy notifications - Fix some memory leaks - Show screen-recorder indication, even in Xorg - Don't play message sounds when "Do not disturb" is enabled - Don't allow adding apps to favorites if they would be hidden anyway - Update translations: bn_IN, es, fur, pt gnome-shell (3.38.1-2) unstable; urgency=medium * debian/patches/modemManager_Add-property-getters.patch: - Cherry picked upstream commit to fix issue with missing "Mobile Broadband" item in the system menu (closes: #971511). [ Simon McVittie ] * d/control.in: Depend on gir1.2-gstreamer-1.0 (closes: #973463) -- Marco Trevisan (Treviño) Tue, 15 Dec 2020 02:42:26 +0100 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification
[Desktop-packages] [Bug 1908500] Re: libxslt.a missing from libxslt1-dev
** Changed in: libxslt (Ubuntu) Status: New => Incomplete -- 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 1908278] Re: [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed
@albertomilone the debian nvidia-legacy-340xx-kernel-dkms (340.108-10) package builds and installs successfully with the ubuntu 5.10.0-9.10 bootstrap kernel on amd64. -- 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/1908278 Title: [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As suggested by moderator Daniel van Vugt (vanvugt) I opened this new bug report: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.10 is available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Thanks for your great contribution to community and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908278/+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 1908278] Re: [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- 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/1908278 Title: [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As suggested by moderator Daniel van Vugt (vanvugt) I opened this new bug report: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.10 is available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Thanks for your great contribution to community and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908278/+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 1908278] Re: [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed
This isn't solved until the patches are added to the ubuntu package, right? Please unmark it as solved until debian's package is imported into ubuntu? -- 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/1908278 Title: [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As suggested by moderator Daniel van Vugt (vanvugt) I opened this new bug report: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.10 is available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Thanks for your great contribution to community and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908278/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
On the Firefox issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1640535 > There is now quite a lot of input delay. Touch-typists typing with one hand on each keyboard will easily out-pace Firefox's ability to display what they are typing. The problem persists until Firefox is restarted. That is exactly what's happening to me, and it looks like it's their bug. Sorry about that! -- 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/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
Hey there, thanks for the discussion, it's helped me find a way around this problem. I also use an R-Go split keyboard. I had the input lag issue OS-wide on Elementary OS and Pop OS. The issue disappears on Wayland. After switching to Regolith, which uses gnome-flashback, the issue is no longer there. There is one big exception, though: there's still the same problem on Firefox! All other apps are doing just fine. I wonder whether I can somehow overcome the problem on Firefox as well. I'm no longer sure whether it's a problem in the interaction between Firefox and Xorg or it's a Firefox-specific problem. ** Bug watch added: Mozilla Bugzilla #1640535 https://bugzilla.mozilla.org/show_bug.cgi?id=1640535 -- 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/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1908553] [NEW] Wireless/Ethernet icon shows no internet
Public bug reported: I'm currently connected to wifi & ethernet cable and we know that in wifi the triage has white color showing the wireless strength. But in my case, there is a question mark "?" in wifi symbol. Even in the ethernet, it (ethernet icon) shows that there is no internet connection while there is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 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 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 22:50:11 2020 InstallationDate: Installed on 2020-05-04 (227 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1908553 Title: Wireless/Ethernet icon shows no internet Status in network-manager package in Ubuntu: New Bug description: I'm currently connected to wifi & ethernet cable and we know that in wifi the triage has white color showing the wireless strength. But in my case, there is a question mark "?" in wifi symbol. Even in the ethernet, it (ethernet icon) shows that there is no internet connection while there is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 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 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 22:50:11 2020 InstallationDate: Installed on 2020-05-04 (227 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1908553/+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 1908278] Re: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed
Hello everyone, great Butterfly (kelebek333) again! Thanks to him we can continue to use our old but still good graphic card with latest 5.10.x LTS kernels also in Groovy: https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-legacy Testing updated drivers since this morning and working great! I think this bug report may be considered solved unless Ubuntu decides to make official drivers available. ** Summary changed: - Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed + [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed -- 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/1908278 Title: [SOLVED] Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: As suggested by moderator Daniel van Vugt (vanvugt) I opened this new bug report: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.10 is available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Thanks for your great contribution to community and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908278/+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 1908476] Re: Memory leaks in Xorg
** Project changed: canonical-identity-provider => xorg-server (Ubuntu) -- 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/1908476 Title: Memory leaks in Xorg Status in xorg-server package in Ubuntu: New Bug description: Memory leaks in Xorg Hi, Everyone. I'm working software developer. I'm having a problem right now. Continuing to decode H.264 using ffmeg and libva causes a memory leak in Xorg. This is especially likely to occur when the resolution is scaled (both UP and Down). The settings of 20-intel.conf are as follows. [20-intel.conf] -- Section "Device" Identifier "Card0" Driver "intel" BusID "PCI:0:2:0" Option "AccelMethod" "sna" Option "SwapbuffersWait" "False" Option "TearFree" "True" EndSection -- If you do not set TearFree, memory leaks will not occur, but tearing will occur. It does not occur on Ubuntu 16.04 with the same settings. Is there a way to eliminate the memory leak and prevent screen tearing? [TOP Command Result] -- DATETME PR NI VIRTRES SHR S %CPU%MEM TIME+ COMMAND 10:34:44 20 0 553532 36340 21692 S 20.00.5 4:33.33 Xorg 10:34:49 20 0 553724 36340 21692 S 20.20.5 4:34.34 Xorg 10:34:54 20 0 553724 36340 21692 S 20.10.5 4:35.35 Xorg 10:34:59 20 0 554112 36340 21692 S 20.10.5 4:36.36 Xorg 10:35:05 20 0 554112 36496 21756 S 20.20.5 4:37.38 Xorg 10:35:10 20 0 554112 36496 21756 S 20.10.5 4:38.39 Xorg 10:35:15 20 0 554112 36496 21756 S 20.00.5 4:39.39 Xorg 10:35:20 20 0 554368 36496 21756 S 20.20.5 4:40.40 Xorg 10:35:25 20 0 554368 36496 21756 S 20.10.5 4:41.41 Xorg 10:35:30 20 0 554368 36496 21756 S 20.70.5 4:42.45 Xorg 10:35:35 20 0 555076 36660 21800 S 19.80.5 4:43.45 Xorg 10:35:40 20 0 555076 36660 21800 S 20.00.5 4:44.45 Xorg 10:35:45 20 0 555076 36660 21800 S 20.10.5 4:45.46 Xorg 10:35:50 20 0 555076 36660 21800 S 20.10.5 4:46.47 Xorg 10:35:55 20 0 555076 36808 21860 S 19.80.5 4:47.47 Xorg 10:36:00 20 0 554692 36700 21748 S 19.80.5 4:48.46 Xorg 10:36:05 20 0 554824 36700 21748 S 19.70.5 4:49.46 Xorg 10:36:10 20 0 554824 36700 21748 R 20.50.5 4:50.49 Xorg 10:36:15 20 0 554824 36700 21748 S 19.70.5 4:51.48 Xorg 10:36:20 20 0 554824 36844 21812 S 20.00.5 4:52.49 Xorg 10:36:25 20 0 554312 36812 21748 S 19.90.5 4:53.49 Xorg 10:36:30 20 0 554312 36812 21748 S 20.00.5 4:54.49 Xorg 10:36:35 20 0 555400 36948 21856 S 20.10.5 4:55.51 Xorg 10:36:40 20 0 32 36948 21856 S 19.90.5 4:56.51 Xorg 10:36:45 20 0 32 36948 21856 S 19.80.5 4:57.50 Xorg 10:36:50 20 0 32 36948 21856 S 20.40.5 4:58.53 Xorg 10:36:55 20 0 555020 37004 21820 S 19.90.5 4:59.53 Xorg 10:37:00 20 0 555020 37004 21820 S 19.70.5 5:00.52 Xorg 10:37:05 20 0 555020 37004 21820 S 20.80.5 5:01.57 Xorg 10:37:10 20 0 554700 36984 21748 S 19.10.5 5:02.53 Xorg 10:37:15 20 0 554640 37012 21756 S 19.90.5 5:03.53 Xorg 10:37:20 20 0 555728 37144 21876 S 19.80.5 5:04.54 Xorg 10:37:25 20 0 555728 37144 21876 S 20.00.5 5:05.55 Xorg 10:37:30 20 0 555728 37144 21876 S 19.90.5 5:06.55 Xorg 10:37:35 20 0 555728 37144 21876 S 20.60.5 5:07.58 Xorg 10:37:40 20 0 555728 37144 21876 S 19.90.5 5:08.58 Xorg 10:37:46 20 0 555600 37248 21876 S 20.00.5 5:09.59 Xorg 10:37:51 20 0 555924 37248 21876 S
[Desktop-packages] [Bug 1908476] [NEW] Memory leaks in Xorg
You have been subscribed to a public bug: Memory leaks in Xorg Hi, Everyone. I'm working software developer. I'm having a problem right now. Continuing to decode H.264 using ffmeg and libva causes a memory leak in Xorg. This is especially likely to occur when the resolution is scaled (both UP and Down). The settings of 20-intel.conf are as follows. [20-intel.conf] -- Section "Device" Identifier "Card0" Driver "intel" BusID "PCI:0:2:0" Option "AccelMethod" "sna" Option "SwapbuffersWait" "False" Option "TearFree" "True" EndSection -- If you do not set TearFree, memory leaks will not occur, but tearing will occur. It does not occur on Ubuntu 16.04 with the same settings. Is there a way to eliminate the memory leak and prevent screen tearing? [TOP Command Result] -- DATETME PR NI VIRTRES SHR S %CPU%MEMTIME+ COMMAND 10:34:4420 0 553532 36340 21692 S 20.00.5 4:33.33 Xorg 10:34:4920 0 553724 36340 21692 S 20.20.5 4:34.34 Xorg 10:34:5420 0 553724 36340 21692 S 20.10.5 4:35.35 Xorg 10:34:5920 0 554112 36340 21692 S 20.10.5 4:36.36 Xorg 10:35:0520 0 554112 36496 21756 S 20.20.5 4:37.38 Xorg 10:35:1020 0 554112 36496 21756 S 20.10.5 4:38.39 Xorg 10:35:1520 0 554112 36496 21756 S 20.00.5 4:39.39 Xorg 10:35:2020 0 554368 36496 21756 S 20.20.5 4:40.40 Xorg 10:35:2520 0 554368 36496 21756 S 20.10.5 4:41.41 Xorg 10:35:3020 0 554368 36496 21756 S 20.70.5 4:42.45 Xorg 10:35:3520 0 555076 36660 21800 S 19.80.5 4:43.45 Xorg 10:35:4020 0 555076 36660 21800 S 20.00.5 4:44.45 Xorg 10:35:4520 0 555076 36660 21800 S 20.10.5 4:45.46 Xorg 10:35:5020 0 555076 36660 21800 S 20.10.5 4:46.47 Xorg 10:35:5520 0 555076 36808 21860 S 19.80.5 4:47.47 Xorg 10:36:0020 0 554692 36700 21748 S 19.80.5 4:48.46 Xorg 10:36:0520 0 554824 36700 21748 S 19.70.5 4:49.46 Xorg 10:36:1020 0 554824 36700 21748 R 20.50.5 4:50.49 Xorg 10:36:1520 0 554824 36700 21748 S 19.70.5 4:51.48 Xorg 10:36:2020 0 554824 36844 21812 S 20.00.5 4:52.49 Xorg 10:36:2520 0 554312 36812 21748 S 19.90.5 4:53.49 Xorg 10:36:3020 0 554312 36812 21748 S 20.00.5 4:54.49 Xorg 10:36:3520 0 555400 36948 21856 S 20.10.5 4:55.51 Xorg 10:36:4020 0 32 36948 21856 S 19.90.5 4:56.51 Xorg 10:36:4520 0 32 36948 21856 S 19.80.5 4:57.50 Xorg 10:36:5020 0 32 36948 21856 S 20.40.5 4:58.53 Xorg 10:36:5520 0 555020 37004 21820 S 19.90.5 4:59.53 Xorg 10:37:0020 0 555020 37004 21820 S 19.70.5 5:00.52 Xorg 10:37:0520 0 555020 37004 21820 S 20.80.5 5:01.57 Xorg 10:37:1020 0 554700 36984 21748 S 19.10.5 5:02.53 Xorg 10:37:1520 0 554640 37012 21756 S 19.90.5 5:03.53 Xorg 10:37:2020 0 555728 37144 21876 S 19.80.5 5:04.54 Xorg 10:37:2520 0 555728 37144 21876 S 20.00.5 5:05.55 Xorg 10:37:3020 0 555728 37144 21876 S 19.90.5 5:06.55 Xorg 10:37:3520 0 555728 37144 21876 S 20.60.5 5:07.58 Xorg 10:37:4020 0 555728 37144 21876 S 19.90.5 5:08.58 Xorg 10:37:4620 0 555600 37248 21876 S 20.00.5 5:09.59 Xorg 10:37:5120 0 555924 37248 21876 S 20.00.5 5:10.59 Xorg 10:37:5620 0 555924 37248 21876 S 20.40.5 5:11.61 Xorg 10:38:0120 0 555924 37248 21876 S 20.50.5 5:12.64 Xorg 10:38:0620 0 555924 37248 21876 S 19.80.5 5:13.64 Xorg 10:38:1120 0 555924
[Desktop-packages] [Bug 335662] Re: [jaunty] hplip status service cannot find system tray
Ubuntu 20.04.1 just started throwing this error this morning. What gives??? Looks like this was fixed 10 years ago?!? This is now like the 7th or 8th bug that's recurred since the disastrous mid September updates to 20.04! C'mon! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/335662 Title: [jaunty] hplip status service cannot find system tray Status in HPLIP: Fix Released Status in hplip package in Ubuntu: Fix Released Status in hplip package in Debian: Fix Released Bug description: Binary package hint: hplip After login to ubuntu hplip status service cannot find system tray. It shows dialog box: "No system tray detected on this system. Unable to start, exiting". hplip version is 2.8.12-3ubuntu1 on jaunty I found the same bug reported in Debian http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg618714.html Regards To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/335662/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
I got it working flawlessly by switching to Wayland. >From the DisplayLink installation instructions page (https://support.displaylink.com/knowledgebase/articles/684649): "Current version supports Wayland and it is recommended to use it." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+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 1837974] Re: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)
*** This bug is a duplicate of bug 1698083 *** https://bugs.launchpad.net/bugs/1698083 Still not solved in Ubuntu 20.10. -- 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/1837974 Title: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Double-clicking a window title-bar now fully-maximizes the window, even though the action is set to "Toggle Maximize Vertically" or "Toggle Maximize Horizontally". In other words, those options now behave just like "Toggle Maximize". This problem started after I upgraded from Ubuntu 18.10 (gnome-shell 3.30?) to Ubuntu 19.04 (gnome-shell 3.32.1). STEPS TO REPRODUCE: 1. Run gnome-tweaks 2. Click "Window Titlebars" in left menu panel 3. Set "Titlebar Actions ... Double-Click" to "Toggle Maximize Vertically" 4. Double-click a gnome-terminal titlebar RESULTS: WIndow maximizes fully (fills entire screen) EXPECTED RESULTS: Maximize in vertical direction only. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 22:53:16 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (477 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837974/+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 1908535] [NEW] Xorg crash after clean Ubuntu 20.10 install on Intel system
Public bug reported: Intel Core i5/8GB/256GB. Each time a minute or so after I boot into the system, I get a system error, but there are no useful details. The only thing I found is a crash log: https://pastebin.com/W54KDMGE Since there does not seem to be much readible stuff in there for a common person, I cannot determine whether or not this bug has been reported already. How can I prevent this bug from happening? I also tried to run sudo ubuntu-bug xorg. That did not work: $ sudo ubuntu-bug xorg cat: /var/log/lightdm/x-0-greeter.log: No such file or directory cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Description changed: Intel Core i5/8GB/256GB. Each time a minute or so after I boot into the system, I get a system error, but there are no useful details. The only thing I found is a crash log: https://pastebin.com/W54KDMGE + Since there does not seem to be much readible stuff in there for a + common person, I cannot determine whether or not this bug has been + reported already. + How can I prevent this bug from happening? + + I also tried to run sudo ubuntu-bug xorg. That did not work: + $ sudo ubuntu-bug xorg + cat: /var/log/lightdm/x-0-greeter.log: No such file or directory + cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory -- 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/1908535 Title: Xorg crash after clean Ubuntu 20.10 install on Intel system Status in xorg-server package in Ubuntu: New Bug description: Intel Core i5/8GB/256GB. Each time a minute or so after I boot into the system, I get a system error, but there are no useful details. The only thing I found is a crash log: https://pastebin.com/W54KDMGE Since there does not seem to be much readible stuff in there for a common person, I cannot determine whether or not this bug has been reported already. How can I prevent this bug from happening? I also tried to run sudo ubuntu-bug xorg. That did not work: $ sudo ubuntu-bug xorg cat: /var/log/lightdm/x-0-greeter.log: No such file or directory cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908535/+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 1906977] Re: moving cursor to dock causes desktop-icons graphic garbage
1. gnome extensions? - found it I have 3: Desktop Icons UbuntuAppIndicators Ubuntu Dock -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1906977 Title: moving cursor to dock causes desktop-icons graphic garbage Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: More generally, desktop mis-displays 3 Variations: a) 0) open a window/app 1) minimise a window/application, causing Desktop to be visible 2) move cursor to dock (to open new app) As soon as cursor hits dock, the graphic of the minimised window (graphic that would be shown by activating "Activities") appears. It can be cleared by sweeping a window over the desktop. It only happens once, once for every time you minimise a window. b) Click "Acivities" - then click again to restore view As soon as cursor hits dock, desktop goes corrupt (large parts blank out) c) Close window As b) By attempting to move an icon on the Desktop, or pressing PrntScrn key, the Desktop repairs itself. Ubuntu 20.04.1 LTS Gnome 3.36.3 64-bit nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 12:11:40 2020 InstallationDate: Installed on 2016-09-01 (1556 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago) usr_lib_nautilus: dropbox 2018.11.08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906977/+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 1906977] Re: moving cursor to dock causes desktop-icons graphic garbage
Daniel, 1. - sorry, where do I find extensions app? 2. I have 3 files: application_state gnome-overrides-migrated notifications -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1906977 Title: moving cursor to dock causes desktop-icons graphic garbage Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: More generally, desktop mis-displays 3 Variations: a) 0) open a window/app 1) minimise a window/application, causing Desktop to be visible 2) move cursor to dock (to open new app) As soon as cursor hits dock, the graphic of the minimised window (graphic that would be shown by activating "Activities") appears. It can be cleared by sweeping a window over the desktop. It only happens once, once for every time you minimise a window. b) Click "Acivities" - then click again to restore view As soon as cursor hits dock, desktop goes corrupt (large parts blank out) c) Close window As b) By attempting to move an icon on the Desktop, or pressing PrntScrn key, the Desktop repairs itself. Ubuntu 20.04.1 LTS Gnome 3.36.3 64-bit nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 12:11:40 2020 InstallationDate: Installed on 2016-09-01 (1556 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago) usr_lib_nautilus: dropbox 2018.11.08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906977/+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 1907870] Re: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9
** Attachment added: "Xrandr output with Plasma" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1907870/+attachment/580/+files/plasmaxrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1907870 Title: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9 Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00
[Desktop-packages] [Bug 1875717] Re: Opening file from Samba share results in Document in Use
@wxl Walter Again I retested and had acloser look at your suggestion nr2 - After input: pcmanfm-qt --profile=lxqt 2>&1 I received the following messages when connecting to the Samba share and opening a file : isPrimaryInstance Icon theme "elementary" not found. shortcut is dir: smb://storhofdi.local:445/ operation finished: 0x0 delete MountOperation file monitor cannot be created: Operation not supported ask password operation finished: 0x0 delete MountOperation file monitor cannot be created: Operation not supported file monitor cannot be created: Operation not supported file monitor cannot be created: Operation not supported file monitor cannot be created: Operation not supported javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx Icon theme "elementary" not found. Any suggestions? -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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
Could you please describe: * Which release you are basing this bug on? * Describe why you'd want the static library? I'm somewhat quite against static libraries as much as possible if people can do without. On Thu, 17 Dec 2020, 10:41 am Graham Inggs, <1908...@bugs.launchpad.net> wrote: > It seems this was intentional, from debian/changelog: > > > libxslt (1.1.34-1) experimental; urgency=medium > > ... > * Stop building and installing the static library. > ... > > -- Mattia Rizzolo Mon, 25 Nov 2019 19:22:08 +0100 > > -- > You received this bug notification because you are subscribed to Ubuntu. > https://bugs.launchpad.net/bugs/1908500 > > Title: > libxslt.a missing from libxslt1-dev > > Status in libxslt package in Ubuntu: > New > > 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 > > -- 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: New 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 1844136] Re: [eoan] Thunderbird 68.0 does not include attachment coming from an external app
Bug seems still/again to be present.
Ubuntu Mate 20.04
Tried Thunderd versions:
- TB 68.10.0 from regular repository
- TB 78.5.1 from PPA ubuntu-mozilla-security/ppa
Tried to launch Composer from LibreOffice Menu ("send as PDF"):
- composer window shows up, but deserved attechment is missing
Tried to launch Composer from command line with parameters "to", "from",
"subject", "attachment":
- composer window shows up
- "to", "from", "subject" beeing set as expected
- no file attached
With Evolution adding attachments works as expected in all cases.
--
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/1844136
Title:
[eoan] Thunderbird 68.0 does not include attachment coming from an
external app
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
(Eoan up-to-date, GNOME session)
When I choose to "send to" my PDF or image from Eog or Evince
(probably others too), TB 68 new message window appears but no file is
attached. Same issue inside Nautilus (right-click on a file, send to).
Was fully ok with TB 60.* .
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1844136/+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 1896167] Re: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B
It's kernel 5.10 apparently. -- 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/1896167 Title: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B. That's after working around bug 1896164. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1896167/+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 1875717] Re: Opening file from Samba share results in Document in Use
@wxl Walter Ran some tests again today. 1.Connected to the Samba share manually and no problem mounting etc. Opened the share directly from LibreOffice Writer and the file came up as "read only" but this time no dialog box. 2. Proceeded onto your second suggestion - and got the same result - file opened in "read only " mode and no dialog box. Of interest is that if the share is mounted by PCManFM-Qt or thunar the file opens with the dialog box as in the original report. 3. Did not test thunar. :) -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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
It seems this was intentional, from debian/changelog: libxslt (1.1.34-1) experimental; urgency=medium ... * Stop building and installing the static library. ... -- Mattia Rizzolo Mon, 25 Nov 2019 19:22:08 +0100 -- 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: New 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 1902244] Re: Backport packages for 20.04.2 HWE stack
the wlroots build regression is fixed by the libglvnd update here -- 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/1902244 Title: Backport packages for 20.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libglvnd package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in libglvnd source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Confirmed Bug description: [Impact] These are needed for 20.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm libglvnd: mostly just EGL headers sync from Khronos, needed by mesa mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1908502] [NEW] [MIR] libtiff5 dependency on libdeflate0
Public bug reported: tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as a dependency to libtiff5, making the package uninstallable. Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate support to make libtiff5 installable again. Either this package stays this way, or it needs a MIR for libdeflate. ** Affects: libdeflate (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: tiff (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: rls-hh-incoming ** Also affects: libdeflate (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-hh-incoming ** Changed in: libdeflate (Ubuntu) Status: New => Incomplete ** Changed in: tiff (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libtiff5 dependency on libdeflate0 Status in libdeflate package in Ubuntu: Incomplete Status in tiff package in Ubuntu: Confirmed Bug description: tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as a dependency to libtiff5, making the package uninstallable. Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate support to make libtiff5 installable again. Either this package stays this way, or it needs a MIR for libdeflate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+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] [NEW] libxslt.a missing from libxslt1-dev
Public bug reported: The libxslt.a file is missing from 1.1.34 ** Affects: libxslt (Ubuntu) Importance: Undecided Status: New ** Summary changed: - libxslt.a missing from libxslt2-dev + libxslt.a missing from libxslt1-dev -- 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: New 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 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.9 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 pulseaudio package in Ubuntu: Fix Committed 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 Committed 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] 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.2 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 pulseaudio package in Ubuntu: Fix Committed 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 Committed 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] 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
