[Desktop-packages] [Bug 1882042] Re: [SRU] Linux, Ubuntu, 18.4, CI, OLP15, PRTS, Audio/video is out of sync/lag when enter Suspend during playback
** Changed in: pulseaudio (Ubuntu Bionic) Status: New => Fix Committed -- 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/1882042 Title: [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag when enter Suspend during playback Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Users reported the audio and video is out of sync when entering suspend during playback on bionic. [Fix] The mainline pulseaudio already has the fix for this issue, and the fix is already in the eoan, focal and groovy, but it is not in the bionic. [Test Case] open a online video on the firefox, while it is playing, suspend the system, wait for 30 seconds, resume the system, the audio and video is still on the sync. [Regression Risk] Low, these 2 patches are already in the mainline pulseaudio, and already in the eoan, focal and groovy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882042/+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 1883369] Re: Weird font rendering on certain website with firefox
** Bug watch added: Mozilla Bugzilla #1645969 https://bugzilla.mozilla.org/show_bug.cgi?id=1645969 -- 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/1883369 Title: Weird font rendering on certain website with firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: When hovering some elements, some letters moves slightly. A gif explains better than words here: https://trancart.eu/lutim/l7qWMFQF/7Q9YJRUn.gif I reproduce this at least on twitter and gitlab.com, but I remember having it on other websites. My OS: kubuntu 20.04 Reproduced on both firefox dev edition and firefox from apt package. Sorry in advance if it is not the correct place, I have no idea where to report that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 77.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: augustin 4577 F pulseaudio BuildID: 2020060727 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Sat Jun 13 16:14:37 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-10 (1310 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.254 dev enp0s31f6 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 docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.4 metric 100 MostRecentCrashID: bp-9faa8c77-de9e-4f98-9e75-033440200610 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=68.0/20190627143605 (Out of date) Profile1 - LastVersion=78.0/20200609215727 (Out of date) Profile0 (Default) - LastVersion=77.0.1/2020060727 (In use) Profile2 - LastVersion=60.5.2/20190221164337 (Out of date) Profile4 - LastVersion=72.0.1/20200107212822 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-05-09 (34 days ago) dmi.bios.date: 05/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET51W (1.25 ) dmi.board.asset.tag:
[Desktop-packages] [Bug 1883369]
Thanks for filing the mozregression issue. I'm afraid I can't help with it but hopefully somebody can on that bug. In the meantime, could you try setting `layers.acceleration.force- enabled=true` in about:config, restart firefox, and see if it reproduces. Then after that, try setting `gfx.webrender.all=true`, restart, and see if it reproduces. -- 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/1883369 Title: Weird font rendering on certain website with firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: When hovering some elements, some letters moves slightly. A gif explains better than words here: https://trancart.eu/lutim/l7qWMFQF/7Q9YJRUn.gif I reproduce this at least on twitter and gitlab.com, but I remember having it on other websites. My OS: kubuntu 20.04 Reproduced on both firefox dev edition and firefox from apt package. Sorry in advance if it is not the correct place, I have no idea where to report that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 77.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: augustin 4577 F pulseaudio BuildID: 2020060727 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Sat Jun 13 16:14:37 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-10 (1310 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.254 dev enp0s31f6 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 docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.4 metric 100 MostRecentCrashID: bp-9faa8c77-de9e-4f98-9e75-033440200610 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=68.0/20190627143605 (Out of date) Profile1 - LastVersion=78.0/20200609215727 (Out of date) Profile0 (Default) - LastVersion=77.0.1/2020060727 (In use) Profile2 - LastVersion=60.5.2/20190221164337 (Out of date) Profile4 - LastVersion=72.0.1/20200107212822 (Out
[Desktop-packages] [Bug 1883369]
I have the same problem. For me `layers.acceleration.force-enabled=true` solves this font problem, but generates another. Now in all menus, the mouseover/hover highlighting/selection of the menus is sometimes not shown (For example: Right click on the website, move your mouse over the menu items. The highlighting does not always follow the mouse and gets stuck in previous items) Additionally using `gfx.webrender.all=true` doesn't solve that problem. But I prefer this problem over the strange fonts in websites. -- 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/1883369 Title: Weird font rendering on certain website with firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: When hovering some elements, some letters moves slightly. A gif explains better than words here: https://trancart.eu/lutim/l7qWMFQF/7Q9YJRUn.gif I reproduce this at least on twitter and gitlab.com, but I remember having it on other websites. My OS: kubuntu 20.04 Reproduced on both firefox dev edition and firefox from apt package. Sorry in advance if it is not the correct place, I have no idea where to report that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 77.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: augustin 4577 F pulseaudio BuildID: 2020060727 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Sat Jun 13 16:14:37 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-10 (1310 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.254 dev enp0s31f6 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 docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.4 metric 100 MostRecentCrashID: bp-9faa8c77-de9e-4f98-9e75-033440200610 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=68.0/20190627143605 (Out of date) Profile1 - LastVersion=78.0/20200609215727 (Out of date) Profi
[Desktop-packages] [Bug 1883369]
> layers.acceleration.force-enabled=true this fixes the issue. > gfx.webrender.all=true this also fixes the issue. So : I reproduce the issue if and only if **both** are false. Additionally I **don't** reproduce on nightly, with both variables set to false. -- 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/1883369 Title: Weird font rendering on certain website with firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: When hovering some elements, some letters moves slightly. A gif explains better than words here: https://trancart.eu/lutim/l7qWMFQF/7Q9YJRUn.gif I reproduce this at least on twitter and gitlab.com, but I remember having it on other websites. My OS: kubuntu 20.04 Reproduced on both firefox dev edition and firefox from apt package. Sorry in advance if it is not the correct place, I have no idea where to report that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 77.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: augustin 4577 F pulseaudio BuildID: 2020060727 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Sat Jun 13 16:14:37 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-10 (1310 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.254 dev enp0s31f6 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 docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.4 metric 100 MostRecentCrashID: bp-9faa8c77-de9e-4f98-9e75-033440200610 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=68.0/20190627143605 (Out of date) Profile1 - LastVersion=78.0/20200609215727 (Out of date) Profile0 (Default) - LastVersion=77.0.1/2020060727 (In use) Profile2 - LastVersion=60.5.2/20190221164337 (Out of date) Profile4 - LastVersion=72.0.1/20200107212822 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus
[Desktop-packages] [Bug 1883369]
In the meantime, I opened https://bugzilla.mozilla.org/show_bug.cgi?id=1645969 for my mozregression problem. -- 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/1883369 Title: Weird font rendering on certain website with firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: When hovering some elements, some letters moves slightly. A gif explains better than words here: https://trancart.eu/lutim/l7qWMFQF/7Q9YJRUn.gif I reproduce this at least on twitter and gitlab.com, but I remember having it on other websites. My OS: kubuntu 20.04 Reproduced on both firefox dev edition and firefox from apt package. Sorry in advance if it is not the correct place, I have no idea where to report that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 77.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: augustin 4577 F pulseaudio BuildID: 2020060727 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Sat Jun 13 16:14:37 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-10 (1310 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.254 dev enp0s31f6 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 docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.4 metric 100 MostRecentCrashID: bp-9faa8c77-de9e-4f98-9e75-033440200610 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=68.0/20190627143605 (Out of date) Profile1 - LastVersion=78.0/20200609215727 (Out of date) Profile0 (Default) - LastVersion=77.0.1/2020060727 (In use) Profile2 - LastVersion=60.5.2/20190221164337 (Out of date) Profile4 - LastVersion=72.0.1/20200107212822 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-05-09 (34 days ago) dmi.bios.date: 05/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET51W (1.25 ) dmi.board.ass
[Desktop-packages] [Bug 1226939] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': double free or corruption (!prev): 0x0000000002972fd0 *** in _int_realloc() from __GI___libc_reall
No crashes after 17.10 so consider it Fix Released. ** Description changed: + https://errors.ubuntu.com/problem/89ba2dc3b6e75994c90c1c4258ccb47786b4a63a + gnome-shell self restarted when I clicked on "Activities" then told it to display all ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-shell 3.8.4-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.2-0ubuntu1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': double free or corruption (!prev): 0x02972fd0 *** Date: Wed Sep 18 00:58:34 2013 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: - b'org.gnome.desktop.interface' b'clock-format' b"'12h'" - b'org.gnome.desktop.interface' b'clock-show-date' b'true' - b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.desktop.interface' b'clock-format' b"'12h'" + b'org.gnome.desktop.interface' b'clock-show-date' b'true' + b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2013-08-05 (43 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANGUAGE=en_US:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: - __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fbf2c0036a0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 - malloc_printerr (ptr=0x2972fd0, str=0x7fbf2c003788 "double free or corruption (!prev)", action=3) at malloc.c:4902 - _int_free (av=av@entry=0x7fbf2c23c740 , p=p@entry=0x2972fc0, have_lock=have_lock@entry=1) at malloc.c:3758 - _int_realloc (av=av@entry=0x7fbf2c23c740 , oldp=oldp@entry=0x2972fc0, oldsize=1328, nb=nb@entry=1952) at malloc.c:4245 - __GI___libc_realloc (oldmem=0x2972fd0, bytes=1936) at malloc.c:2984 + __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fbf2c0036a0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 + malloc_printerr (ptr=0x2972fd0, str=0x7fbf2c003788 "double free or corruption (!prev)", action=3) at malloc.c:4902 + _int_free (av=av@entry=0x7fbf2c23c740 , p=p@entry=0x2972fc0, have_lock=have_lock@entry=1) at malloc.c:3758 + _int_realloc (av=av@entry=0x7fbf2c23c740 , oldp=oldp@entry=0x2972fc0, oldsize=1328, nb=nb@entry=1952) at malloc.c:4245 + __GI___libc_realloc (oldmem=0x2972fd0, bytes=1936) at malloc.c:2984 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': double free or corruption (!prev): 0x02972fd0 *** UpgradeStatus: Upgraded to saucy on 2013-08-19 (30 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1226939 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': double free or corruption (!prev): 0x02972fd0 *** in _int_realloc() from __GI___libc_realloc() from ft_mem_qrealloc() from ft_mem_realloc() from af_axis_hints_new_segment() Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/89ba2dc3b6e75994c90c1c4258ccb47786b4a63a gnome-shell self restarted when I clicked on "Activities" then told it to display all ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-shell 3.8.4-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.2-0ubuntu1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': double free or corruption (!prev): 0x02972fd0 *** Date: Wed Sep 18 00:58:34 2013 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.desktop.interface' b'clock-format' b"'12h'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2013-08-05 (43 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_D
[Desktop-packages] [Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***
Gnome Shell on 16.04 is not supported by Ubuntu. Please upgrade to 20.04, or at least 18.04 and continue to report any problems you find. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix -- 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/1705146 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x05405f00 *** Status in gnome-shell package in Ubuntu: Won't Fix Bug description: lschris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 lschris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 Happened during this update today: Start-Date: 2017-07-18 17:22:01 Commandline: aptdaemon role='role-commit-packages' sender=':1.151' Upgrade: python-problem-report:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), python-apport:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), python3-apport:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-retrace:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-gtk:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), python3-problem-report:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10) End-Date: 2017-07-18 17:27:27 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x05405f00 *** CurrentDesktop: GNOME Date: Tue Jul 18 17:32:37 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-10-24 (998 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: __libc_message (do_abort=2, fmt=fmt@entry=0x7f7ca6ab3e98 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=0x7f7ca6ce7b20 , ptr=0x5405f00, str=0x7f7ca6ab0c35 "corrupted size vs. prev_size", action=3) at malloc.c:5006 _int_free (av=0x7f7ca6ce7b20 , p=, have_lock=0) at malloc.c:4014 __GI___libc_free (mem=) at malloc.c:2968 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x05405f00 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705146/+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 1457689] Re: relative path resolution is incorrect in imported CSS files used in Gnome Shell themes
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1457689 Title: relative path resolution is incorrect in imported CSS files used in Gnome Shell themes Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The CSS engine being used by Gnome Shell v3.14.4 for dealing with themes seems to have broken behavior when: * CSS file X is imported by another CSS file Y * CSS file X uses relative paths via "url(...)" to refer to resources (such as images or svg files) In this situation, syslog records continuous "Error opening file: No such file or directory" messages related to incorrect paths for the resources refered to by relative url. The CSS engine seems to be trying to resolve these relative paths with respect to the user's home directory, instead of relative to the path of the included CSS file where the the "url(...)" declaration exists (per sec 6.4 of the w3c REC-CSS1 specification: http://www.w3.org/TR/REC-CSS1/#url ). NOTE: as far as I can tell, the theme still *looks* correct, suggesting that perhaps the CSS engine is in fact finding these resources in the correct paths, *after* logging these errors? This bug did not exist in the previous version I upgraded from: Gnome Shell v3.4.1 I discovered this bug because I use a "custom" theme which includes the gnome-shell.css file from default theme and then overrides a few select properties -- as mentioned, this worked fine with Gnome Shell v3.4.1. Steps to reproduce: 1) Install Ubuntu-Gnome 15.04 containing Gnome Shell 3.14.4 $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ uname -a Linux tray 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ gnome-shell --version GNOME Shell 3.14.4 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.14.4-0ubuntu1 Candidate: 3.14.4-0ubuntu1 Version table: *** 3.14.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status 2) create a new user named "gnomeshellbug" and login as that user 3) create the following .themes directory for the gnomeshellbug user... $ find /home/gnomeshellbug/.themes/ /home/gnomeshellbug/.themes/ /home/gnomeshellbug/.themes/BuggyCssImportShellTheme /home/gnomeshellbug/.themes/BuggyCssImportShellTheme/gnome-shell /home/gnomeshellbug/.themes/BuggyCssImportShellTheme/gnome-shell/gnome-shell.css $ cat /home/gnomeshellbug/.themes/BuggyCssImportShellTheme/gnome-shell/gnome-shell.css @import url("/usr/share/gnome-shell/theme/gnome-shell.css"); .panel-button { /* not so much damn padding */ -natural-hpadding: 6px; -minimum-hpadding: 4px; } 4) Note that the imported file /usr/share/gnome-shell/theme/gnome- shell.css mentioned above contains url refrences to files which exist in the same /usr/share/gnome-shell/theme/ directory... $ grep message-tray-background.png /usr/share/gnome-shell/theme/gnome-shell.css background: #2e3436 url(message-tray-background.png); $ ls -l /usr/share/gnome-shell/theme/message-tray-background.png -rw-r--r-- 1 root root 19246 Mar 23 16:13 /usr/share/gnome-shell/theme/message-tray-background.png 5) Use the tweak-tool to enable the "User Themes" extension 6) Use the tweak-tool to select BuggyCssImportShellTheme as the Shell theme 7) observe log messages like these in syslog May 21 15:08:06 tray gnome-session[16490]: Gjs-Message: JS LOG: loading user theme: /home/gnomeshellbug/.themes/BuggyCssImportShellTheme/gnome-shell/gnome-shell.css May 21 15:08:06 tray gnome-session[16490]: (gnome-shell:16670): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. May 21 15:08:06 tray gnome-session[16490]: (gnome-shell:16670): St-WARNING **: Failed to load /home/gnomeshellbug/message-tray-background.png: Error opening file: No such file or directory May 21 15:08:14 tray gnome-session[16490]: message repeated 4 times: [ (gnome-shell:16670): St-WARNING **: Failed to load /home/gnomeshellbug/message-tray-background.png: Error opening file: No such file or directory] 8) As you interact with the UI -- clicking on the menu's for example -- note that many more similar error messages will start getting logged continuously... May 21 15:08:20 tray gnome-session[16490]: (gnome-shell:16670): St-WARNING **: Failed to load /home/gnomeshellbug/panel-button-border.svg: Error opening file: No such file or directory May 21 15:08:20 tray gnome-session[16490]: (gnome-shell:16670):
[Desktop-packages] [Bug 1374786] Re: gnome-shell crashed with SIGSEGV in notify_swap_buffers()
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-gnome Status: Incomplete => Invalid -- 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/1374786 Title: gnome-shell crashed with SIGSEGV in notify_swap_buffers() Status in GNOME Shell: New Status in Ubuntu GNOME: Invalid Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Start ubuntu and open apport. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: gnome-shell 3.12.2-1ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 27 12:39:14 2014 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2014-09-25 (2 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) ProcCmdline: gnome-shell --mode=gdm ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 LANGUAGE=es_CL:es SegvAnalysis: Segfault happened at: 0x7f70c2bd7f95:mov%rax,0x50(%r14) PC (0x7f70c2bd7f95) ok source "%rax" ok destination "0x50(%r14)" (0x0050) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1374786/+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 1297383] Re: Gnome-shell desktop is just a white blank screen after switching users
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-gnome Status: Incomplete => Invalid -- 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/1297383 Title: Gnome-shell desktop is just a white blank screen after switching users Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Invalid Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Whenever I use GDM as greeter and select "Switch user" from the menu, my desktop is left with only a white blank, no lock screen, nothing. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-shell 3.8.4-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Mar 25 17:29:32 2014 DisplayManager: gdm InstallationDate: Installed on 2013-04-30 (328 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-shell UpgradeStatus: Upgraded to saucy on 2013-10-21 (155 days ago) Way to reproduce, you have to use Nvidia proprietary drivers (version 319, 331) and GDM: 1) Log in as user1 2) Switch users at this point I usually already have a non-working desktop, but if not: 3) Log in as User2 4) Switch back to User1 It might take more than one user switching, but at least for me, eventually it will result in non-working desktops for both users. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1297383/+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 1652267] Re: Minimized windows show minimize button still being held down when in AO under Wayland
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-gnome Status: Incomplete => Invalid -- 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/1652267 Title: Minimized windows show minimize button still being held down when in AO under Wayland Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Invalid Status in gnome-shell package in Ubuntu: Won't Fix Bug description: After switch from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that when a window is minimized the minimized button will still appear held down when I view it in the AO: Minimize_Button_Still_Held_In_AO.png However it appears normally when the program is not minimized: Normal_Minimize_Button_In_AO.png ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 23 09:41:45 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (221 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1652267/+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 1743246] Re: problema audio
Please run this command to send us more information about your audio problems: apport-collect 1743246 ** Package changed: xorg (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1743246 Title: problema audio Status in pulseaudio package in Ubuntu: Incomplete Bug description: Buonasera, è da qualche giorno che non funziona l'Audio nel mio sistema, nell'icona in alto a destra del desktop che indica il volume c'è una x come se fosse disabilitata la scheda audio, nella scheda audio sulle impostazioni di sistema nel riquadro che indica Riproduci suono tramite, non si vede la scheda audio. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jan 14 20:28:52 2018 DistUpgraded: 2016-05-03 22:27:56,922 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G92 [GeForce 9800 GT] [10b0:0401] InstallationDate: Installed on 2016-01-19 (726 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic root=UUID=90cd0f82-be9c-4d2d-8632-288f1a48bc83 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-05-03 (620 days ago) dmi.bios.date: 03/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q TURBO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd03/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QTURBO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jan 14 20:18:05 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Basic Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1743246/+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 1743259] Re: 3D acceleration stops working after kernel upgrade
The attached files suggest 3D acceleration is working, fundamentally. Though this might be an issue specific to Compiz/Unity. ** Package changed: xorg (Ubuntu) => compiz (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1743259 Title: 3D acceleration stops working after kernel upgrade Status in compiz package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Thinkpad X200. I installed Ubunntu 16.04.3. It works fine immediately after installation (kernel 4.10.0-28). But when I install updates (kernel 4.13, post Meltdown/Spectre), it starts to behave weirdly: WHAT HAPPENS: All Unity eye-candies stop to work and cause a session refresh. I mean, when I press Alt (HUD), or Super (Dash), or even when I hover my mouse over an icon on the launcher the system goes through a mini-crash: all elements on the screen disappear for ~2 seconds, and they come back again. I never see HUD, Dash, or the laucher tooltip that I intended to see. POSSIBLE PROBLEM: Is it safe to say 3D accleration has stopped working after kernel update? SYSTEM SPECS: Intel Core 2 CPU P8600 @ 2.40GHz x 2, Mobile Intel GM45 Express Chipset, 64-bit (and by the way, it is running Libreboot as BIOS) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jan 14 22:16:30 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2018-01-13 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 74595FG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2016 dmi.bios.vendor: coreboot dmi.bios.version: CBET4000 3774c98 dmi.board.name: 74595FG dmi.board.vendor: LENOVO dmi.board.version: ThinkPad X200 dmi.chassis.type: 9 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvncoreboot:bvrCBET40003774c98:bd09/07/2016:svnLENOVO:pn74595FG:pvrThinkPadX200:rvnLENOVO:rn74595FG:rvrThinkPadX200:cvnLENOVO:ct9:cvr: dmi.product.name: 74595FG dmi.product.version: ThinkPad X200 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Jan 13 16:11:04 2018 xserver.configfile: default xserver.errors: Serial Wacom Tablet WACf004 stylus: wcmWriteWait error : Input/output error Serial Wacom Tablet WACf004 stylus: wcmWriteWait error : Input/output error PreInit returned 8 for "Serial Wacom Tablet WACf004 stylus" xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1743259/+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 1747881] Re: mouse scroll not working
** Package changed: xorg (Ubuntu) => xserver-xorg-input-libinput (Ubuntu) ** Package changed: xserver-xorg-input-libinput (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - mouse scroll not working + [evdev] mouse scroll not working (Kinzu V3 Optical mouse) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1747881 Title: [evdev] mouse scroll not working (Kinzu V3 Optical mouse) Status in xorg-server package in Ubuntu: Confirmed Bug description: I'm using Kinzu V3 Optical mouse on my ubuntu 16.04.3 LTS (Xenial Xerus). Mouse scroll is not working. The mouse scroll works with my Windows 10 computer but not on my ubuntu laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Feb 7 18:01:16 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated Graphics [1462:115a] Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 950M] [1462:115a] InstallationDate: Installed on 2017-08-07 (183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Micro-Star International Co., Ltd. GP62 6QE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=7925d32a-375f-4667-94c5-dc44c01247aa ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J5IMS.109 dmi.board.asset.tag: Default string dmi.board.name: MS-16J5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.A dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.109:bd10/27/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.name: GP62 6QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 7 09:33:45 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1747881/+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 1743520] Re: CompizPlugins
** Package changed: xorg (Ubuntu) => compiz (Ubuntu) ** Project changed: xorg-server => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1743520 Title: CompizPlugins Status in compiz package in Ubuntu: New Bug description: No value set for /apps/compiz-1/general/screen0/options/active_plugins ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jan 16 13:22:47 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-109-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0429] InstallationDate: Installed on 2018-01-10 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5410 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=b42e5347-f89d-4d00-bb62-8e8974d2ecf0 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 05C67D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jan 14 05:55:58 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1743520/+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 1750269] Re: Graphics driver problem
** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1750269 Title: Graphics driver problem Status in Ubuntu: Incomplete Bug description: massage on the screen dev/sda1/cleanfile..block how to solve it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Feb 18 23:52:18 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3809] InstallationDate: Installed on 2018-02-17 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:06b3 Acer, Inc Bus 001 Device 003: ID 0cf3:e360 Atheros Communications, Inc. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO INVALID ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-35-generic.efi.signed root=UUID=7c4bdac5-dec9-420c-95af-efd1cee14ede ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 1GCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr1GCN23WW:bd09/05/2017:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNODPK:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Feb 18 23:45:46 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1750269/+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 1743557] Re: ye
Can you explain in different words what kind of problem you are experiencing? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1743557 Title: ye Status in Ubuntu: Incomplete Bug description: how to make me full user in ubuntu,i have many problem when me installing application nvidia,intel graphic driver and more application. Im new user in ubuntu before im user windows 7 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jan 16 19:37:35 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0719] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 630M] [1025:0719] InstallationDate: Installed on 2018-01-16 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Aspire E1-471G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=ea244222-eec1-49d3-8a4c-0e2e05af4f7d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA40_HC dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.07:bd10/11/2012:svnAcer:pnAspireE1-471G:pvrV2.07:rvnAcer:rnEA40_HC:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-471G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jan 16 18:36:56 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1743557/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 80866566
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1868520 Title: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) Status in Mesa: Fix Released Status in MPV: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Focal: Fix Committed Bug description: [Impact] Wayland apps fail to start in focal with: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 [Test Case] Just run: es2gears_wayland [Regression Potential] Medium/unknown. The fix is quite new. [Other Info] When attempting to run es2gears_wayland against GNOME Shell, it fails with: EGL_VERSION = 1.5 vertex shader info: fragment shader info: info: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 The full wayland protocol trace is: [3104432.914] -> wl_display@1.get_registry(new id wl_registry@2) [3104432.972] -> wl_disp...@1.sync(new id wl_callback@3) [3104433.139] wl_display@1.delete_id(3) [3104433.175] wl_registry@2.global(1, "wl_drm", 2) [3104433.207] wl_registry@2.global(2, "wl_compositor", 4) [3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id [unknown]@4) [3104433.285] wl_registry@2.global(3, "wl_shm", 1) [3104433.316] wl_registry@2.global(4, "wl_output", 2) [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3) [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3) [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 1) [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1) [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2) [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1) [3104433.513] wl_registry@2.global(11, "wl_shell", 1) [3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5) [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3) [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1) [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1) [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1) [3104433.699] wl_registry@2.global(16, "wl_seat", 5) [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1) [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1) [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1) [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1) [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3) [3104433.875] wl_registry@2.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1) [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1) [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1) [3104433.991] wl_callb...@3.done(3421) [3104436.266] -> wl_display@1.get_registry(new id wl_registry@3) [3104436.279] -> wl_disp...@1.sync(new id wl_callback@6) [3104436.647] wl_display@1.delete_id(6) [3104436.672] wl_registry@3.global(1, "wl_drm", 2) [3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7) [3104436.744] wl_registry@3.global(2, "wl_compositor", 4) [3104436.780] wl_registry@3.global(3, "wl_shm", 1) [3104436.790] wl_registry@3.global(4, "wl_output", 2) [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3) [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3) [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 1) [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1) [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2) [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1) [3104436.925] wl_registry@3.global(11, "wl_shell", 1) [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3) [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1) [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1) [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1) [3104436.990] wl_registry@3.global(16, "wl_seat", 5) [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1) [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1) [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1) [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1) [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3) [3104437.066] -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id [unknown]@8) [3104437.083] wl_registry@3.global(22,
[Desktop-packages] [Bug 1876891] Re: The fractional scaling toggle applies instantly and not when "Apply" is pressed
** Changed in: gnome-control-center (Ubuntu) Assignee: Robert Ancell (robert-ancell) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-control-center (Ubuntu Focal) Assignee: Robert Ancell (robert-ancell) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-control-center (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1876891 Title: The fractional scaling toggle applies instantly and not when "Apply" is pressed Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: Do this when in an Xorg/Ubuntu session: 0. Have fractional scaling disabled and set to 100% 1. Go to gnome-control-center -> displays 2. Turn on the fractional scaling toggle 3. Select 125% 4. Press apply (the scaling should apply correctly) 5. Turn off the toggle 6. Turn the toggle back on At 5 and 6, the scaling changes. It shouldn't - this should only happen when you press 'Apply'. The toggle needs to not be directly connected to GSettings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 10:35:48 2020 InstallationDate: Installed on 2012-10-07 (2766 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876891/+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 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling
** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1876894 Title: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling Status in gnome-control-center package in Ubuntu: In Progress Status in mutter package in Ubuntu: Confirmed Bug description: Do this in an Ubuntu/Xorg session: 0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 100% 1. Open gnome-control-center → displays 2. Turn on fractional scaling 3. Select 125% 4. Press apply (the scaling should correctly change now) 5. Turn off fractional scaling by changing the toggle Now everything is shrunk - it's not been returned to 100% properly. See the attached screenshot where the text is tiny instead of regular 100% size. If you do this instead of step 5: 5. Select 100% scaling 7. Press apply 8. Turn off fractional scaling by changing the toggle Then everything returns to the normal size. I'm on nvidia(-440), but Séb said that he saw this on his Intel machine too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 10:57:40 2020 InstallationDate: Installed on 2012-10-07 (2766 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876894/+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 1873541] Re: black screen with cursor on dual nouveau + i915
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873541 Title: black screen with cursor on dual nouveau + i915 Status in mutter package in Ubuntu: Expired Bug description: This bug should be able to be reproduced on any computer with both an nvidia (stock nouveau) and intel igpu (stock i915), booting to stock gdm3 (wayland by default). My main example is a MacBookPro6,2 with the infamous GT 330m on 20.04 with -proposed enabled and booting with the following grub manipulations to set gmux to the integrated LVDS: outb 0x710 2 - switch LVDS to intel outb 0x728 1 - switch internal DDC to intel outb 0x740 2 - switch displayport out to intel I am not using outb 0x750 0, so that the 330m remains powered on. It still works just fine-- the only thing broken is the LVDS connection to the internal panel. I disable it with video=LVDS-2:d. --> NOTE: This mod is only for the convenience of not having to deal with a phantom second screen once booted (both GPU's have the LVDS and edid of the internal screen hooked up). The computer boots fine and the bug reproduces exactly the same with or without it. I tested with all these modifications disabled, and this still occurred - it's not specific to my configuration. A user booting stock Ubuntu on this laptop, or as I discovered later, any nouveau + i915 hardware combination will run into this as well. Anyways, I'm keeping the 330m enabled to use DRI_PRIME to run applications on the 330m for good reason- it supports OpenGL 3.3 while HD Graphics (arrandale aka Ironlake) is the only HD Graphics iGPU stuck on OpenGL 2.1, thus otherwise vastly restricting the modern graphics workloads of the system. When explicitly booting with gdm3 WaylandEnable=false (login and desktop both xorg), everything works as expected - single screen driven by the i915's KMS, nouveau with DRI_PRIME working, returning NVA5 stats and functional with OpenGL 3 apps as well. On GDM3 wayland, however (the default-- which is why I think this bug is rather important), gdm3 starts to a black screen with cursor. The login screen and shell still seem to be running-- I can type my password blindly and press enter and the cursor freezes briefly as it does during a non-broken login. After a few seconds, I can press the volume up/down keys and I hear the volume sound. Pressing the app grid shortcut makes the cursor lag, just as it does when I disable the nvidia at the pcie link level and rendering works on i915. Backlight control also works on the login screen and once logged in. It's as if everything except the actual rendering to the screen is working. The minute I pass nouveau.modeset=0 in cmdline, or cut the power to the 330m at the hardware level with outb 0x750, Wayland starts working again. The issue has something to do with GDM3's handling of a KMS- enabled nouveau GPU, whether it is headless or not (no difference with video=LVDS-2:d or not). To confirm my suspicions that it is not specific to the macbook pro line, this exact same issue (Xorg works wayland doesn't) also occurred on a desktop dual-gpu setup, with a GTX 760 (kepler) on nouveau tandem with a Haswell HD Graphics G3258-- with any combination of displays, all on the Intel, mixed on nvidia and intel, or all on nvidia, as long as both cards were present and modesetting, a black screen with cursor but blindly working gnome followed. This bug has existed since at least 19.04, if not earlier-- I replaced the nvidia gpu in that system with a Radeon 7870 when it ran that release due to this bug, as a matter of fact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873541/+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 1175882] Re: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images)
** Changed in: df-libreoffice Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Triaged Bug description: Follow these steps to bring LibreOffice writer to a crawl: 1) Allow this page to fully load in firefox (in a new tab): http://www.amorosity.com/SlingBlade/ 2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire page's contents into memory). 3) Open LibreOffice writer, and paste your clipboard into it. I don't mind waiting for all the images to get loaded. The main point here, is that performance is not only slow during the initial paste. After the images get fully loaded into the word processing document, interacting with the document becomes impractical. Everything you try to do makes the application hang for several seconds. I have 4 gigabytes of RAM available for LibreOffice writer to use as it wishes, but it must be using some type of swap file (instead) while I'm modifying this large document. However, I have a really fast solid-state hard drive, so you'd think that even that would be fast on my machine. My machine should have the specs to enable me the ability to handle converting this large web page into a word processing document. Yes there are other ways to achieve what I'm trying to do, but this bug is about how LibreOffice can't handle the job. If it was programmed just right, it would make use of the resources my computer would gladly provide it, and scale up to this rather intensive task. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 23:09:24 2013 InstallationDate: Installed on 2013-04-02 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+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 827695]
Hello, This comment is going to be post on the bugs: bug 32362 bug 133081 bug 92373 bug 127483 All those bugs seem to be related. In my humble opinion as begginer programmer they seem to be related with a disfunction with OpenGL in windows. Tested on linux (LO 6.4), no problem. Tested with beta 7 on windows, no problem (does not use OpenGL any more). So the bug happened to correct by itself. So I suggest marking as duplicated bug 32362 bug 133081 bug 127483 and close them all. -- 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/827695 Title: [Upstream] bug in displaying scalable square brackets in math object Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) When is expected to happen in LibreOffice Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_example.odt && lowriter --nologo bracket_example.odt is the scalable square brackets look as they would in Word. Latex also shows the desired bracket shape as per https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2287347/+files/latex_brackets.pdf . 4) What happens instead is the top and bottom part of the bracket look like a square instead of a line pointing inwards towards the equation. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/827695/+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 1175882]
(In reply to launchpad from comment #9) > I created a png version of the page again, so that I could test this in > Kubuntu 20.04. I don't want to post a hyperlink of that page here, because I > don't want google to index it. To get to the png version of the page, add > "png/" onto the end of this URL: > http://www.amorosity.com/SlingBlade/ It does not lock up for me with KDE Plasma either. Finishes OK. I think we should close. -- 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/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Triaged Bug description: Follow these steps to bring LibreOffice writer to a crawl: 1) Allow this page to fully load in firefox (in a new tab): http://www.amorosity.com/SlingBlade/ 2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire page's contents into memory). 3) Open LibreOffice writer, and paste your clipboard into it. I don't mind waiting for all the images to get loaded. The main point here, is that performance is not only slow during the initial paste. After the images get fully loaded into the word processing document, interacting with the document becomes impractical. Everything you try to do makes the application hang for several seconds. I have 4 gigabytes of RAM available for LibreOffice writer to use as it wishes, but it must be using some type of swap file (instead) while I'm modifying this large document. However, I have a really fast solid-state hard drive, so you'd think that even that would be fast on my machine. My machine should have the specs to enable me the ability to handle converting this large web page into a word processing document. Yes there are other ways to achieve what I'm trying to do, but this bug is about how LibreOffice can't handle the job. If it was programmed just right, it would make use of the resources my computer would gladly provide it, and scale up to this rather intensive task. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 23:09:24 2013 InstallationDate: Installed on 2013-04-02 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+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 827695]
(In reply to RGB from comment #50) > @dante19031999 this is NOT an OpenGL or OS related problem. Indeed, this > problem predates the whole introduction of OpenGL support into the suite. > > Insert a Math object into Writer and type this code > > left[ stack{1#2#3#4#5#6#7#8} right] > > you'll immediately see how wrong square brackets are, independently of > OpenGL, OS or anything: just print or export to PDF to see that's NOT a > display problem, but something deeper. Sorry. My bad. -- 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/827695 Title: [Upstream] bug in displaying scalable square brackets in math object Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) When is expected to happen in LibreOffice Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_example.odt && lowriter --nologo bracket_example.odt is the scalable square brackets look as they would in Word. Latex also shows the desired bracket shape as per https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2287347/+files/latex_brackets.pdf . 4) What happens instead is the top and bottom part of the bracket look like a square instead of a line pointing inwards towards the equation. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/827695/+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 1175882]
A lot has changed since I originally submitted this bug report. That page no longer contains PNG images, and it seems that LibreOffice Writer doesn't support the new webp standard images that the page contains. Read about webp here: https://en.wikipedia.org/wiki/WebP Additionally, I'm now using Kubuntu 20.04, which is less likely to lock up when a single applications has a problem. I created a png version of the page again, so that I could test this in Kubuntu 20.04. I don't want to post a hyperlink of that page here, because I don't want google to index it. To get to the png version of the page, add "png/" onto the end of this URL: http://www.amorosity.com/SlingBlade/ >From there, you can test this yourself by following steps 2 and 3 given at the top of this report. In Kubuntu 20.04, LibreOffice Writer does a poor job at scaling the png images (that the page contains), but it doesn't crash in Kubuntu 20.04. I can no longer speak for GNOME 3, but you can easily test it yourself from the png version of the page that I made exclusively for this bug report. -- 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/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Triaged Bug description: Follow these steps to bring LibreOffice writer to a crawl: 1) Allow this page to fully load in firefox (in a new tab): http://www.amorosity.com/SlingBlade/ 2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire page's contents into memory). 3) Open LibreOffice writer, and paste your clipboard into it. I don't mind waiting for all the images to get loaded. The main point here, is that performance is not only slow during the initial paste. After the images get fully loaded into the word processing document, interacting with the document becomes impractical. Everything you try to do makes the application hang for several seconds. I have 4 gigabytes of RAM available for LibreOffice writer to use as it wishes, but it must be using some type of swap file (instead) while I'm modifying this large document. However, I have a really fast solid-state hard drive, so you'd think that even that would be fast on my machine. My machine should have the specs to enable me the ability to handle converting this large web page into a word processing document. Yes there are other ways to achieve what I'm trying to do, but this bug is about how LibreOffice can't handle the job. If it was programmed just right, it would make use of the resources my computer would gladly provide it, and scale up to this rather intensive task. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 23:09:24 2013 InstallationDate: Installed on 2013-04-02 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+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 827695]
@dante19031999 this is NOT an OpenGL or OS related problem. Indeed, this problem predates the whole introduction of OpenGL support into the suite. Insert a Math object into Writer and type this code left[ stack{1#2#3#4#5#6#7#8} right] you'll immediately see how wrong square brackets are, independently of OpenGL, OS or anything: just print or export to PDF to see that's NOT a display problem, but something deeper. -- 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/827695 Title: [Upstream] bug in displaying scalable square brackets in math object Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) When is expected to happen in LibreOffice Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_example.odt && lowriter --nologo bracket_example.odt is the scalable square brackets look as they would in Word. Latex also shows the desired bracket shape as per https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2287347/+files/latex_brackets.pdf . 4) What happens instead is the top and bottom part of the bracket look like a square instead of a line pointing inwards towards the equation. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/827695/+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 827695]
Created attachment 162107 Announced attachment (In reply to dante19031999 from comment #48) > ... > In my humble opinion as begginer programmer they seem to be related with a > disfunction with OpenGL in windows. > ... Either misunderstood completely or cannot confirm: With LibO 7.0.0.0.beta1 under Win 10 I got exactly the behavior previously described independent of whether 'skia' was enabled or not. See new attachment. -- 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/827695 Title: [Upstream] bug in displaying scalable square brackets in math object Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) When is expected to happen in LibreOffice Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_example.odt && lowriter --nologo bracket_example.odt is the scalable square brackets look as they would in Word. Latex also shows the desired bracket shape as per https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2287347/+files/latex_brackets.pdf . 4) What happens instead is the top and bottom part of the bracket look like a square instead of a line pointing inwards towards the equation. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/827695/+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 1175882]
Thank you for reporting the bug. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. -- 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/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Triaged Bug description: Follow these steps to bring LibreOffice writer to a crawl: 1) Allow this page to fully load in firefox (in a new tab): http://www.amorosity.com/SlingBlade/ 2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire page's contents into memory). 3) Open LibreOffice writer, and paste your clipboard into it. I don't mind waiting for all the images to get loaded. The main point here, is that performance is not only slow during the initial paste. After the images get fully loaded into the word processing document, interacting with the document becomes impractical. Everything you try to do makes the application hang for several seconds. I have 4 gigabytes of RAM available for LibreOffice writer to use as it wishes, but it must be using some type of swap file (instead) while I'm modifying this large document. However, I have a really fast solid-state hard drive, so you'd think that even that would be fast on my machine. My machine should have the specs to enable me the ability to handle converting this large web page into a word processing document. Yes there are other ways to achieve what I'm trying to do, but this bug is about how LibreOffice can't handle the job. If it was programmed just right, it would make use of the resources my computer would gladly provide it, and scale up to this rather intensive task. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 23:09:24 2013 InstallationDate: Installed on 2013-04-02 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+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 1777285] Re: [upstream] Batch libreoffice --convert-to offers no way to wait for document completion
** Changed in: df-libreoffice Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1777285 Title: [upstream] Batch libreoffice --convert-to offers no way to wait for document completion Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Triaged Bug description: Command-line: libreoffice --convert-to odt:writer8 myfile.txt The returned status code ($?) is zero. So far, so good. But, when I try to access the ODT file (E.g. copy it), it doesn't yet exist. Adding `sync; sync; sync` right after the libreoffice batch execution did not help. Adding --headless as an option did not help. If I sleep for a few seconds immediately after the libreoffice batch execution, then the file finally gets completed before a subsequent command references the ODT file. Sample script: ### Create somehow a file called myfile.txt rm myfile.odt somewhere-else.odt libreoffice --headless --convert-to odt:writer8 myfile.txt RC=$? if [ $RC -ne 0 ]; then echo '*** libreoffice conversion failed for myfile.txt' exit 86 fi #sleep 3 ls *.odt Result: ls: cannot access '*.odt': No such file or directory If one changes the above script so that the sleep is executed, then the ODT file is available. Observation: It appears that executing libreoffice in batch mode is somehow kicking off a separate process to finish the ODT file. The exit to the shell and the availability of the ODT file should be synchronized. Before 18.04, I never saw this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jun 16 17:07:02 2018 InstallationDate: Installed on 2017-10-13 (246 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+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 1738774]
In general I think people with high DPI screens would prefer to use SVG icons and live with or report a small number of bugs with a small number of mid-rendered icons then live with 100% of all icons being pixelated and ugly. Perhaps making the SVG renderer default only for high DPi users of SVG-compatible icon themes would make everyone happy: high DPI users get nicer icons overall, while devs get more user eyeballs (and bug reports, and potential contributors) using the SVG renderer. FWIW all the icons look flawless to me with the Breeze SVG icon theme and a global 250% scale scale factor -- 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/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+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 1738774]
(In reply to Jan-Marek Glogowski from comment #34) > This is the typical chicken-egg problem: LO's SVG rasterizer / icons broken > => default to PNG. Everybody uses PNG (and some complain about blocky icons > in HiDPI) => nobody fixes the LO's SVG rasterizer / icons. Some more > background info is in bug 133877 comment 11. I totally agree on that, the main problem is the SVG Rasterizer (I guess that's the same as a SVG Renderer?). But there are plenty of free OpenSource SVG Renderers out there: Inkscape, Chromium, Firefox aso... all support SVG Rendering. Isn't it possible to use the code of those, if the LibO renderer is so hard to fix? I know its easy to talk like that when you are not a developer, so just my two cents on that ;) -- 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/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+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 1777285]
(In reply to Buovjaga from comment #17) > (In reply to Richard Elkins from comment #0) > > Steps to Reproduce: > > Linux batch script, starting with an existing text file called "myfile.txt": > > > > libreoffice --headless --convert-to odt:writer8 myfile.txt > > RC=$? > > if [ $RC -ne 0 ]; then > > echo '*** libreoffice conversion failed for myfile.txt' > > exit 86 > > fi > > cp myfile.odt somewhere-else.odt > > > > Actual Results: > > cp: cannot stat 'myfile.odt': No such file or directory > > > > Expected Results: > > Copy completes as normal because myfile.odt is available. > > I get the expected result. I guess you should bite the bullet, clone the > source and try modifying it. > > https://wiki.documentfoundation.org/Development/BuildingOnLinux > https://wiki.documentfoundation.org/Development/Linux_Build_Dependencies > > Arch Linux 64-bit > Version: 7.0.0.0.alpha1+ > Build ID: c73418d8d1258ea0a8c77c07672fd182e2b28b26 > CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; > Locale: fi-FI (fi_FI.UTF-8); UI: en-US > Calc: threaded > Built on 9 May 2020 @Richard Elkins, have you had time to try it ? -- 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/1777285 Title: [upstream] Batch libreoffice --convert-to offers no way to wait for document completion Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Triaged Bug description: Command-line: libreoffice --convert-to odt:writer8 myfile.txt The returned status code ($?) is zero. So far, so good. But, when I try to access the ODT file (E.g. copy it), it doesn't yet exist. Adding `sync; sync; sync` right after the libreoffice batch execution did not help. Adding --headless as an option did not help. If I sleep for a few seconds immediately after the libreoffice batch execution, then the file finally gets completed before a subsequent command references the ODT file. Sample script: ### Create somehow a file called myfile.txt rm myfile.odt somewhere-else.odt libreoffice --headless --convert-to odt:writer8 myfile.txt RC=$? if [ $RC -ne 0 ]; then echo '*** libreoffice conversion failed for myfile.txt' exit 86 fi #sleep 3 ls *.odt Result: ls: cannot access '*.odt': No such file or directory If one changes the above script so that the sleep is executed, then the ODT file is available. Observation: It appears that executing libreoffice in batch mode is somehow kicking off a separate process to finish the ODT file. The exit to the shell and the availability of the ODT file should be synchronized. Before 18.04, I never saw this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jun 16 17:07:02 2018 InstallationDate: Installed on 2017-10-13 (246 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+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 1883920] Re: ubuntu logo in wslfetch needs update
Hi Sebastien, Thanks for the heads up. Included the screenshot in description now. ** Description changed: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the - outdated version. + outdated version: + https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png [Test Case] - * Install Ubuntu WSL and install this fix. - * run wslfetch command. - * new logo should be shown. + * Install Ubuntu WSL and install this fix. + * run wslfetch command. + * new logo should be shown like the following: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png [Regression Potential] * None for now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown like the following: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
It seems like I get this crash only when I am typing in VS Code. I found this post in Stack Overflow which suggest disabling GPU acceleration in VS Code. I've made this configuration change to VS Code and so far no more crashes. https://stackoverflow.com/questions/29966747/how-can-i-disable-gpu- rendering-in-visual-studio-code/58762168#58762168 -- 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/1543192 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main() Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530 https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851 --- No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Mon Feb 8 17:07:23 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2015-04-30 (283 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 panic=-1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, init=, fini=, rtld_fini=, stack_end=0x7fffc9e34fc8) at libc-start.c:289 SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Mon Feb 8 17:08:14 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 9847 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
I will eventually figure out a hardware configuration to work on this. Though last time I did I kept hitting bug 1874567 instead, so that might come first... Once I am able to reproduce this bug my next priority will be to figure out if it is another one caused by x11-Add-support-for-fractional- scaling-using-Randr.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+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 1884008] [NEW] network manager prefers further away AP when there are multiple APs
Public bug reported: I'm on Ubuntu 20.04. My Wifi set-up has multiple access points throughout my home, and they all have the same SSID. It doesn't matter where I am in my home though, network manager always connects to one particular AP. If I list all the access points with `nmcli dev wifi list` I can see that it even picks that one access point if it is the farthest away one: 76:83:C2:BB:34:2A -- Infra 36405 Mbit/s 97 ▂▄▆█ WPA2 74:83:C2:BB:34:2A my_access_point Infra 36405 Mbit/s 95 ▂▄▆█ WPA2 74:83:C2:BA:34:2A my_access_point Infra 1 195 Mbit/s 94 ▂▄▆█ WPA2 76:83:C2:BA:34:2A -- Infra 1 195 Mbit/s 94 ▂▄▆█ WPA2 B6:FB:E4:45:CA:82 -- Infra 157 405 Mbit/s 44 ▂▄__ WPA2 * B4:FB:E4:45:CA:82 my_access_point Infra 157 405 Mbit/s 44 ▂▄__ WPA2 B6:FB:E4:44:CA:82 -- Infra 11195 Mbit/s 42 ▂▄__ WPA2 B4:FB:E4:44:CA:82 my_access_point Infra 11195 Mbit/s 40 ▂▄__ WPA2 It is true that if I change the BSSID field in the wifi settings I can get it to connect to a particular one, but that is not sufficient. I have a laptop, and if I move around my home I need it to connect to the closest one, and switching manually to whichever one is closest is not practical. I can't even create multiple entries for each BSSID in the list of networks, if I try many different networks appear with the same name and random numbers and I can't even label them. This is network manager version 1.22.10-1ubuntu2.1 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1884008 Title: network manager prefers further away AP when there are multiple APs Status in network-manager package in Ubuntu: New Bug description: I'm on Ubuntu 20.04. My Wifi set-up has multiple access points throughout my home, and they all have the same SSID. It doesn't matter where I am in my home though, network manager always connects to one particular AP. If I list all the access points with `nmcli dev wifi list` I can see that it even picks that one access point if it is the farthest away one: 76:83:C2:BB:34:2A -- Infra 36405 Mbit/s 97 ▂▄▆█ WPA2 74:83:C2:BB:34:2A my_access_point Infra 36405 Mbit/s 95 ▂▄▆█ WPA2 74:83:C2:BA:34:2A my_access_point Infra 1 195 Mbit/s 94 ▂▄▆█ WPA2 76:83:C2:BA:34:2A -- Infra 1 195 Mbit/s 94 ▂▄▆█ WPA2 B6:FB:E4:45:CA:82 -- Infra 157 405 Mbit/s 44 ▂▄__ WPA2 * B4:FB:E4:45:CA:82 my_access_point Infra 157 405 Mbit/s 44 ▂▄__ WPA2 B6:FB:E4:44:CA:82 -- Infra 11195 Mbit/s 42 ▂▄__ WPA2 B4:FB:E4:44:CA:82 my_access_point Infra 11195 Mbit/s 40 ▂▄__ WPA2 It is true that if I change the BSSID field in the wifi settings I can get it to connect to a particular one, but that is not sufficient. I have a laptop, and if I move around my home I need it to connect to the closest one, and switching manually to whichever one is closest is not practical. I can't even create multiple entries for each BSSID in the list of networks, if I try many different networks appear with the same name and random numbers and I can't even label them. This is network manager version 1.22.10-1ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884008/+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 1878775] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_
** Description changed: https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8 https://errors.ubuntu.com/problem/bd6ce0ebb5afe5054592e605660dff1d41db4f34 + https://errors.ubuntu.com/problem/317edd5b79c720818834b79ad9ede23cbb132ff4 --- 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.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8 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/. ** Summary changed: - gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_session() + Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_session() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1878775 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_session() Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8 https://errors.ubuntu.com/problem/bd6ce0ebb5afe5054592e605660dff1d41db4f34 https://errors.ubuntu.com/problem/317edd5b79c720818834b79ad9ede23cbb132ff4 --- 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.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878775/+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 1884006] Re: /usr/libexec/gsd-keyboard:11:g_str_hash:g_hash_table_lookup:g_autoptr_cleanup_generic_gfree:_systemd_session_is_graphical:_find_graphical_systemd_session
*** This bug is a duplicate of bug 1878775 *** https://bugs.launchpad.net/bugs/1878775 ** This bug has been marked a duplicate of bug 1878775 gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_session() -- 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/1884006 Title: /usr/libexec/gsd- keyboard:11:g_str_hash:g_hash_table_lookup:g_autoptr_cleanup_generic_gfree:_systemd_session_is_graphical:_find_graphical_systemd_session Status in gnome-settings-daemon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 3.36.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/317edd5b79c720818834b79ad9ede23cbb132ff4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1884006/+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 1880728] Re: [amdgpu] Gnome Shell freeze
Oh those are much better links, thanks. There you have: Bug 1877075: A fix for 20.04 is on the way (you will need libmutter version 3.36.3). Bug 1843982: A fix for 20.04 was released to updates yesterday. Bug 1878775: Not sure but maybe fixed with bug 1843982 yesterday? But that doesn't help us to choose a single issue for this bug to be about. I guess this bug doesn't need to stay open unless we can identify some new issue that doesn't already have a bug ID. Please continue reporting your crashes here so we can find some pattern. -- 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/1880728 Title: [amdgpu] Gnome Shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: was logged in through team viewer and got kicked out. when i was able to physically access the machine the screens were on, but was not able to move the mouse or interact with the computer. performed hard reboot to get it back on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 26 11:24:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 [174b:e347] InstallationDate: Installed on 2020-05-09 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LM dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE(MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+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 1884006] [NEW] /usr/libexec/gsd-keyboard:11:g_str_hash:g_hash_table_lookup:g_autoptr_cleanup_generic_gfree:_systemd_session_is_graphical:_find_graphical_systemd_session
*** This bug is a duplicate of bug 1878775 *** https://bugs.launchpad.net/bugs/1878775 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 3.36.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/317edd5b79c720818834b79ad9ede23cbb132ff4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal groovy -- 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/1884006 Title: /usr/libexec/gsd- keyboard:11:g_str_hash:g_hash_table_lookup:g_autoptr_cleanup_generic_gfree:_systemd_session_is_graphical:_find_graphical_systemd_session Status in gnome-settings-daemon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 3.36.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/317edd5b79c720818834b79ad9ede23cbb132ff4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1884006/+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 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
Just happened to me again on focal. Annoyingly, the act of taking a screenshot corrects the glitch before the screenshot is taken. Seems screenshotting forces a full screen redraw. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2912 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2912 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2912 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+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 1880728] Re: [amdgpu] Gnome Shell freeze
Here are a couple other links from errors.ubuntu.com today. There were three from temviewer as well, but i did not list those here. https://errors.ubuntu.com/oops/5f1c4638-b0a5-11ea-af49-fa163e983629 https://errors.ubuntu.com/oops/69a6aac2-b0a4-11ea-9cf2-fa163e102db1 https://errors.ubuntu.com/oops/3fa61456-b0a4-11ea-a652-fa163e6cac46 https://errors.ubuntu.com/oops/3a454040-b0a4-11ea-9cf2-fa163e102db1 I actually just uninstalled teamviewer to see if that resolves anything. I am going to be using a different program called anydesk for right now. On Wed, Jun 17, 2020 at 8:55 PM Daniel van Vugt <1880...@bugs.launchpad.net> wrote: > The crash in comment #9 is > > /opt/teamviewer/tv_bin/TeamViewer_Desktop > > While that doesn't appear to be a supported component of Ubuntu, if that > is the main crash you experience then it would account for this bug. But > still, we can't help with crashes of TeamViewer itself. So let's ignore > any crashes in TeamViewer binaries here. We're only interested in > crashes of 'gnome-shell' or 'Xorg'. Because those are provided by > Ubuntu. > > Please continue repeating the steps from comment #2 as we still need to > figure out the signature of a recurring problem in gnome-shell, if any. > > You also seem to have the extension 'dash-to-dock' loaded so please try > removing that. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1880728 > > Title: > [amdgpu] Gnome Shell freeze > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > was logged in through team viewer and got kicked out. when i was able > to physically access the machine the screens were on, but was not able > to move the mouse or interact with the computer. performed hard > reboot to get it back on. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 > Uname: Linux 5.4.0-31-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue May 26 11:24:02 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GpuHangFrequency: Several times a week > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Immediately after installing this version of Ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX > 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA > controller]) > Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 > [174b:e347] > InstallationDate: Installed on 2020-05-09 (16 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: Micro-Star International Co., Ltd. MS-7A34 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic > root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/08/2019 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: A.LM > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: B350 PC MATE(MS-7A34) > dmi.board.vendor: Micro-Star International Co., Ltd > dmi.board.version: 2.0 > dmi.chassis.asset.tag: To be filled by O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Micro-Star International Co., Ltd. > dmi.chassis.version: 2.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: MS-7A34 > dmi.product.sku: To be filled by O.E.M. > dmi.product.version: 2.0 > dmi.sys.vendor: Micro-Star International Co., Ltd. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+subscriptions > -- You
[Desktop-packages] [Bug 1883981] Re: dash-to-dock extension gets buggy after lock
Please run 'gnome-shell-extension-prefs' and ensure you only have one dock extension enabled. If you have multiple docks enabled then we should reword this bug to be about any remaining issue that occurs when only one dock is enabled. ** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1883981 Title: dash-to-dock extension gets buggy after lock Status in gnome-shell-extension-dashtodock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Works perfect on boot. After 1st lock both dash-to-dock and ubuntu-gnome-dock appear on Activities Overview. On 2nd lock, dash-to-dock appears on lockscreen. After 2nd lock, two docks appear (overlapped) on the homescreen (desktop). Dash to dock - version 68 Gnome 3.36.2 Ubuntu 20.04 LTS x64 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 23:27:58 2020 InstallationDate: Installed on 2020-06-15 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1883981/+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 1884001] Re: External 4k monitor periodically shows black screen
I believe it's a kernel problem. There are several of these reports: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=ice-lake-flicker ** Tags added: ice-lake-flicker ** Summary changed: - External 4k monitor periodically shows black screen + [Ice Lake] External 4k monitor periodically shows black screen ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884001 Title: [Ice Lake] External 4k monitor periodically shows black screen Status in linux package in Ubuntu: New Bug description: I have a 4k dell monitor attached to a Dell XPS13 (2020). The connection is: Computer -> Thunderbolt (USBC) Cable -> Caldigit Thunderbolt Hub -> Thunderbolt-to-Displayport Cable -> Monitor. Note: The Thunderbolt cable from the Caldigit hub is powered. I have a keyboard, mouse, monitor etc all attached to the thunderbolt hub. So there is just one cable connected to the laptop, which is nice. If I wake my laptop, everything's fine for a few minutes, then periodically the screen goes black for a second or two, then back to display. This happens with increasing frequency. If I log out and log back in, the problem is usually resolved. Sometimes I have to unplug and replug the hub from my laptop. I assume this is xorg-related because logging out and back in effectively restarts X. But X might not be the problem, it might be thunderbolt-related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 18:22:45 2020 DistUpgraded: 2020-04-28 11:49:08,077 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-03-14 (95 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=15b70d1f-6d44-4cea-a1ad-10b0924bc69b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (50 days ago) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884001/+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 1883831] Re: my laptop screen crashes when i take my laptop with one hand in some positios , the display have multiple rectangle with white gray and pixels , after restart it i
Please attach a photo of the problem, but also... 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. -- 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/1883831 Title: my laptop screen crashes when i take my laptop with one hand in some positios , the display have multiple rectangle with white gray and pixels , after restart it is normal ,this was happen for two times.Yesterday and today Status in gnome-shell package in Ubuntu: Incomplete Bug description: My screen laptop crashes when i take my laptop with one hand or some positions, this was happen for two times , yesterday and today . All display is with white and gray rectangle with pixels. Thanks. Gabriel. I have ubuntu 20.02 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 77.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriel1705 F pulseaudio BuildID: 2020060727 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 08:20:16 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-05-14 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.8.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-65afbb722696 proto kernel scope link src 172.18.0.1 linkdown 192.168.8.0/24 dev wlo1 proto kernel scope link src 192.168.8.111 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=76.0.1/20200507114007 (Out of date) Profile0 - LastVersion=77.0.1/2020060727 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2019 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C9 dmi.board.vendor: HP dmi.board.version: 56.31 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.09:bd12/20/2019:svnHP:pnHPLaptop15s-fq1xxx:pvr:rvnHP:rn86C9:rvr56.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-fq1xxx dmi.product.sku: 8PQ82EA#AKE dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883831/+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 1882781] Re: Gnome 3.36.2 leaking in 20.04
*** This bug is a duplicate of bug 1856838 *** https://bugs.launchpad.net/bugs/1856838 I am starting to suspect (from other bug reports too) that systems with the Nvidia driver in particular degrade over time. That might be a graphics resource leak which would be Mutter's fault. -- 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/1882781 Title: Gnome 3.36.2 leaking in 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've noticed lately that the performance of the UI in Gnome 3.36.2 seems to decay with uptime. The most obvious manifestation is that over time, window animations have a delay and feel "sticky". Applications themselves seem unaffected. When I tell gnome to switch workspaces, there's about a half second to full second delay before the animation happens. This also applies to things like pressing the meta key to show all my windows or pressing alt-tab. Each one appears to share the same delay. I'm running a fairly unremarkable desktop setup using vanilla gnome on Ubuntu 20.04. My research on this issue seems to indicate that there were memory leak issues in 18.xx versions of the OS, but that those were supposedly fixed. The only thing I can conclude at this point is that a new issue has emerged, there was a regression, or the original fix didn't work. The animation delay is sapping productivity to the point that I eventually have to reboot my system. The gnome-shell process definitely leaks over time as it starts around ~300mb and if left for a day will sit at ~600mb or more. --- Regarding my overall hardware and nominal state of my system, I'm experiencing this issue even as I'm creating this question. I'm running the stock/vanilla gnome desktop, not the ubuntu customized one. My system has 32gb of RAM, only 6gb of which are in use currently. My CPU usage fluctuates across 12 vcores up to 20% max. I have an RTX 2060 for my GPU. At least as best as I can tell, I see no issue with the amount of resources gnome-shell is getting right now. 😉 --- There also appear to be other accounts of this same issue building up since the release of 20.04. It's clear that this is a widespread issue: https://www.reddit.com/r/gnome/comments/fxffcd/gnome_shell_336_in_ubuntu_2004_still_leaks/ I would treat this with some urgency as for regular users this bug renders the OS completely unusable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Jun 9 08:19:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882781/+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 1883915] Re: notifications off for vlc app ignored and notifications pop up regardless
** Also affects: vlc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1883915 Title: notifications off for vlc app ignored and notifications pop up regardless Status in gnome-control-center package in Ubuntu: New Status in vlc package in Ubuntu: New Bug description: Install vlc (videolan) and run gnome-control-center as user. Disable all notifications for vlc app. Play vlc app in loop (repeat) mode and it will pop notifications 'now playing' etc. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 Uname: Linux 5.6.0-050600-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 16:22:09 2020 InstallationDate: Installed on 2020-05-19 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1883915/+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 1882462] Re: Displays wake up pre-maturely (likely driven by notification)
Also check that you don't have a Night Light schedule which might be triggering it: Settings > Screen Display > Night Light [in the top bar] -- 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/1882462 Title: Displays wake up pre-maturely (likely driven by notification) Status in gnome-shell package in Ubuntu: Confirmed Bug description: After a period of time, my displays go to sleep as they should. However, I often come back to find that the displays are awake, the mouse pointer is on a screen, but the screens are otherwise black. They're in this weird "awake but not fully on" mode. At that point, they will not go back to sleep as they should unless I fully awake them and let them go back to sleep. I don't know exactly what triggers the "half awake" but I suspect it's a notification. The displays shouldn't turn on without a user action. It wastes power and is clearly broken. I've attached a photo for an example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 16:10:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (684 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+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 1880728] Re: [amdgpu] Gnome Shell freeze
The crash in comment #9 is /opt/teamviewer/tv_bin/TeamViewer_Desktop While that doesn't appear to be a supported component of Ubuntu, if that is the main crash you experience then it would account for this bug. But still, we can't help with crashes of TeamViewer itself. So let's ignore any crashes in TeamViewer binaries here. We're only interested in crashes of 'gnome-shell' or 'Xorg'. Because those are provided by Ubuntu. Please continue repeating the steps from comment #2 as we still need to figure out the signature of a recurring problem in gnome-shell, if any. You also seem to have the extension 'dash-to-dock' loaded so please try removing 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/1880728 Title: [amdgpu] Gnome Shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: was logged in through team viewer and got kicked out. when i was able to physically access the machine the screens were on, but was not able to move the mouse or interact with the computer. performed hard reboot to get it back on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 26 11:24:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 [174b:e347] InstallationDate: Installed on 2020-05-09 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LM dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE(MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 80866566
Bionic is not relevant to this bug. There is nothing to verify. The bug only exists in mutter 3.36 onward. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1868520 Title: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) Status in Mesa: Fix Released Status in MPV: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Focal: Fix Committed Bug description: [Impact] Wayland apps fail to start in focal with: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 [Test Case] Just run: es2gears_wayland [Regression Potential] Medium/unknown. The fix is quite new. [Other Info] When attempting to run es2gears_wayland against GNOME Shell, it fails with: EGL_VERSION = 1.5 vertex shader info: fragment shader info: info: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 The full wayland protocol trace is: [3104432.914] -> wl_display@1.get_registry(new id wl_registry@2) [3104432.972] -> wl_disp...@1.sync(new id wl_callback@3) [3104433.139] wl_display@1.delete_id(3) [3104433.175] wl_registry@2.global(1, "wl_drm", 2) [3104433.207] wl_registry@2.global(2, "wl_compositor", 4) [3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id [unknown]@4) [3104433.285] wl_registry@2.global(3, "wl_shm", 1) [3104433.316] wl_registry@2.global(4, "wl_output", 2) [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3) [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3) [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 1) [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1) [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2) [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1) [3104433.513] wl_registry@2.global(11, "wl_shell", 1) [3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5) [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3) [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1) [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1) [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1) [3104433.699] wl_registry@2.global(16, "wl_seat", 5) [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1) [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1) [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1) [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1) [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3) [3104433.875] wl_registry@2.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1) [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1) [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1) [3104433.991] wl_callb...@3.done(3421) [3104436.266] -> wl_display@1.get_registry(new id wl_registry@3) [3104436.279] -> wl_disp...@1.sync(new id wl_callback@6) [3104436.647] wl_display@1.delete_id(6) [3104436.672] wl_registry@3.global(1, "wl_drm", 2) [3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7) [3104436.744] wl_registry@3.global(2, "wl_compositor", 4) [3104436.780] wl_registry@3.global(3, "wl_shm", 1) [3104436.790] wl_registry@3.global(4, "wl_output", 2) [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3) [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3) [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 1) [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1) [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2) [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1) [3104436.925] wl_registry@3.global(11, "wl_shell", 1) [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3) [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1) [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1) [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1) [3104436.990] wl_registry@3.global(16, "wl_seat", 5) [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1) [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1) [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1) [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1) [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3) [3104437.066] -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id [unknown]@8) [3104437.083] wl
[Desktop-packages] [Bug 1676069] Re: soxr resampling library not supported by pulseaudio
*** This bug is a duplicate of bug 1574746 *** https://bugs.launchpad.net/bugs/1574746 ** This bug has been marked a duplicate of bug 1574746 Enable support for libsoxr -- 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/1676069 Title: soxr resampling library not supported by pulseaudio Status in pulseaudio package in Ubuntu: Fix Released Bug description: AMD 64 Ubuntu 17.04 Beta 2 Pulseaudio 10.0 sampling rate 96K /24b in daemon.conf , set resample-method to soxr-vhq resample-method = soxr-vhq ;soxr-mq,soxr-hq, soxr-vhq. ;resample-method = speex-float-10 ;resample-method = copy restart pulseaudio, then launch VLC with MP3 file @ 44.1KHz Output of pulseaudio log : W: [pulseaudio] resampler.c: Support for resampler 'soxr-vhq' not compiled in, reverting to 'auto'. D: [pulseaudio] resampler.c: Resampler: D: [pulseaudio] resampler.c: rate 44100 -> 96000 (method speex-float-1) D: [pulseaudio] resampler.c: format float32le -> float32le (intermediate float32le) D: [pulseaudio] resampler.c: channels 2 -> 2 (resampling 2) I: [pulseaudio] speex.c: Choosing speex quality setting 1. So why soxr library is not compiled in ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1676069/+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 1720262] Re: gnome-screenshot Actions don't work in Wayland
This bug is already fixed and closed. Please report any remaining issues by running: ubuntu-bug gnome-shell -- 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/1720262 Title: gnome-screenshot Actions don't work in Wayland Status in GNOME Shell: Confirmed Status in gnome-screenshot package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in gnome-screenshot source package in Artful: Fix Released Bug description: Ubuntu 17.10 Beta Ubuntu session (Wayland) Open the Activities Overview. Right-click on Screenshot. 2 of the 3 extra desktop actions don't work. Works = Take a Screenshot of the Whole Screen Doesn't Work Take a Screenshot of the Current Window Take a Screenshot of a Selected Area Other Info == All 3 functions work if you open Screenshot and click the buttons in the app. The Current Window action is upstream, but Selected Area is an Ubuntu patch. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1720262/+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 1884001] [NEW] External 4k monitor periodically shows black screen
Public bug reported: I have a 4k dell monitor attached to a Dell XPS13 (2020). The connection is: Computer -> Thunderbolt (USBC) Cable -> Caldigit Thunderbolt Hub -> Thunderbolt-to-Displayport Cable -> Monitor. Note: The Thunderbolt cable from the Caldigit hub is powered. I have a keyboard, mouse, monitor etc all attached to the thunderbolt hub. So there is just one cable connected to the laptop, which is nice. If I wake my laptop, everything's fine for a few minutes, then periodically the screen goes black for a second or two, then back to display. This happens with increasing frequency. If I log out and log back in, the problem is usually resolved. Sometimes I have to unplug and replug the hub from my laptop. I assume this is xorg-related because logging out and back in effectively restarts X. But X might not be the problem, it might be thunderbolt-related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 18:22:45 2020 DistUpgraded: 2020-04-28 11:49:08,077 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-03-14 (95 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=15b70d1f-6d44-4cea-a1ad-10b0924bc69b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (50 days ago) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884001 Title: External 4k monitor periodically shows black screen Status in xorg package in Ubuntu: New Bug description: I have a 4k dell monitor attached to a Dell XPS13 (2020). The connection is: Computer -> Thunderbolt (USBC) Cable -> Caldigit Thunderbolt Hub -> Thunderbolt-to-Displayport Cable -> Monitor. Note: The Thunderbolt cable from the Caldigit hub is powered. I have a keyboard, mouse, monitor etc all attached to the thunderbolt hub. So there is just one cable connected to the laptop, which is nice. If I wake my laptop, everything's fine for a few minutes, then periodically the screen goes black for a second or two, then back to display. This happens with increasing frequency. If I log out and log back in, the problem is usually resolved. Sometimes I have to unplug and replug the hub from my laptop. I assume this is xorg-related because logging out and back in effectively restarts X. But X might not be the problem, it might be thunderbolt-related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDeskt
[Desktop-packages] [Bug 1814238] Re: deja-dup saves passphrase in /tmp
** Changed in: deja-dup Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1814238 Title: deja-dup saves passphrase in /tmp Status in Déjà Dup: Fix Committed Status in deja-dup package in Ubuntu: Triaged Bug description: I have unchecked the "save passphrase" option in deja-dup, but still I have found the file /tmp/deja-dup-HXGLWZ that contains my passphrase in the clear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-2fakesync1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 10:59:06 2019 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1814238/+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 1815056] Re: deja-dup is aksing for the admin password
** Also affects: deja-dup Importance: Undecided Status: New ** Changed in: deja-dup Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1815056 Title: deja-dup is aksing for the admin password Status in Déjà Dup: Fix Committed Status in deja-dup package in Ubuntu: New Bug description: This is on Ubuntu 18.04.1 LTS with deja-dup 37.1-2fakesync1ubuntu0.1. I'm using deja-dup for backup of my home directory. I don't have sudo permissions on the machine. I have only my home in backup and all files are owned by me. Still I always get this message: "Privileges are required to restore files to system locations". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-2fakesync1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 15:38:37 2019 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1815056/+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 1863506] Re: mate-session[1159]: WARNING: Could not parse desktop file /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized desktop file Version '1.1'
** Changed in: deja-dup Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1863506 Title: mate-session[1159]: WARNING: Could not parse desktop file /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized desktop file Version '1.1' Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Invalid Status in mate-session-manager package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Remove `~/.xsession-errors` and then login 3. Open `~/.xsession-errors` Expected results: * `~/.xsession-errors` do not have warnings Actual results: * `~/.xsession-errors` have warnings: mate-session[1159]: WARNING: Could not parse desktop file /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized desktop file Version '1.1' mate-session[1159]: WARNING: could not read /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.5-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Sun Feb 16 21:49:08 2020 InstallationDate: Installed on 2020-02-16 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200216) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1863506/+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 1880728] Re: [amdgpu] Xorg freeze
crashed again this afternoon. attached is another prevboot file. On Wed, Jun 17, 2020 at 8:11 AM DavidJr. wrote: > Crashed again overnight. Went to wake the screen (the computer doesnt > sleep, just turns off the screen) and got no response from the mouse or > keyboard. When i pressed the power buttonit woke the screen, but it was > just a black screen with the mouse cursor displayed, but not able to be > moved. There is a new error on errors.ubuntu.com, but it was in the > afternoon and i used it in the evening just fine. Here is the link: > https://errors.ubuntu.com/oops/1abba6b4-b09b-11ea-aba8-fa163ee63de6 > > i also am attaching another prevboot file that i ran after it powered up > this morning. > > On Mon, Jun 15, 2020 at 9:29 PM DavidJr. wrote: > >> attached is the file requested. I have unplugged the viewsonic monitor >> from the GPU and will run for a while to see if it still has issues. >> >> On Mon, Jun 15, 2020 at 9:00 PM Daniel van Vugt < >> 1880...@bugs.launchpad.net> wrote: >> >>> Thanks. Certainly gnome-shell is crashing so we should focus on those: >>> >>> https://errors.ubuntu.com/oops/f1dcc3fa-988e-11ea-ad8b-fa163e983629 >>> https://errors.ubuntu.com/oops/f3279c74-95fc-11ea-a45e-fa163e6cac46 >>> https://errors.ubuntu.com/oops/53690272-9516-11ea-a9c3-fa163ee63de6 >>> >>> Unfortunately there isn't any debugging information available in those. >>> >>> What I can see is a recurring problem with your ViewSonic monitor being >>> redetected/reconnected on DVI regularly. So it looks like there's a >>> connection problem there which might be triggering this. Please try >>> replacing the DVI cable, or leaving the ViewSonic unplugged for a while >>> to see if the problem goes away. >>> >>> Please also run this command: >>> >>> gsettings list-recursively org.gnome.shell > settings.txt >>> >>> and then attach the resulting text file here. >>> >>> >>> ** Summary changed: >>> >>> - [amdgpu] Xorg freeze >>> + [amdgpu] Gnome Shell freeze >>> >>> ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1880728 >>> >>> Title: >>> [amdgpu] Gnome Shell freeze >>> >>> Status in gnome-shell package in Ubuntu: >>> Incomplete >>> >>> Bug description: >>> was logged in through team viewer and got kicked out. when i was able >>> to physically access the machine the screens were on, but was not able >>> to move the mouse or interact with the computer. performed hard >>> reboot to get it back on. >>> >>> ProblemType: Bug >>> DistroRelease: Ubuntu 20.04 >>> Package: xorg 1:7.7+19ubuntu14 >>> ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 >>> Uname: Linux 5.4.0-31-generic x86_64 >>> ApportVersion: 2.20.11-0ubuntu27 >>> Architecture: amd64 >>> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >>> CasperMD5CheckResult: skip >>> CompositorRunning: None >>> CurrentDesktop: ubuntu:GNOME >>> Date: Tue May 26 11:24:02 2020 >>> DistUpgraded: Fresh install >>> DistroCodename: focal >>> DistroVariant: ubuntu >>> ExtraDebuggingInterest: Yes >>> GpuHangFrequency: Several times a week >>> GpuHangReproducibility: Seems to happen randomly >>> GpuHangStarted: Immediately after installing this version of Ubuntu >>> GraphicsCard: >>>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX >>> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA >>> controller]) >>> Subsystem: PC Partner Limited / Sapphire Technology Radeon RX >>> 470/480 [174b:e347] >>> InstallationDate: Installed on 2020-05-09 (16 days ago) >>> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 >>> (20200423) >>> MachineType: Micro-Star International Co., Ltd. MS-7A34 >>> ProcEnviron: >>>PATH=(custom, no user) >>>XDG_RUNTIME_DIR= >>>LANG=en_US.UTF-8 >>>SHELL=/bin/bash >>> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic >>> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7 >>> SourcePackage: xorg >>> Symptom: display >>> Title: Xorg freeze >>> UpgradeStatus: No upgrade log present (probably fresh install) >>> dmi.bios.date: 07/08/2019 >>> dmi.bios.vendor: American Megatrends Inc. >>> dmi.bios.version: A.LM >>> dmi.board.asset.tag: To be filled by O.E.M. >>> dmi.board.name: B350 PC MATE(MS-7A34) >>> dmi.board.vendor: Micro-Star International Co., Ltd >>> dmi.board.version: 2.0 >>> dmi.chassis.asset.tag: To be filled by O.E.M. >>> dmi.chassis.type: 3 >>> dmi.chassis.vendor: Micro-Star International Co., Ltd. >>> dmi.chassis.version: 2.0 >>> dmi.modalias: >>> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: >>> dmi.product.family: To be fille
[Desktop-packages] [Bug 1871864] Re: Toggle "Fractional Scaling" does nothing on wayland
** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => In Progress ** Also affects: gnome-control-center (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871864 Title: Toggle "Fractional Scaling" does nothing on wayland Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: System: Ubuntu Focal Fossa (Development Branch) 20.04 Version of "gnome-control-center": 1:3.36.1-1ubuntu4 In the setting there is option called "Fractional Scaling" but this option only works for X11. What is the problem: Enabling "Fractional Scaling" adds only ['x11-randr-fractional-scaling'] but ['scale-monitor-framebuffer'] What it should be: Enabling "Fractional Scaling" in the setting adds parameter for both X11 and wayland: ['x11-randr-fractional-scaling', 'scale-monitor-framebuffer'] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 23:43:57 2020 InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871864/+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 1881458] Re: Playback aborts when a download is started, printing "server does not support seeking"
What is your network speed ( mbps ) ? When you start your downloads, does other apps ( browser page loading / youtube in browser ) work fine or they are stalled too ? You can give the following steps to get some insight into the issue: 1. Rhythmbox ( RB ) uses gstreamer backend for playing audio files. This step confirms if the problem is with gstreamer or RB. Run the following commands from the terminal. $ sudo apt-get install gstreamer1.0-tools $ gst-launch-1.0 playbin uri="http://stream-dc1.radioparadise.com/rp_192m.ogg"; This should play the audio stream. You can substitute your audio stream URI in the above command. Now start the downloads. If the playback is stuck / aborted etc, the same way as it happens in Rhythmbox, this is a gstreamer limitation and RB can do very little about it. Try opening a gstreamer bug at https://gitlab.freedesktop.org/gstreamer/gst-plugins- base/-/issues/new 2. If audio plays fine in above step, start rhythmbox in terminal as below $ rhythmbox -d &> ~/rhythmbox.log Start audio streams followed by downloads. Wait for the playback issues to show up. Quit Rhythmbox and attach rhythmbox.log in this bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" Status in rhythmbox package in Ubuntu: New Bug description: Whenever heavy traffic starts on my network, Rhythmbox will abruptly stop playing audio streams. The traffic in question may be local data transfer or (mostly large) downloads. The same happens to local audio streams managed by pulseaudio. A data transfer starts and the stream very much immediately cuts out. Typically, rhythmbox will pops up a dialog saying "server does not support seeking". I can usually resume playback but during longer data transfers/downloads, it will frequently cut out again. I have tried replacing the onboard audio chip with a discrete ASUS DX card. This does not make any difference. What does work is manually restricting download speeds using a download manager. However,, not all network traffic is controlled by such a manager. Something trivial - say, installing a firefox or a gnome-shell plug-in - has been enough for an audio stream to die instantly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 05:06:56 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-04-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+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 1877108] Re: Ubuntu Dock appears on the display opposite to that indicated on Appearance tab
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => In Progress ** Also affects: gnome-control-center (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1877108 Title: Ubuntu Dock appears on the display opposite to that indicated on Appearance tab Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: I am unable to use ubuntu-bug to raise this report as I have upgraded to a new version in -proposed to test bug 1866088. This issue was not addressed in that bug fix. paul@n1644:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 100 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages I am using a a laptop with an external monitor set up as follows: Display 1 is the laptop's built-in monitor Display 2 is the external monitor set as being the primary display To reproduce: 1) Go to the Appearance tab 2) "Show on" will indicate on which display the dock is being shown 3) In my case it is set to "1. Built in display" but it appears on the second or primary display 4) Change the setting and the dock will move but... 5) In my case if I change to "2. GKE 24 (Primary display)" the dock appears on the built-in display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877108/+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 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.
I'm new to this forum and not sure what the status of this bug is. My situation: HP Spectre x360 laptop with the AX201 Wifi/BT chip. My wifi seems to work fine but I have "no bluetooth device" in Ubuntu 20.04 or 19.10. I'd really like to have my bluetooth working. The output of lshw shows the wifi as AC9462. The output of sudo journalctl -k | grep 'iwlwifi' Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: enabling device ( -> 0002) Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2 Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2 Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: Found debug configuration: 0 Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3: base HW address: 0c:dd:24:d1:ce:d2 Jun 17 17:03:44 misen-spectre kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 Jun 17 17:05:14 misen-spectre kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM Jun 17 17:05:14 misen-spectre kernel: iwlwifi :00:14.3: FW already configured (0) - re-configuring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1876847 Title: HP-Spectre 2019 Intel wireless driver is detected incorrectly. Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Incorrect wifi drivers detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1876847/+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 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
@daniel: I have 2 extra DVI to HDMI adapters that I would be happy to ship to you if it would help in solving this issue. My DMs are open on Twitter (@travisdieckmann) if you’d like to let me know where I can ship them. On Wed, Jun 17, 2020 at 1:05 PM Peter Klaesson <1874...@bugs.launchpad.net> wrote: > @Daniel: Sounds like something you should be able to have access too if > you are assigned to test this. > > Do you have any thought about how it could be solved? I mean, you need a > new card or an adapter(?) for your current card? > > I have no idea how this works for you financially. Can you get what you > need and get the expenses covered by Canonical? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1874217 > > Title: > [nvidia] Dual monitor setup with secondary monitor in portrait-right > mode cause tiled windows to occupy 1.5 monitors > > Status in gnome-control-center: > Unknown > Status in Mutter: > Unknown > Status in gnome-control-center package in Ubuntu: > Triaged > Status in mutter package in Ubuntu: > Confirmed > > Bug description: > I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. > > I use dual screen : the main screen is on the left side (32"), the > secondary screen (19") is at right and in portrait mode (rotated > right). The window are improperly growed : they extend from full main > screen to half the "witdh" of the secondary screen. Additionnally, the > « pop-up » menus (eg. from settings) do not appear at the right place > (see screen capture in comment). The problem disappears if I revert > the orientation of secondary screen from « portrait turned right » to > « landscape ». I do have gnome-shell-extension-ubuntu-dock in version > 67ubuntu20.04.5, but still got the problem. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-shell 3.36.1-5ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 > Uname: Linux 5.4.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Wed Apr 22 11:11:25 2020 > DisplayManager: gdm3 > InstallationDate: Installed on 2020-04-19 (2 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions > -- Best regards, Travis Dieckmann Ph: 317-341-2727 tadieckm...@gmail.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-co
[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same issue here. Ubuntu 18.04, kernel 5.3.0-53-generic, pulseaudio 11.1, sound card: Intel Sunrise Point-LP HD Audio (HDA Intel PCH) and chipset: Conexant Generic. Name: H1 Pro Alias: H1 Pro Class: 0x00240418 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
** Summary changed: - Rhythmnox ignores pulseaudio default sink and outputs sound on random device + rhythmbox ignores pulseaudio default sink and outputs sound on random device -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+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 1883981] [NEW] dash-to-dock extension gets buggy after lock
Public bug reported: Works perfect on boot. After 1st lock both dash-to-dock and ubuntu-gnome-dock appear on Activities Overview. On 2nd lock, dash-to-dock appears on lockscreen. After 2nd lock, two docks appear (overlapped) on the homescreen (desktop). Dash to dock - version 68 Gnome 3.36.2 Ubuntu 20.04 LTS x64 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 23:27:58 2020 InstallationDate: Installed on 2020-06-15 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1883981 Title: dash-to-dock extension gets buggy after lock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Works perfect on boot. After 1st lock both dash-to-dock and ubuntu-gnome-dock appear on Activities Overview. On 2nd lock, dash-to-dock appears on lockscreen. After 2nd lock, two docks appear (overlapped) on the homescreen (desktop). Dash to dock - version 68 Gnome 3.36.2 Ubuntu 20.04 LTS x64 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 23:27:58 2020 InstallationDate: Installed on 2020-06-15 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1883981/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3
On 2020-06-17 15:31, vasdi wrote: > It does not affect new users. That's important (and explains why I failed to reproduce the issue). So it's something in your $HOME which causes it. It may be some subtle thing somewhere in e.g. your ~/.cache folder. If you like, you can rename that folder: mv ~/.cache ~/.cache.old and relogin. The issue you experienced is probably some sort of bug. I'm not sure, though, if it's practicable to figure out exactly what the problem is and how it happened. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1882415 Title: Graphical artifact in top-right corner, owned by ibus-ui-gtk3 Status in gnome-shell package in Ubuntu: New Status in ibus package in Ubuntu: New Status in im-config package in Ubuntu: New Bug description: Ubuntu 20.04, Gnome 3.36.2, Nvidia Small gray line in top-right corner. More precisely, it happens to be in the corner in 1920x1080 resolution. Not present in smaller resolutions. In panning mode it's fixed to panel, not screen. Present on the panel and on fullscreen windows but not in overview. Not clickable (prevents me from clicking button underneath it). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2014-11-12 (2037 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 Tags: focal Uname: Linux 5.4.0-37-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1792000] Re: VirtualBox icon does not show un dock until screen locks
Confirmed on focal, it's also not an issue with a GNOME session in the 'overview screen launcher' so seems specific to dashtodock ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Confirmed ** Tags added: desktop-lts-wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1792000 Title: VirtualBox icon does not show un dock until screen locks Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Quite simple: I start VirtualBox or a virtual machine straight from the build directory (without installing) and the icon in the dock is a red, crossed-out circle. After deliberately or due to a timeout locking the screen and unlocking it, the correct X11 property icon is shown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 11 20:32:51 2018 InstallationDate: Installed on 2018-06-12 (91 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1792000/+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 1424201]
(In reply to eric.riese from comment #34) > > In my opinion the bounty was already earned when this issue was resolved but > I don't know who gets to be the arbiter. That would certainly be Martin Stránský :) Martin, do you want to claim the bounty? If you don't care about it / don't need it yourself, you could donate it or so. -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1424201]
Reminder that there is still a bounty for this issue at BountySource https://www.bountysource.com/issues/55506502-add-va-api-hardware- decoding-support-on-linux I got an email from BountySource that they're going to start taking old bounties for themselves starting *2020-07-1* (reproduced below) In my opinion the bounty was already earned when this issue was resolved but I don't know who gets to be the arbiter. ``` Hi, You are receiving this email because we are updating the Bountysource Terms of Service, effective 1st July 2020. What's changing? We have added a Time-Out clause to the Bounties section of the agreement: 2.13 Bounty Time-Out. If no Solution is accepted within two years after a Bounty is posted, then the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource. For Bounties posted before June 30, 2018, the Backer may redeploy their Bounty to a new Issue by contacting supp...@bountysource.com before July 1, 2020. If the Backer does not redeploy their Bounty by the deadline, the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource. You can read the full Terms of Service here What do I need to do? If you agree to the new terms, you don't have to do anything. If you have a bounty posted prior to June 30, 2018 that is not currently being solved, email us at supp...@bountysource.com to redeploy your bounty. Or, if you do not agree with the new terms, please discontinue using Bountysource. Thanks for reading Bountysource Team ``` -- 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 80866566
I tested version '20.0.8-0ubuntu1~20.04.1' from 'focal-proposed' and it fixes the issues I encountered with EGL and specifically 'es2gears_wayland'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1868520 Title: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) Status in Mesa: Fix Released Status in MPV: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Focal: Fix Committed Bug description: [Impact] Wayland apps fail to start in focal with: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 [Test Case] Just run: es2gears_wayland [Regression Potential] Medium/unknown. The fix is quite new. [Other Info] When attempting to run es2gears_wayland against GNOME Shell, it fails with: EGL_VERSION = 1.5 vertex shader info: fragment shader info: info: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 The full wayland protocol trace is: [3104432.914] -> wl_display@1.get_registry(new id wl_registry@2) [3104432.972] -> wl_disp...@1.sync(new id wl_callback@3) [3104433.139] wl_display@1.delete_id(3) [3104433.175] wl_registry@2.global(1, "wl_drm", 2) [3104433.207] wl_registry@2.global(2, "wl_compositor", 4) [3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id [unknown]@4) [3104433.285] wl_registry@2.global(3, "wl_shm", 1) [3104433.316] wl_registry@2.global(4, "wl_output", 2) [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3) [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3) [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 1) [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1) [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2) [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1) [3104433.513] wl_registry@2.global(11, "wl_shell", 1) [3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5) [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3) [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1) [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1) [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1) [3104433.699] wl_registry@2.global(16, "wl_seat", 5) [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1) [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1) [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1) [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1) [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3) [3104433.875] wl_registry@2.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1) [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1) [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1) [3104433.991] wl_callb...@3.done(3421) [3104436.266] -> wl_display@1.get_registry(new id wl_registry@3) [3104436.279] -> wl_disp...@1.sync(new id wl_callback@6) [3104436.647] wl_display@1.delete_id(6) [3104436.672] wl_registry@3.global(1, "wl_drm", 2) [3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7) [3104436.744] wl_registry@3.global(2, "wl_compositor", 4) [3104436.780] wl_registry@3.global(3, "wl_shm", 1) [3104436.790] wl_registry@3.global(4, "wl_output", 2) [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3) [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3) [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 1) [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1) [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2) [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1) [3104436.925] wl_registry@3.global(11, "wl_shell", 1) [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3) [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1) [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1) [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1) [3104436.990] wl_registry@3.global(16, "wl_seat", 5) [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1) [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1) [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1) [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1) [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3) [3104437.066] -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1",
[Desktop-packages] [Bug 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 80866566
I have tested 20.0.8 from focal-proposed. I have tested both es2gears_wayland and mpv under wayland and both programs work for me. This is the list of packages upgraded Install: libllvm10:amd64 (1:10.0.0-4ubuntu1, automatic) Upgrade: libegl-mesa0:amd64 (20.0.4-2ubuntu1, 20.0.8-0ubuntu1~20.04.1), libglapi-mesa:amd64 (20.0.4-2ubuntu1, 20.0.8-0ubuntu1~20.04.1), libgbm1:amd64 (20.0.4-2ubuntu1, 20.0.8-0ubuntu1~20.04.1), libgl1-mesa-dri:amd64 (20.0.4-2ubuntu1, 20.0.8-0ubuntu1~20.04.1), mesa-vdpau-drivers:amd64 (20.0.4-2ubuntu1, 20.0.8-0ubuntu1~20.04.1), mesa-vulkan-drivers:amd64 (20.0.4-2ubuntu1, 20.0.8-0ubuntu1~20.04.1), mesa-va-drivers:amd64 (20.0.4-2ubuntu1, 20.0.8-0ubuntu1~20.04.1), libglx-mesa0:amd64 (20.0.4-2ubuntu1, 20.0.8-0ubuntu1~20.04.1) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1868520 Title: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) Status in Mesa: Fix Released Status in MPV: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Focal: Fix Committed Bug description: [Impact] Wayland apps fail to start in focal with: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 [Test Case] Just run: es2gears_wayland [Regression Potential] Medium/unknown. The fix is quite new. [Other Info] When attempting to run es2gears_wayland against GNOME Shell, it fails with: EGL_VERSION = 1.5 vertex shader info: fragment shader info: info: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 The full wayland protocol trace is: [3104432.914] -> wl_display@1.get_registry(new id wl_registry@2) [3104432.972] -> wl_disp...@1.sync(new id wl_callback@3) [3104433.139] wl_display@1.delete_id(3) [3104433.175] wl_registry@2.global(1, "wl_drm", 2) [3104433.207] wl_registry@2.global(2, "wl_compositor", 4) [3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id [unknown]@4) [3104433.285] wl_registry@2.global(3, "wl_shm", 1) [3104433.316] wl_registry@2.global(4, "wl_output", 2) [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3) [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3) [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 1) [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1) [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2) [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1) [3104433.513] wl_registry@2.global(11, "wl_shell", 1) [3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5) [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3) [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1) [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1) [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1) [3104433.699] wl_registry@2.global(16, "wl_seat", 5) [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1) [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1) [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1) [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1) [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3) [3104433.875] wl_registry@2.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1) [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1) [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1) [3104433.991] wl_callb...@3.done(3421) [3104436.266] -> wl_display@1.get_registry(new id wl_registry@3) [3104436.279] -> wl_disp...@1.sync(new id wl_callback@6) [3104436.647] wl_display@1.delete_id(6) [3104436.672] wl_registry@3.global(1, "wl_drm", 2) [3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7) [3104436.744] wl_registry@3.global(2, "wl_compositor", 4) [3104436.780] wl_registry@3.global(3, "wl_shm", 1) [3104436.790] wl_registry@3.global(4, "wl_output", 2) [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3) [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3) [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 1) [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1) [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2) [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1) [3104436.925] wl_registry@3.global(11, "wl_shell", 1) [3104436.937] wl_registry@3.glo
[Desktop-packages] [Bug 1883965] [NEW] gnome-software consumes 600 MB of memory after 6 days uptime
Public bug reported: The gnome-software background process consumes 600 MB of memory after 6 days uptime. I think this is a memory leak. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 21:41:49 2020 InstallationDate: Installed on 2020-04-26 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snapN/A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1883965 Title: gnome-software consumes 600 MB of memory after 6 days uptime Status in gnome-software package in Ubuntu: New Bug description: The gnome-software background process consumes 600 MB of memory after 6 days uptime. I think this is a memory leak. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 21:41:49 2020 InstallationDate: Installed on 2020-04-26 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snapN/A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1883965/+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 1883292] Re: Laptop not suspending on lid close after external monitors disconnected
The gdm processes should be stopped when switching to the session, there is a bug there... ** Package changed: gnome-settings-daemon (Ubuntu) => gdm3 (Ubuntu) -- 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/1883292 Title: Laptop not suspending on lid close after external monitors disconnected Status in gdm3 package in Ubuntu: New Bug description: I have a Dell XPS 13 9380 laptop with Type-C dock. There are two external monitors (DisplayPort) and USB mouse attached to the doc. Normally I disconnect the dock cable from the laptop, close the laptop lid and laptop suspends. However, sometimes it doesn't suspend. I can see the 'Lid closed.' message in systemd-logind log which is normally followed by a sleep. Once this happens, laptop no longer suspends on lid close until I restart Gnome session. Also, if I lock it, the screen goes black but the backlight does not turn off. I can put computer to a sleep from Gnome menu. I'm not sure if it's issue is specific to Type-C dock though. It happens rarely, maybe 1 of 20 times. It appears like gsd does not detect monitors disconnect event in some cases: abram@abram-laptop:~$ systemd-inhibit --list --mode=block WHO UID USER PID COMM WHAT WHY MODE gdm 123 gdm 1977595 gsd-power handle-lid-switch External monitor attached or configuration changed recently block gdm 123 gdm 1977593 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block abram 1000 abram 779130 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block 3 inhibitors listed. I've also seen a similar issue mentioned at askubuntu: https://askubuntu.com/questions/1196871/gnome-supend-on-laptop-lid-close-no-longer-works-since-19-10-upgrade The accepted answer involves killing gsd-power but that's more like a workaround than a fix; the same presumably happens when Gnome session is restarted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jun 12 19:19:35 2020 InstallationDate: Installed on 2019-04-17 (421 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-04-02 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1883292/+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 1883534] Re: Screen flickering
*** This bug is a duplicate of bug 1853094 *** https://bugs.launchpad.net/bugs/1853094 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1883534 Title: Screen flickering Status in xorg package in Ubuntu: Confirmed Bug description: To whom it may concern, As stated I have screen flickerings (see lightning like flickering on photo attached for portrait screen, for horizontal screen I also have screen flickering on the upper part but hard to catch in a photo) on freshly installed Ubuntu 20.04 LTS. I have tried this: https://askubuntu.com/questions/1231441/ubuntu-screen-flickering and this: https://learnubuntumate.weebly.com/screen-tearing-on-intel- graphics.html without success. I have also seen some other people mentioning screen flickering on ubuntu 20.04 here: https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/ without solution. I also know that it is very unlikely hardware problem because my screens were displaying well on archlinux. I think my graphic card info are already included in the report but just in case: Intel Corporation UHD Graphics 630. Might be intel driver problems ? Could you help me on this please ? Best regards, Jeremy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 15:05:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] InstallationDate: Installed on 2020-06-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0615 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534/+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 1883920] Re: ubuntu logo in wslfetch needs update
Thanks, could be useful if you included a screenshot of what is the intended branding so it's easier for someone to verify that the right thing is displayed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version. [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown. [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+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 1883958] [NEW] package tex-common 6.04ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: I try to install the tar package and isn't possible because this error occurs. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.23 AptOrdering: tex-common: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 17 15:46:04 2020 DpkgHistoryLog: Start-Date: 2020-06-17 15:45:58 Commandline: apt install tar Requested-By: marcelo (1000) ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2012-02-07 (3053 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1883958 Title: package tex-common 6.04ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in tex-common package in Ubuntu: New Bug description: I try to install the tar package and isn't possible because this error occurs. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.23 AptOrdering: tex-common: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 17 15:46:04 2020 DpkgHistoryLog: Start-Date: 2020-06-17 15:45:58 Commandline: apt install tar Requested-By: marcelo (1000) ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2012-02-07 (3053 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1883958/+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 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
** Attachment added: "syslog061720" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+attachment/5384827/+files/syslog061720 -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.: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.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
Never mind, the problem occurs with the analogue sound card. What's next? I've attached another two sample error logs from syslog. System freeze after the error message reported above (you can find it after searching for error message). ** Attachment added: "syslog061320" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+attachment/5384826/+files/syslog061320 -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.: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.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I can confirm that Michael's solution also fixed it for me. I didn't have the 19.10 config to hand so I extracted default.pa from the .deb from 19.10 as found here https://launchpad.net/ubuntu/bionic/amd64/pulseaudio/1:11.1-1ubuntu7, ran the diff, restarted Pulseaudio and the HSP/HFP profile worked immediately. Thank you Michael! -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1676069] Re: soxr resampling library not supported by pulseaudio
** Changed in: pasystray (Ubuntu) Status: Confirmed => Fix Released ** Package changed: pasystray (Ubuntu) => pulseaudio (Ubuntu) -- 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/1676069 Title: soxr resampling library not supported by pulseaudio Status in pulseaudio package in Ubuntu: Fix Released Bug description: AMD 64 Ubuntu 17.04 Beta 2 Pulseaudio 10.0 sampling rate 96K /24b in daemon.conf , set resample-method to soxr-vhq resample-method = soxr-vhq ;soxr-mq,soxr-hq, soxr-vhq. ;resample-method = speex-float-10 ;resample-method = copy restart pulseaudio, then launch VLC with MP3 file @ 44.1KHz Output of pulseaudio log : W: [pulseaudio] resampler.c: Support for resampler 'soxr-vhq' not compiled in, reverting to 'auto'. D: [pulseaudio] resampler.c: Resampler: D: [pulseaudio] resampler.c: rate 44100 -> 96000 (method speex-float-1) D: [pulseaudio] resampler.c: format float32le -> float32le (intermediate float32le) D: [pulseaudio] resampler.c: channels 2 -> 2 (resampling 2) I: [pulseaudio] speex.c: Choosing speex quality setting 1. So why soxr library is not compiled in ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1676069/+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 1616650] Re: snap refresh while command is running may cause issues
I'm working using $SNAP_USER_COMMON to store chromium profiles, to mitigate the issue. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => In Progress ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1616650 Title: snap refresh while command is running may cause issues Status in snapd: In Progress Status in chromium-browser package in Ubuntu: In Progress Bug description: In testing a desktop snap that saves state in $HOME on close, I noticed that if I snap refresh the snap while the command is running that it will try to save its state to the previous snap version's data directory. For the snap I was testing (a browser), this resulted in a very poor user experience (the browser on restart complained about an improper shutdown). What is happening is that: 1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something like /home/user/snap/foo/x1. The security policy correctly allows writes to SNAP_USER_DATA 2. on snap refresh to 'x2', the security policy for the snap is updated for the running process such that /home/user/snap/foo/x1 is readonly and /home/user/snap/foo/x2 is read/write 3. the command in '1's environment is not changed and HOME (as well as SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path 4. the command tries to shutdown gracefully and save state to the 'x1' HOME and security policy blocks it Snappy's design for rollbacks relies on the previous SNAP_DATA and SNAP_USER_DATA directories not being writable and IMHO we should not change the policy to make other snap version's data dirs writable. The design of the snappy state engine ensures (among other things) that there is only ever one security policy in place for the snap. In snappy 15.04 this problem was (intentionally) avoided because we used snap security policy that was versioned such that the new policy would not apply until the next app invocation. Gustavo and Zygmunt, you both advocated strongly for only one version of the policy on disk and loaded in the kernel and I recall bringing up this type of bug as a counter-argument, and if IIRC for daemons we said that snapd could simply restart them (makes perfect sense). Have you thought of the mechanism for restarting non-daemons? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+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 1676069] [NEW] soxr resampling library not supported by pulseaudio
You have been subscribed to a public bug: AMD 64 Ubuntu 17.04 Beta 2 Pulseaudio 10.0 sampling rate 96K /24b in daemon.conf , set resample-method to soxr-vhq resample-method = soxr-vhq ;soxr-mq,soxr-hq, soxr-vhq. ;resample-method = speex-float-10 ;resample-method = copy restart pulseaudio, then launch VLC with MP3 file @ 44.1KHz Output of pulseaudio log : W: [pulseaudio] resampler.c: Support for resampler 'soxr-vhq' not compiled in, reverting to 'auto'. D: [pulseaudio] resampler.c: Resampler: D: [pulseaudio] resampler.c: rate 44100 -> 96000 (method speex-float-1) D: [pulseaudio] resampler.c: format float32le -> float32le (intermediate float32le) D: [pulseaudio] resampler.c: channels 2 -> 2 (resampling 2) I: [pulseaudio] speex.c: Choosing speex quality setting 1. So why soxr library is not compiled in ? ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Fix Released -- soxr resampling library not supported by pulseaudio https://bugs.launchpad.net/bugs/1676069 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
@Daniel: Sounds like something you should be able to have access too if you are assigned to test this. Do you have any thought about how it could be solved? I mean, you need a new card or an adapter(?) for your current card? I have no idea how this works for you financially. Can you get what you need and get the expenses covered by Canonical? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+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 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
I've just tested the proposed bionic 20.0.8-0ubuntu1~18.04.1. It's working for my bug. Hope we get release soon now :) As you know bionic is under LTS support until 2023.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: Fix Released Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1882781] Re: Gnome 3.36.2 leaking in 20.04
*** This bug is a duplicate of bug 1856838 *** https://bugs.launchpad.net/bugs/1856838 I haven't been running any of the weather widgets for a while now and I had to do another reset of gnome just to get window animation speeds back to normal. This issue is definitely present on a vanilla configuration. -- 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/1882781 Title: Gnome 3.36.2 leaking in 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've noticed lately that the performance of the UI in Gnome 3.36.2 seems to decay with uptime. The most obvious manifestation is that over time, window animations have a delay and feel "sticky". Applications themselves seem unaffected. When I tell gnome to switch workspaces, there's about a half second to full second delay before the animation happens. This also applies to things like pressing the meta key to show all my windows or pressing alt-tab. Each one appears to share the same delay. I'm running a fairly unremarkable desktop setup using vanilla gnome on Ubuntu 20.04. My research on this issue seems to indicate that there were memory leak issues in 18.xx versions of the OS, but that those were supposedly fixed. The only thing I can conclude at this point is that a new issue has emerged, there was a regression, or the original fix didn't work. The animation delay is sapping productivity to the point that I eventually have to reboot my system. The gnome-shell process definitely leaks over time as it starts around ~300mb and if left for a day will sit at ~600mb or more. --- Regarding my overall hardware and nominal state of my system, I'm experiencing this issue even as I'm creating this question. I'm running the stock/vanilla gnome desktop, not the ubuntu customized one. My system has 32gb of RAM, only 6gb of which are in use currently. My CPU usage fluctuates across 12 vcores up to 20% max. I have an RTX 2060 for my GPU. At least as best as I can tell, I see no issue with the amount of resources gnome-shell is getting right now. 😉 --- There also appear to be other accounts of this same issue building up since the release of 20.04. It's clear that this is a widespread issue: https://www.reddit.com/r/gnome/comments/fxffcd/gnome_shell_336_in_ubuntu_2004_still_leaks/ I would treat this with some urgency as for regular users this bug renders the OS completely unusable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Jun 9 08:19:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882781/+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 1883924] Re: Ubuntu.exe will not be detected properly if other LTS version is installed
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/385930 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883924 Title: Ubuntu.exe will not be detected properly if other LTS version is installed Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases when using from the Ubuntu app from Microsoft Store. When other LTS version of app is installed from Microsoft Store, baseexec generated by wslu on Ubuntu app will not be using ubuntu.exe but other LTS release apps (such as ubuntu1804.exe) [Test Case] * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store. * run any wslu tools (like wslfetch --help) * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+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 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/385930 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Confirmed Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution * run any wslu tool (like wslfetch) * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 19m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+
[Desktop-packages] [Bug 1883920] Re: ubuntu logo in wslfetch needs update
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/385930 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version. [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown. [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+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 1749774] Re: include fwupd packages in Server Seed
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1749774 Title: include fwupd packages in Server Seed Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: fwupd is the closest we have to a standard mechanism currently for doing in-band firmware updates in a vendor agnostic way. As long as the vendors provide firmware blobs in an appropriately formatted package, fwupd (or fwupdate) can install those firmware blobs from within Ubuntu. Because of this, we should include the related packages in the server seed. The main components all live in Main currently. As far as I can tell (verified on a Bionic install), nothing in the current server seed pulls in fwupd, fwupdate, or fwupdate-signed as a dependency. ubuntu@xwing:~$ apt-cache policy fwup* fwupdate: Installed: (none) Candidate: 10-2 Version table: 10-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages fwupd: Installed: (none) Candidate: 1.0.4-3build1 Version table: 1.0.4-3build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages fwupdate-signed: Installed: (none) Candidate: 1.17+10-2 Version table: 1.17+10-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1749774/+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 1883924] Re: Ubuntu.exe will not be detected properly if other LTS version is installed
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/384608 ** Changed in: wslu (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: wslu (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: wslu (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: wslu (Ubuntu Groovy) Importance: Undecided => Critical ** Changed in: wslu (Ubuntu Groovy) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883924 Title: Ubuntu.exe will not be detected properly if other LTS version is installed Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases when using from the Ubuntu app from Microsoft Store. When other LTS version of app is installed from Microsoft Store, baseexec generated by wslu on Ubuntu app will not be using ubuntu.exe but other LTS release apps (such as ubuntu1804.exe) [Test Case] * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store. * run any wslu tools (like wslfetch --help) * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+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 1883920] Re: ubuntu logo in wslfetch needs update
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/384608 ** Changed in: wslu (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: wslu (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: wslu (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: wslu (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: wslu (Ubuntu Groovy) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version. [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown. [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Rebuilt the package against the latest changes: https://drive.google.com/file/d/1OUkiq3Pt42_U1Pa25uIGITd4iOG7a- eI/view?usp=sharing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d
[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
** Description changed: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] - * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates - * Run the autopktest in a WSL environment where the user name contains space. - * Verify the other individual bugs fixed by the SRU. + * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution + * run any wslu tool (like wslfetch) + * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 19m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` ** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/384608 -- You received this bug notification because you are a member of Desktop Packages, wh
[Desktop-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
I've enabled proposed repository, rebooted, and can confirm my issue is resolved. I can connect to WPA2 networks! Also marked my bug from yesterday as a dup. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Committed Status in wpa source package in Groovy: Fix Released Bug description: [Impact] * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT), also called fast roaming) if it either supports SME or the NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites, wpa_supplicant currently doesn't take into account whether or not either of those conditions are met. This can cause association failures, e.g., when an AP supports both WPA-EAP and FT-EAP but the driver doesn't support FT (wpa_supplicant will decide to do FT-EAP since it is unaware the driver doesn't support it). * This is known to affect users at least users with popular chip-sets, such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15 laptops). * The upload fixes the bug by allowing an FT suite to be selected only when the driver also supports FT. [Test Case] * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R and connecting to an AP supporting WPA-EAP and FT-EAP [Regression Potential] * a driver not advertising correctly its support for SME or the NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from using FT but would still be able to connect to APs [Other Info] * Upstream fix: https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490 * Initial report: https://bugs.archlinux.org/task/63397 --- Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1881549/+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 1883924] [NEW] Ubuntu.exe will not be detected properly if other LTS version is installed
Public bug reported: [Impact] This affects all wslu tools on all releases when using from the Ubuntu app from Microsoft Store. When other LTS version of app is installed from Microsoft Store, baseexec generated by wslu on Ubuntu app will not be using ubuntu.exe but other LTS release apps (such as ubuntu1804.exe) [Test Case] * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store. * run any wslu tools (like wslfetch --help) * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe [Regression Potential] * None for now. ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Focal) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883924 Title: Ubuntu.exe will not be detected properly if other LTS version is installed Status in wslu package in Ubuntu: New Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: New Bug description: [Impact] This affects all wslu tools on all releases when using from the Ubuntu app from Microsoft Store. When other LTS version of app is installed from Microsoft Store, baseexec generated by wslu on Ubuntu app will not be using ubuntu.exe but other LTS release apps (such as ubuntu1804.exe) [Test Case] * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store. * run any wslu tools (like wslfetch --help) * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+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 1883920] [NEW] ubuntu logo in wslfetch needs update
Public bug reported: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version. [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown. [Regression Potential] * None for now. ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Focal) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Eoan) Importance: Undecided Status: New ** No longer affects: wslu (Ubuntu Eoan) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: New Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: New Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version. [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown. [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+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 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
** Merge proposal unlinked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/384608 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Committed Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Confirmed Status in wslu source package in Groovy: Fix Committed Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates * Run the autopktest in a WSL environment where the user name contains space. * Verify the other individual bugs fixed by the SRU. [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 19m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o
Re: [Desktop-packages] [Bug 1882462] Re: Displays wake up pre-maturely (likely driven by notification)
I've disabled fwupd and cups and I still see it in the morning when I come into the office. I'm inclined to shutdown boltd and see if that stops it from happening since I don't have anything plugged into the thunderbolt port at this time. -- 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/1882462 Title: Displays wake up pre-maturely (likely driven by notification) Status in gnome-shell package in Ubuntu: Confirmed Bug description: After a period of time, my displays go to sleep as they should. However, I often come back to find that the displays are awake, the mouse pointer is on a screen, but the screens are otherwise black. They're in this weird "awake but not fully on" mode. At that point, they will not go back to sleep as they should unless I fully awake them and let them go back to sleep. I don't know exactly what triggers the "half awake" but I suspect it's a notification. The displays shouldn't turn on without a user action. It wastes power and is clearly broken. I've attached a photo for an example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 16:10:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (684 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+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