[Desktop-packages] [Bug 1861391] Re: Full-screen window flickers once when switching to it
Or run: lspci -k > lspcik.txt dmesg > dmesg.txt journalctl -b0 > journal.txt dpkg -l > dpkgs.txt and then attach all four text files. -- 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/1861391 Title: Full-screen window flickers once when switching to it Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+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 1861391] Re: Full-screen window flickers once when switching to it
Hmm, that didn't collect what I expected. Please try running the command again now. ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) -- 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/1861391 Title: Full-screen window flickers once when switching to it Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+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 1861391] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1861391/+attachment/5324376/+files/ProcCpuinfoMinimal.txt -- 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/1861391 Title: Full-screen window flickers once when switching to it Status in mutter package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1861391/+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 1861391] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1861391/+attachment/5324377/+files/ProcEnviron.txt -- 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/1861391 Title: Full-screen window flickers once when switching to it Status in mutter package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1861391/+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 1861391] Re: Full-screen window flickers once when switching to it
apport information ** Tags added: apport-collected eoan ** Description changed: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. - Changes of the graphics driver does not change anything, however, - switching to Wayland solves the problem. + Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-11-16 (75 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 + Tags: eoan + Uname: Linux 5.3.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1861391/+attachment/5324375/+files/Dependencies.txt -- 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/1861391 Title: Full-screen window flickers once when switching to it Status in mutter package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1861391/+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 1851385] Re: ubuntu 19.10 / print bug : requires authentication
*** This bug is a duplicate of bug 1849859 *** https://bugs.launchpad.net/bugs/1849859 Same issue on Ubuntu 19.10 trying to access printer on samba share. Used to work on 18.04. Not obvious if related to bug #1849859, al least error message is different. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1851385 Title: ubuntu 19.10 / print bug : requires authentication Status in cups package in Ubuntu: Confirmed Bug description: Hello, I have 2 computers(one laptop and one desktop) which have a dual boot Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a USB port from my modem on which my computers are connected using Wi- Fi. Since the upgrade of Ubuntu to version 19.10, I cannot print. On both computers I get the same message : [The printer] requires authentication / credentials required in order to print. With Ubuntu 19.04, I had absolutely no problem. I tried with a live USB with Ubuntu 19.04, there is no problem, the printer works. With a Ubuntu live 19.10, it doesn't work. If I plug the printer directly on a USB port on my computer, I get the same error message : [The printer] requires authentication / credentials required in order to print. It's the same behaviour on both computers, no I guess it must be a bug. Anyway I don't know which authentication I could do, with which ID and password ? Thank you very much ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 15:12:07 2019 Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B MachineType: Acer Aspire V5-571 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571 dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: Aspire V5-571 dmi.product.name: Aspire V5-571 dmi.product.sku: Aspire V5-571_072A_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+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 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
It sounds like the Fix Released status for focal is wrong. Jonathan, can you please boot from USB and test 20.04? http://cdimage.ubuntu.com/daily-live/current/ ** Changed in: mutter (Ubuntu) Status: Fix Released => Incomplete ** Also affects: mutter (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Incomplete -- 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/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Eoan: Confirmed Status in mutter source package in Focal: Incomplete Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+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 484529] Re: When trying to play a track the error message Couldn't start playback, and Cannot resolve proxy host name appears
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/484529 Title: When trying to play a track the error message Couldn't start playback, and Cannot resolve proxy host name appears Status in rhythmbox package in Ubuntu: Expired Bug description: Binary package hint: rhythmbox When playing a song, the Error message Can't Start Playback, and Cannot resolve Proxy hostname appears. ProblemType: Bug Architecture: i386 Date: Tue Nov 17 16:23:20 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/rhythmbox NonfreeKernelModules: nvidia Package: rhythmbox 0.12.5-0ubuntu5 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: rhythmbox Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/484529/+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 509471] Re: Last.fm plugin skips tracks
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/509471 Title: Last.fm plugin skips tracks Status in rhythmbox package in Ubuntu: Expired Bug description: Binary package hint: rhythmbox While playing tracks Last.fm plugins skips some of them (~10 %) and doesn't submit information about them to the server. I'm using Ubuntu 9.10, Rhythmbox is 0.12.5-0ubuntu4 ProblemType: Bug Architecture: i386 Date: Tue Jan 19 11:19:52 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: rhythmbox 0.12.5-0ubuntu5 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: rhythmbox Uname: Linux 2.6.31-17-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/509471/+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 1309036] Re: Travou o reprodutor de música(Rhythmbox)
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1309036 Title: Travou o reprodutor de música(Rhythmbox) Status in rhythmbox package in Ubuntu: Expired Bug description: Tentei reproduzir uma música no rhythmbox e a janela parou de responder e fechou. Com sorte quando inicializo o programa ele volta a reproduzir normalmente, mas isso e chato perco tempo assim. Google translation: I tried to play a song in rhythmbox and the window stopped responding and closed. With luck when I start the program it will play back normally, but that's annoying I waste time like that. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Apr 17 11:09:44 2014 InstallationDate: Installed on 2014-04-14 (3 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True 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/1309036/+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 1046066] Re: Rhythmbox goes crazy if I change keyboard layout
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1046066 Title: Rhythmbox goes crazy if I change keyboard layout Status in rhythmbox package in Ubuntu: Expired Bug description: Description: Ubuntu 12.04.1 LTS Release: 12.04 rhythmbox: Installed: 2.96-0ubuntu4.1 Candidate: 2.96-0ubuntu4.1 Version table: *** 2.96-0ubuntu4.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 2.96-0ubuntu4 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages DESCRIPTION Not so trivial to explain but I'll try. 1. Launch Rhythmbox 2. Insert a CD in the CD-ROM 3. The CD is not automatically identified (it's of a not very famous Russian band) 4. I'm manually setting track names and... 5. Magic, black magic! If I change the keyboard layout (RU <-> EN) during editing then Rhythmbox kicks me out of the editing. So if a track name contains both Russian and English words I'm compelled to write one part, press Enter (so that the changes are not lost), change layout, click on the track name, write another part in the opposite layout. In some tricky names I have to do this several times. By the way, I use Alt+Shift to change layout. With Ctrl+Shift it works much better. Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1046066/+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 1268197] Re: UI freeze when doing import from 'Music' folder on first run
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1268197 Title: UI freeze when doing import from 'Music' folder on first run Status in Ubuntu GNOME: Expired Status in rhythmbox package in Ubuntu: Expired Bug description: UI freeze when doing import from 'Music' folder on first run. See attached screenshot. The importing progress bar just stops mid run and requires the app to be restarted to clear. The status bar is correct that all 185 tracks have been imported. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 11 20:28:10 2014 InstallationDate: Installed on 2014-01-11 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140110) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1268197/+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 1407777] Re: command line parameters are incorrect
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/140 Title: command line parameters are incorrect Status in rhythmbox package in Ubuntu: Expired Bug description: De naar dit programma verzonden parameters zijn ongeldig. Gelieve een foutenrapport in te dienen! (Parameters send to this program are incorrect. Please report bug) De parameters luiden: (Parameters are) --transient-for=69206023 gstreamer|1.0|rhythmbox|MPEG-1 Layer 3 (MP3) decoder|decoder-audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, layer=(int)3, parsed=(boolean)true 1)Ubuntu 14.04 LTS 2)rhythmbox 3.0.2-0ubuntu2 3) to play any kind of music either from URL, mp3 or so 4) all failed,but worked in teh previous version of Ubuntu 12 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: Unity Date: Mon Jan 5 20:23:17 2015 InstallationDate: Installed on 2012-12-02 (764 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) SourcePackage: rhythmbox UpgradeStatus: Upgraded to trusty on 2014-09-21 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/140/+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 1513885] Re: rhythm box crashes
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1513885 Title: rhythm box crashes Status in rhythmbox package in Ubuntu: Expired Bug description: xdiagnose is the one who found the bug, so I am unsure what kind it is or if it is valid. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27 Uname: Linux 3.13.0-67-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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: Fri Nov 6 10:38:48 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Device [14c0:0075] InstallationDate: Installed on 2015-02-25 (253 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Compal VAW70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-67-generic root=UUID=f55d1f1a-b68d-432a-bdbb-96e51cac8660 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01T01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Compal dmi.board.version: V1.01T01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: VAW70 dmi.product.version: V1.01T01 dmi.sys.vendor: Compal version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 1 19:04:01 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1479 vendor BOE xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1513885/+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 1302397] Re: Pause button from quicklist not working
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1302397 Title: Pause button from quicklist not working Status in rhythmbox package in Ubuntu: Expired Bug description: When i'm playing radio stream pause button is not working from quickist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1302397/+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 1360510] Re: rhythmbox
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1360510 Title: rhythmbox Status in rhythmbox package in Ubuntu: Expired Bug description: rhythmbox crashing when trying to import 8GB of several songs (mp3, flac, etc). External media. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1360510/+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 1302402] Re: Radio stream stops when buffer level reach 0%.
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1302402 Title: Radio stream stops when buffer level reach 0%. Status in rhythmbox package in Ubuntu: Expired Bug description: It should try to restart stream and reconnect. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 rhythmbox: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1302402/+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 1268197] Re: UI freeze when doing import from 'Music' folder on first run
[Expired for Ubuntu GNOME because there has been no activity for 60 days.] ** Changed in: ubuntu-gnome Status: Incomplete => Expired -- 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/1268197 Title: UI freeze when doing import from 'Music' folder on first run Status in Ubuntu GNOME: Expired Status in rhythmbox package in Ubuntu: Expired Bug description: UI freeze when doing import from 'Music' folder on first run. See attached screenshot. The importing progress bar just stops mid run and requires the app to be restarted to clear. The status bar is correct that all 185 tracks have been imported. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 11 20:28:10 2014 InstallationDate: Installed on 2014-01-11 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140110) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1268197/+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 1418161] Re: rhythmbox freezes. got rid of window, but kill -9 doesn't work
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1418161 Title: rhythmbox freezes. got rid of window, but kill -9 doesn't work Status in rhythmbox package in Ubuntu: Expired Bug description: rhythmbox can be pretty slow - creating playlists and changing songs. but this time it froze completely. I tried to kill the PID and it didn't work. tried also kill -9 as me and as root. no effect. X'ing the window in the GUI got rid of the window, but the process is still running. can't get rid of it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: rhythmbox 3.0.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 4 13:20:06 2015 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2014-12-05 (61 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: PATH=(custom, user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash 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/1418161/+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 1615314] Re: It struggles to start
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1615314 Title: It struggles to start Status in rhythmbox package in Ubuntu: Expired Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center rhythmbox: Installed: 3.0.2-0ubuntu2 Candidate: 3.0.2-0ubuntu2 Version table: *** 3.0.2-0ubuntu2 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen The application starts easily and quickly 4) What happened instead 4.1 As soon as starting the app, the screen greys out, as if running low on system resources. I can now rule that possibility out, because I had only just booted, I had not started any other applications, and this computer has LOADS of memory and LOADS of processing power. This 'greying out' lasts for about 30 seconds or so, and I cannot use the application at all during this time. 4.2 Also right near the end of this 'greying out' time, an error message appears, saying "The application Rhythmbox has closed unexpectedly", despite the fact that the application Rhythmbox HAS NOT closed. I attach a screenshot of the message. This bug has been occurring for more than a year, and occurs EVERY TIME that I start the application. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 21 11:24:25 2016 InstallationDate: Installed on 2014-10-14 (676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash 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/1615314/+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 1713736] Re: Rhythmbox crashes when clicking on "Play" button
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1713736 Title: Rhythmbox crashes when clicking on "Play" button Status in rhythmbox package in Ubuntu: Expired Bug description: I am using Ubuntu 14.04.5 LTS. I purged Unity because it is really slow on my PC. I installed GNOME & KDE (kubuntu-desktop). Before I logged out from KDE because it was somehow slow, Rhythmbox played the music files just fine. However, when I logged in to GNOME Flashback (Metacity), I started Rhythmbox, and when I pressed the "Play" button on my keyboard, Rhythmbox crashed instead of playing the music file normally. Can anyone help me. (Note: This only happens with Ubuntu 14.04 on my PC. Back when I was using Ubuntu 10.10 & 12.04, Rhythmbox worked OK.) Ubuntu release (lsb_release -rd): Description: Ubuntu 14.04.5 LTS Release: 14.04 Version of Rhythmbox (apt-cache policy rhythmbox): rhythmbox: Installed: 3.0.2-0ubuntu2 Candidate: 3.0.2-0ubuntu2 Release Table: *** 3.0.2-0ubuntu2 0 500 http://gr.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 0 500 http://gr.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76 Uname: Linux 4.4.0-92-generic i686 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: i386 CurrentDesktop: GNOME Flashback (Metacity) Date: Tue Aug 29 16:57:09 2017 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2017-08-27 (1 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) ProcEnviron: LANGUAGE=el PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash 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/1713736/+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 1849135] Re: Clicking Activities in the corner doesn't work
** Changed in: gnome-shell Status: Unknown => New -- 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/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mutter source package in Eoan: Confirmed Bug description: [ Impact ] Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan [ Test case ] - Move the mouse to the top-left corner pixel and click on it - Activities should open [ Regression potential ] Mouse picking location could be wrong in all clutter operations To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1849135] Re: Clicking Activities in the corner doesn't work
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2164 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164 ** Changed in: gnome-shell Status: Fix Released => Unknown ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1649 => gitlab.gnome.org/GNOME/gnome-shell/issues #2164 ** No longer affects: mutter ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed ** Changed in: mutter (Ubuntu Eoan) Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- 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/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mutter source package in Eoan: Confirmed Bug description: [ Impact ] Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan [ Test case ] - Move the mouse to the top-left corner pixel and click on it - Activities should open [ Regression potential ] Mouse picking location could be wrong in all clutter operations To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1849135] Re: Clicking Activities in the corner doesn't work
Here's the new issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2164 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164 -- 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/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Eoan: Incomplete Bug description: [ Impact ] Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan [ Test case ] - Move the mouse to the top-left corner pixel and click on it - Activities should open [ Regression potential ] Mouse picking location could be wrong in all clutter operations To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1861307] Re: [HP Laptop 14-bs0xx][HDA-Intel - HDA Intel PCH, playback] No sound at all
** Summary changed: - [HDA-Intel - HDA Intel PCH, playback] No sound at all + [HP Laptop 14-bs0xx][HDA-Intel - HDA Intel PCH, playback] No sound at all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1861307 Title: [HP Laptop 14-bs0xx][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound at all in ubuntu 16.4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andre 1507 F...m pulseaudio /dev/snd/pcmC0D0p: andre 1507 F...m pulseaudio /dev/snd/controlC0: andre 1507 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 11:18:59 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-atami161222-xenial-amd64-20170321-0 InstallationDate: Installed on 2019-05-16 (258 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170321-07:27 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andre 1507 F...m pulseaudio /dev/snd/pcmC0D0p: andre 1507 F...m pulseaudio /dev/snd/controlC0: andre 1507 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 831E dmi.board.vendor: HP dmi.board.version: 17.42 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.44:bd12/13/2018:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn831E:rvr17.42:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Laptop 14-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861307/+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 1861043] Re: GUI frozen when memory was exhausted
** Summary changed: - [nvidia] System freeze + GUI frozen when memory was exhausted ** Package changed: ubuntu => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Summary changed: - GUI frozen when memory was exhausted + GUI frozen when memory was exhausted (by non-GUI processes) ** Tags removed: has-fix has-workaround -- 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/1861043 Title: GUI frozen when memory was exhausted (by non-GUI processes) Status in gnome-shell package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 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/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Po
[Desktop-packages] [Bug 1861079] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
Yeah it's not obvious but buggy gnome-shell extensions can still cause problems even when disabled. They need to be uninstalled. It sounds like that is working well so far... As for the CPU usage, that's not related to this bug so should be discussed elsewhere. I think that's a general problem with compositing software-rendered apps as GTK apps are. Bug 1773502 covers 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/1861079 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: I can confirm the issue described in Bug #1827791 is existent in Ubuntu 18.04 LTS as well. When I issue the command "sudo swapoff /swapfile" the issue never shows up. I always issue that command as the laptop otherwise is barely usable and I need to use it for work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Uname: Linux 4.15.0-1066-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 09:14:31 2020 DisplayManager: gdm3 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-20180608-47+italia-whl+X31 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com', 'move_cl...@rmy.pobox.com', 'no-title-...@franglais125.gmail.com', 'gsconn...@andyholmes.github.io']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-01-29 (364 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash 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/1861079/+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 1860907] Re: gnome-shell crashes when using touchscreen
Thanks, but those instructions also say: > 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. I have looked inside your crash file and this is certainly true. So please run: ubuntu-bug /path/to/your/file.crash -- 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/1860907 Title: gnome-shell crashes when using touchscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+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 1849135] Re: Clicking Activities in the corner doesn't work
I'll create the new issue there. I have only one monitor. -- 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/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Eoan: Incomplete Bug description: [ Impact ] Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan [ Test case ] - Move the mouse to the top-left corner pixel and click on it - Activities should open [ Regression potential ] Mouse picking location could be wrong in all clutter operations To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1861043] [NEW] GUI frozen when memory was exhausted
You have been subscribed to a public bug: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 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/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: gnome-shell (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug focal freeze has-fix has-workaround nvidia ubuntu -- GUI frozen when memory was exhausted https://bugs.launchpad.net/bugs/1861043 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
The simplest first test would be to try booting Ubuntu 20.04 from USB: http://cdimage.ubuntu.com/daily-live/current/ -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Most likely this is a kernel bug so the next step would be to try some newer or older kernels and see if any of them DO NOT have the same bug. Then hopefully we can identify when things changed. https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1854672] Re: On print dialog, add "Manual" option to "Two-sided". Print odd pages first, then display message to remove and reinsert pages, then horizontally rotate and print e
Maybe gnome-manual-duplex could be integrated into Ubuntu, or it could be added to the Ubuntu repository and a user could be prompted to install it, if the user selects manual two sided. https://sourceforge.net/projects/g-manual-duplex/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1854672 Title: On print dialog, add "Manual" option to "Two-sided". Print odd pages first, then display message to remove and reinsert pages, then horizontally rotate and print even numbered pages in descending order. Status in system-config-printer package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) system-config-printer 1.5.11 3) Inability to manually print on both side of paper. 4) Ability to manually print on both side of paper. If print page count is 1, then do not display a message to remove and reinsert page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1854672/+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 1860540] Re: network password entry has no way of displaying what you type
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1022 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Tags added: fixed-in-3.35.3 fixed-upstream ** Summary changed: - network password entry has no way of displaying what you type + Password entry has no way of displaying what you type -- 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/1860540 Title: Password entry has no way of displaying what you type Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In Focal the network password / passphrase entry form has no way of displaying what is being typed. I'd expect a checkbox or something... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.442 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CasperVersion: 1.438 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 11:13:41 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1860540/+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 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
Great, thanks! ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Jarno Suni (jarnos) ** Tags added: fixed-in-14.0 fixed-upstream -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Triaged Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ Only pulseaudio is a regular file; other ones are symbolic links, so it is enough to modify the first one. gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1200 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio /dev/snd/controlC0: jarnos 1200 F pulseaudio /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857708/+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 1849135] Re: Clicking Activities in the corner doesn't work
Those still experiencing problems: Do you use multiple monitors or have a single screen? ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Incomplete ** Changed in: mutter (Ubuntu) Status: Triaged => Incomplete ** Changed in: mutter (Ubuntu Eoan) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Eoan: Incomplete Bug description: [ Impact ] Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan [ Test case ] - Move the mouse to the top-left corner pixel and click on it - Activities should open [ Regression potential ] Mouse picking location could be wrong in all clutter operations To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1849135] Re: Clicking Activities in the corner doesn't work
To move this bug forward, someone still experiencing problems should please open a new upstream issue at: https://gitlab.gnome.org/GNOME/gnome-shell/issues and tell them that it's different to the current upstream bugs we have (which are definitely fixed and closed): https://gitlab.gnome.org/GNOME/mutter/issues/893 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 -- 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/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Eoan: Incomplete Bug description: [ Impact ] Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan [ Test case ] - Move the mouse to the top-left corner pixel and click on it - Activities should open [ Regression potential ] Mouse picking location could be wrong in all clutter operations To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1776447] Re: Xorg's Indirect GLX broken from upstream regression
Great to hear. I don't have any power to help get this released sooner. It looks like you've done everything right for an SRU, and Timo (who handles Xorg) is already aware of it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: [Impact] * IGLX is a way for an opengl application sending the 3D drawing GLX commands to the Xorg server for rendering instead of using the DRI infrastructure it is commonplace for High Performance Compute and Scientific institutions to use this feature of the Xorg server. (ref: https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX- Potential-Bye-Bye) * The feature is completely broken, currently, and any attempt to use it will cause the Xorg server to crash. This feature has been broken since a commit upstream in 2016. * The attached patch is from the revert commit entered into the upstream repository on 28 Jan 2020 following a git bisect of the bug discovering the offending commit. [Test Case] * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the following contents: ``` Section "ServerFlags" Option "IndirectGLX" "on" EndSection ``` * Log out of your Xorg session * Switch to a VT (Ctrl+Alt+F2) and login * Run `sudo systemctl restart gdm` to restart Xorg * Login to the graphical session * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils` * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears` * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting [Regression Potential] * This change is within DRI-related functionality and so might break all 3D accelerated applications. * There is a potential that the change is insufficient to fix the IGLX feature and so attempts to use it may still have undesirable and undefined results. * Upstream has run the patch through their CI system, which passed with no errors. This does not necessarily mean the patch will achieve the desired results, but at least indicates that the code does compile cleanly and can start an Xvfb headless instance. [Other Info] * This bug affects Ubuntu releases all the way back to, and including, Bionic 18.04. Original Bug Report Follows There's already an upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=99555 Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear: steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: 255 Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 1 (X_GLXRender) Serial number of failed request: 42 Current serial number in output stream: 936 I am trying to run what is effectively a traditional X Terminal, but as the hardware I am using has a 3D accelerated chipset it seems sensible to try to use it.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Jun 12 10:09:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2018-05-31 (11 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: AZW S I ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 00.12 dmi.board.asset.tag: Default string dmi.board.name: AB1 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35
[Desktop-packages] [Bug 1854672] Re: In printer settings, add "Manual Double Sided". Print odd pages first, then display message to remove and reinsert pages, then horizontally rotate and print even n
Could you add the following options to "Two-sided": "Off", "Automatic", and "Manual". The "Automatic" option could be removed, if the printer does not support automatic two sided printing. ** Attachment added: "Print_Dialog.png" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1854672/+attachment/5324322/+files/Print_Dialog.png ** Summary changed: - In printer settings, add "Manual Double Sided". Print odd pages first, then display message to remove and reinsert pages, then horizontally rotate and print even numbered pages in descending order. + On print dialog, add "Manual" option to "Two-sided". Print odd pages first, then display message to remove and reinsert pages, then horizontally rotate and print even numbered pages in descending order. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1854672 Title: On print dialog, add "Manual" option to "Two-sided". Print odd pages first, then display message to remove and reinsert pages, then horizontally rotate and print even numbered pages in descending order. Status in system-config-printer package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) system-config-printer 1.5.11 3) Inability to manually print on both side of paper. 4) Ability to manually print on both side of paper. If print page count is 1, then do not display a message to remove and reinsert page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1854672/+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 1861391] Re: Full-screen window flickers once when switching to it
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1861391 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1861391 Title: Full-screen window flickers once when switching to it Status in mutter package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1861391/+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 1741768] Re: U2F FIDO authentication doesn't work
Tested this today, via the github site, and both authentication and the
registration of a new key fails. Logging I can find related to this in
/var/log/syslog is:
Jan 31 09:53:13 hyperion kernel: [605631.650563] audit: type=1400
audit(1580428393.744:1863): apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/sys/devices/virtual/misc/uhid/0005:046D:B01D.0013/hidraw/hidraw6/uevent"
pid=25081 comm=4950444C204261636B67726F756E64 requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
--
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/1741768
Title:
U2F FIDO authentication doesn't work
Status in firefox package in Ubuntu:
Confirmed
Bug description:
I have a Yubico U2F security key. If I download the upstream Firefox
binary for 57.0.4 and go to https://demo.yubico.com/u2f?tab=register,
the test page works fine: I can register with a username/password, my
key starts blinking and I can touch it to validate.
If I go to the same page using the official Ubuntu package of Firefox,
the U2F device is not recognized and the page displays the following
error:
"""
Registration failed!
Make sure you have a U2F device connected, and try again.
Traceback (most recent call last):
File "/root/python-u2flib-server-demo/examples/yubiauth_server.py", line
161, in __call__
raise Exception("FIDO Client error: %s" % error)
Exception: FIDO Client error: 1 (OTHER ERROR)
"""
Note that in both cases, I did enable the required options in
"about:config" (as outlined in e.g. https://www.yubico.com/2017/11
/how-to-navigate-fido-u2f-in-firefox-quantum/).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 57.0.4+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-21.24~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm
nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: antoine3844 F pulseaudio
/dev/snd/controlC1: antoine3844 F pulseaudio
BuildID: 20180104112904
Channel: Unavailable
CurrentDesktop: XFCE
Date: Sun Jan 7 17:32:38 2018
DefaultProfileIncompatibleExtensions: Default -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: 'utf-8' codec can't decode byte 0xe9 in position
2410: invalid continuation byte
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-12 (1730 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409)
MostRecentCrashID: bp-eb109c63-e3b5-4c21-a920-d262b2150407
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
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
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
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
Profile4PrefSources: prefs.js
Profile4Themes: extensions.sqlite corrupt or missing
Profiles:
Profile0 (Default) - LastVersion=57.0.4/20180104112904 (In use)
Profile1 - LastVersion=57.0.4/20180104112904
Profile2 - LastVersion=57.0.4/20180104112904
Profile3 - LastVersion=57.0.3/20171227151400 (Out of date)
Profile4 - LastVersion=57.0.4/20180104112904 (In use)
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to xenial on 2015-07-27 (894 days ago)
dmi.bios.date: 06/22/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M EVO
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
dm
[Desktop-packages] [Bug 1859750] Re: "Out of Paper" message is NOT displayed.
Reported to foo2zjs developer: http://foo2zjs.rkkda.com/forum/read.php?7,4343 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1859750 Title: "Out of Paper" message is NOT displayed. Status in system-config-printer package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) system-config-printer 1.5.11 3) system-config-printer detected my HP Laserjet 1020. I printed a page, and it was added to the print queue. The page did not print and the print job disappeared from the print queue. I downloaded foo2zjs.tar.gz from http://foo2zjs.rkkda.com/ and followed the instructions. I was able to get my printer to successfully print pages. When my HP Laserjet 1020 is out of paper. The green light on the printer changes to a blinking orange light. An "Out of Paper" message with a retry button, should have been displayed. 4) An "Out of Paper" message with a retry button, was NOT displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1859750/+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 1859750] Re: "Out of Paper" message is NOT displayed.
Reported to foo2zjs developer: http://foo2zjs.rkkda.com/forum/read.php?7,4342 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1859750 Title: "Out of Paper" message is NOT displayed. Status in system-config-printer package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) system-config-printer 1.5.11 3) system-config-printer detected my HP Laserjet 1020. I printed a page, and it was added to the print queue. The page did not print and the print job disappeared from the print queue. I downloaded foo2zjs.tar.gz from http://foo2zjs.rkkda.com/ and followed the instructions. I was able to get my printer to successfully print pages. When my HP Laserjet 1020 is out of paper. The green light on the printer changes to a blinking orange light. An "Out of Paper" message with a retry button, should have been displayed. 4) An "Out of Paper" message with a retry button, was NOT displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1859750/+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 1854672] Re: In printer settings, add "Manual Double Sided". Print odd pages first, then display message to remove and reinsert pages, then horizontally rotate and print even n
Reported to foo2zjs developer: http://foo2zjs.rkkda.com/forum/read.php?7,4343 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1854672 Title: In printer settings, add "Manual Double Sided". Print odd pages first, then display message to remove and reinsert pages, then horizontally rotate and print even numbered pages in descending order. Status in system-config-printer package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) system-config-printer 1.5.11 3) Inability to manually print on both side of paper. 4) Ability to manually print on both side of paper. If print page count is 1, then do not display a message to remove and reinsert page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1854672/+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 1741768] Re: U2F FIDO authentication doesn't work
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
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/1741768
Title:
U2F FIDO authentication doesn't work
Status in firefox package in Ubuntu:
Confirmed
Bug description:
I have a Yubico U2F security key. If I download the upstream Firefox
binary for 57.0.4 and go to https://demo.yubico.com/u2f?tab=register,
the test page works fine: I can register with a username/password, my
key starts blinking and I can touch it to validate.
If I go to the same page using the official Ubuntu package of Firefox,
the U2F device is not recognized and the page displays the following
error:
"""
Registration failed!
Make sure you have a U2F device connected, and try again.
Traceback (most recent call last):
File "/root/python-u2flib-server-demo/examples/yubiauth_server.py", line
161, in __call__
raise Exception("FIDO Client error: %s" % error)
Exception: FIDO Client error: 1 (OTHER ERROR)
"""
Note that in both cases, I did enable the required options in
"about:config" (as outlined in e.g. https://www.yubico.com/2017/11
/how-to-navigate-fido-u2f-in-firefox-quantum/).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 57.0.4+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-21.24~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm
nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: antoine3844 F pulseaudio
/dev/snd/controlC1: antoine3844 F pulseaudio
BuildID: 20180104112904
Channel: Unavailable
CurrentDesktop: XFCE
Date: Sun Jan 7 17:32:38 2018
DefaultProfileIncompatibleExtensions: Default -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: 'utf-8' codec can't decode byte 0xe9 in position
2410: invalid continuation byte
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-12 (1730 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409)
MostRecentCrashID: bp-eb109c63-e3b5-4c21-a920-d262b2150407
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
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
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
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
Profile4PrefSources: prefs.js
Profile4Themes: extensions.sqlite corrupt or missing
Profiles:
Profile0 (Default) - LastVersion=57.0.4/20180104112904 (In use)
Profile1 - LastVersion=57.0.4/20180104112904
Profile2 - LastVersion=57.0.4/20180104112904
Profile3 - LastVersion=57.0.3/20171227151400 (Out of date)
Profile4 - LastVersion=57.0.4/20180104112904 (In use)
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to xenial on 2015-07-27 (894 days ago)
dmi.bios.date: 06/22/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M EVO
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.:bvr1801:bd06/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.s
[Desktop-packages] [Bug 1846988] Re: [Audio playback] No 'Speaker - Built-in Audio'
Hi there, the same device currently has ubuntu 19.10 and I have updates installed every 2-3 days. This is still an issue for my device, and currently I use a duel boot of windows to get audio (works fine) I intend to update to major releases when they drop (ie 20.04) when they become available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846988 Title: [Audio playback] No 'Speaker - Built-in Audio' Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Installation details: Ubuntu 19.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Expected a 'Speaker - Built-in Audio' option in my Audio settings. Actual behaviour: Seems the 'Speakers - Built-in Audio' playback device is not available in my settings. Instead there is 'Headphones - Built-in Audio' which obviously shouldn't exist. When actual headphones are attached, the do not playback either. Playback only works when connected via bluetooth or HDMI, but there are extra options, that do not work... not sure what it is detecting, as there is only one HDMI output. I followed this document to debug myself: https://help.ubuntu.com/community/SoundTroubleshooting. However, the second step works fine when connected via bluetooth or HDMI, as stated before. I have tried booting the Live USB, and audio works perfectly fine here, so this is not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer /dev/snd/pcmC0D0c: lawrence 2033 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 09:27:18 2019 InstallationDate: Installed on 2019-09-07 (29 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TMB dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: IT Channel Pty Ltd dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: IT Channel Pty Ltd dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TMB:bd04/10/2019:svnITChannelPtyLtd:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnITChannelPtyLtd:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnITChannelPtyLtd:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: IT Channel Pty Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-07T11:50:26.934452 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846988/+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 1861409] Re: searching for irc takes more than 10 minutes
Thanks Sergio. Was it a one time issue or can you reproduce? Could you attach the journalctl log from around the time where you hit the problem? (oh, also I'm fixing the typo in the tag ;-) ** Tags removed: champange ** Tags added: champagne -- 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/1861409 Title: searching for irc takes more than 10 minutes Status in gnome-software package in Ubuntu: New Bug description: A fresh install, searching for IRC and still waiting for the results after 10 minutes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.34.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 10:58:56 2020 InstallationDate: Installed on 2020-01-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.34.2-1ubuntu1 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/1861409/+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 1860907] Re: gnome-shell crashes when using touchscreen
Thanks for the guidance, Daniel I have uninstalled the extensions, rebooted, and was still able to reproduce the crash. I have uploaded the .crash file per the instructions you linked. Please let me know if there's anything else I can do to aid in the investigation. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+attachment/5324291/+files/_usr_bin_gnome-shell.1000.crash -- 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/1860907 Title: gnome-shell crashes when using touchscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+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 1861453] [NEW] The chromium-browser snap package fails to run
Public bug reported: Xubuntu 19.10 chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 Transitional package - chromium-browser -> chromium snap Chromium worked fine before the upgrade to 19.10. There has been a transition to snap packaging. My first attempt to launch the browser results in: % chromium-browser 2020/01/30 11:12:47.911841 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/x/u/jeff/.Xauthority" cannot perform operation: mount --rbind /home /tmp/snap.rootfs_MDsNgD//home: Permission denied % dmesg | grep DENIED (just showing one typical message) [827635.380132] audit: type=1400 audit(1580411567.940:87): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/snap/core/8268/usr/lib/snapd/snap-confine" name="/tmp/snap.rootfs_MDsNgD/home/" pid=2968 comm="snap-confine" srcname="/x/u/" flags="rw, rbind" The home directory is: /u/jeff The home directory is actually resides on an external drive mounted on /x with /u being a symlink to /x/u % cd / % ls -l home u lrwxrwxrwx 1 root root 1 Jan 2 2015 home -> u lrwxrwxrwx 1 root root 3 Nov 30 2017 u -> x/u %echo $XAUTHORITY /u/jeff/.Xauthority Applications should not care about these sorts of mounts and linkages, but they now appear to be very sensitive to them. What needs to be done to make this work? BTW, I think this move to SNAP is a disaster and completely the wrong way to go. Let's please stick with a single .deb packaging strategy which has proven itself. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: 19.10 chromium snap xubuntu -- 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/1861453 Title: The chromium-browser snap package fails to run Status in chromium-browser package in Ubuntu: New Bug description: Xubuntu 19.10 chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 Transitional package - chromium-browser -> chromium snap Chromium worked fine before the upgrade to 19.10. There has been a transition to snap packaging. My first attempt to launch the browser results in: % chromium-browser 2020/01/30 11:12:47.911841 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/x/u/jeff/.Xauthority" cannot perform operation: mount --rbind /home /tmp/snap.rootfs_MDsNgD//home: Permission denied % dmesg | grep DENIED (just showing one typical message) [827635.380132] audit: type=1400 audit(1580411567.940:87): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/snap/core/8268/usr/lib/snapd/snap-confine" name="/tmp/snap.rootfs_MDsNgD/home/" pid=2968 comm="snap-confine" srcname="/x/u/" flags="rw, rbind" The home directory is: /u/jeff The home directory is actually resides on an external drive mounted on /x with /u being a symlink to /x/u % cd / % ls -l home u lrwxrwxrwx 1 root root 1 Jan 2 2015 home -> u lrwxrwxrwx 1 root root 3 Nov 30 2017 u -> x/u %echo $XAUTHORITY /u/jeff/.Xauthority Applications should not care about these sorts of mounts and linkages, but they now appear to be very sensitive to them. What needs to be done to make this work? BTW, I think this move to SNAP is a disaster and completely the wrong way to go. Let's please stick with a single .deb packaging strategy which has proven itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1861453/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
> 3. mtr ping test > --- > GoodSystem..0.0% Loss; 0.2 Avg; 0.1 Best, 0.9 Worst, 0.1 StdDev > BadSystem2...11.7% Loss; 0.1 Avg; 0.1 Best, 0.2 Worst, 0.0 StdDev The mtr packet loss is an interesting result. What mtr options did you use? Is this a UDP or ICMP test? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware
[Desktop-packages] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
both changes are now in upstream Xorg's repository, as PR388 was merged a few hours ago. So the changes in this debdiff are a backport of those to Bionic, Eoan and Focal (although if Focal were to sync with the upstream code then the delta won't be necessary going forward). -- 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/1776447 Title: Xorg's Indirect GLX broken from upstream regression Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: [Impact] * IGLX is a way for an opengl application sending the 3D drawing GLX commands to the Xorg server for rendering instead of using the DRI infrastructure it is commonplace for High Performance Compute and Scientific institutions to use this feature of the Xorg server. (ref: https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX- Potential-Bye-Bye) * The feature is completely broken, currently, and any attempt to use it will cause the Xorg server to crash. This feature has been broken since a commit upstream in 2016. * The attached patch is from the revert commit entered into the upstream repository on 28 Jan 2020 following a git bisect of the bug discovering the offending commit. [Test Case] * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the following contents: ``` Section "ServerFlags" Option "IndirectGLX" "on" EndSection ``` * Log out of your Xorg session * Switch to a VT (Ctrl+Alt+F2) and login * Run `sudo systemctl restart gdm` to restart Xorg * Login to the graphical session * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils` * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears` * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting [Regression Potential] * This change is within DRI-related functionality and so might break all 3D accelerated applications. * There is a potential that the change is insufficient to fix the IGLX feature and so attempts to use it may still have undesirable and undefined results. * Upstream has run the patch through their CI system, which passed with no errors. This does not necessarily mean the patch will achieve the desired results, but at least indicates that the code does compile cleanly and can start an Xvfb headless instance. [Other Info] * This bug affects Ubuntu releases all the way back to, and including, Bionic 18.04. Original Bug Report Follows There's already an upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=99555 Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear: steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: 255 Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 1 (X_GLXRender) Serial number of failed request: 42 Current serial number in output stream: 936 I am trying to run what is effectively a traditional X Terminal, but as the hardware I am using has a 3D accelerated chipset it seems sensible to try to use it.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Jun 12 10:09:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2018-05-31 (11 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: AZW S I ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 00.12 dmi.board.asset.tag: Default string dmi.board.name: AB1 dmi.board.vendor: IP3 Tech dm
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
With respect to one of these situations, this is the following system: > Dell PowerEdge R440/0XP8V5, BIOS 2.2.11 06/14/2019 > > Note that a similar system does not have any issues: > > Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.3.4 11/08/2016 > > So the NIC in the "bad" environment is: > > BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) > Product Name: Broadcom Adv. Dual 10G SFP+ Ethernet > > The NIC in the "good" environment is: > > Broadcom Inc. and subsidiaries NetXtreme II BCM57810 > 10 Gigabit Ethernet [14e4:1006] > Product Name: QLogic 57810 10 Gigabit Ethernet There are more than one variable at play here. Does the problem follow the NIC if you swap the NICs between systems? Are OS / kernel and driver versions the same on both systems? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In th
[Desktop-packages] [Bug 1860137] Re: Chromium-browser Snap is amnesiac
I enabled the flag, still encountered this issue. This time when I restarted Chromium my tabs were lost and restoring previous session just did nothing. Thankfully the extension "Tab Suspender" allowed me to recover my tabs but a few services logged me off. I guess the flag improves situation, thanks for that, but isn't flawless. -- 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/1860137 Title: Chromium-browser Snap is amnesiac Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 19.10, latest Chromium(-browser) installed. The issue is that after the switch to snap-based Chromium it started forgetting my logged in sessions very very often. This is not isolated to one online service, I have to log back in to everything I use, including Chromium itself. It also forgets any "Remember this device" checkmarks. History, downloads or extensions however do not suffer from any data loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860137/+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 1861322] Re: PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing
Hi Seb It seems I can't reproduce the problem any more. I now can clearly see nf_conntrack_pptp loading when I try to establish PPTP connection in NM. I have no idea how this changed. Thank you for looking into it, I'll close the bug and reopen it occurs again. ** Changed in: network-manager-pptp (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1861322 Title: PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing Status in network-manager-pptp package in Ubuntu: Invalid Bug description: PPTP based VPN doesn't work out of the box on Focal Fossa. From syslog: Jan 29 19:41:35 thinkpad pppd[8734]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:41:35 thinkpad NetworkManager[8734]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:41:35 thinkpad pptp[8739]: nm-pptp-service-8722 log[main:pptp.c:353]: The synchronous pptp option is NOT activated Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request' Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 'Outgoing-Call-Request' Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 44616, peer's call ID 0). Jan 29 19:42:03 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:976]: Call disconnect notification received (call id 44616) Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[logecho:pptp_ctrl.c:719]: Echo Request received. Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 6 'Echo-Reply' Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722 warn[decaps_hdlc:pptp_gre.c:226]: short read (-1): Input/output error Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722 warn[decaps_hdlc:pptp_gre.c:238]: pppd may have shutdown, see pppd log Jan 29 19:42:06 thinkpad pppd[8734]: Child process /usr/sbin/pptp 161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722 (pid 8737) terminated with signal 15 Jan 29 19:42:06 thinkpad NetworkManager[8734]: Child process /usr/sbin/pptp 161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722 (pid 8737) terminated with signal 15 Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled) Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 12 'Call-Clear-Request' Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[call_callback:pptp_callmgr.c:84]: Closing connection (call state) Once nf_conntrack_pptp kernel module is loaded, VPN connection succeeds: Jan 29 19:44:02 thinkpad pppd[10166]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:44:02 thinkpad NetworkManager[10166]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:44:02 thinkpad pptp[10170]: nm-pptp-service-10156 log[main:pptp.c:353]: The synchronous pptp option is NOT activated Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request' Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 'Outgoing-Call-Request' Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 61223, peer's call ID 0). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1861322/+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.ne
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Here is the Ettus benchmark tool https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio You would need an Ettus device to run those tests. I cant test the affected node now as it is in production unfortunately. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the trou
[Desktop-packages] [Bug 1855009] Re: autopkgtests all fail on s390x
autopkgtests are now all skipped on s390. ** Tags removed: verification-needed ** Tags added: verification-done-eoan ** Tags removed: verification-needed-eoan -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386
eoan i386 autopkgtest skips urfkill tests, and all other tests pass. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/i386/n/network- manager/20200130_131800_17227@/log.gz ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+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 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
** Changed in: mutter Status: Unknown => New -- 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/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Confirmed Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
I have accepted nvidia-settings for bionic, but let's keep an eye out for any eventual breakages of reverse-dependencies of libxnvctrl0. This SRU dropped the (minor) NV_ID symbol without bumping the SONAME - Alberto asserts that it is highly unlikely to cause any problems, but just in case let's at least give a spin to these packages: $ reverse-depends libxnvctrl0 Reverse-Depends === * conky-all [amd64] * indicator-sensors [amd64 arm64 armhf ppc64el s390x] * libhwloc-plugins * libmyth [amd64 arm64 armhf ppc64el s390x] * libxnvctrl-dev * mate-sensors-applet-nvidia [amd64 armhf] * nvidia-settings [amd64 arm64 armhf i386 ppc64el] * psensor [amd64] * xfce4-sensors-plugin [amd64 arm64 armhf ppc64el s390x] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: In Progress Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen"
[Desktop-packages] [Bug 1860522] Re: Mesa 19.2.8 stable release
verified mesa on bionic, T470s with intel GPU ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Released Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Hello Alberto, or anyone else affected, Accepted nvidia-settings into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- settings/440.44-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-settings (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: In Progress Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to col
[Desktop-packages] [Bug 1860540] Re: network password entry has no way of displaying what you type
Thank you for the bug report, you should be able to find an item to show the password in the right click menu, that's not obvious though which is reported upstream on https://gitlab.gnome.org/GNOME/gnome- shell/issues/1022 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1022 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1022 ** Package changed: ubuntu-meta (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1860540 Title: network password entry has no way of displaying what you type Status in gnome-shell package in Ubuntu: New Bug description: In Focal the network password / passphrase entry form has no way of displaying what is being typed. I'd expect a checkbox or something... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.442 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CasperVersion: 1.438 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 11:13:41 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta 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/1860540/+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 1860540] [NEW] network password entry has no way of displaying what you type
You have been subscribed to a public bug: In Focal the network password / passphrase entry form has no way of displaying what is being typed. I'd expect a checkbox or something... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.442 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CasperVersion: 1.438 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 11:13:41 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug champagne focal -- network password entry has no way of displaying what you type https://bugs.launchpad.net/bugs/1860540 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647059] Re: On screen keyboard partially clipped or completely off screen
This bug is still present in 18.04 LTS. The steps are the same. The startup application workaround #2 in the OP works only temporarily as the permissions on /var/lib/lightdm/.config/dconf/user get reset and the workaround fails. Switching from lightdm to gdm3 gives you an ugly primitive on screen keyboard but at least they get the coordinates right. This page explains how to switch display manager. https://www.linuxuprising.com/2018/12/how-to-change-default-display- manager.html If you do this on a laptop with an external monitor you will probably run into gdm bug: https://gitlab.gnome.org/GNOME/gdm/issues/372 To get the gdm3 login screen to appear on the proper monitor I used the accepted solution by Aravind here: https://askubuntu.com/questions/1043337/ubuntu-18-04-login-screen- display-settings ** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #372 https://gitlab.gnome.org/GNOME/gdm/issues/372 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1647059 Title: On screen keyboard partially clipped or completely off screen Status in unity-greeter package in Ubuntu: New Bug description: The on screen keyboard is too low and partially clipped or completely off the bottom of the screen. On a laptop with a 2000 pixel high built-in screen with the lid closed and connected to a 1080p hdmi tv. The built-in screen is turned off in the display settings in case that's relevant. Replication steps 1) Turn on the on screen keyboard and log in using it 2) Logout or reboot 3) Lightdm remembers that the on screen keyboard is on and tries to display it = Lightdm displays the on screen keyboard using the size of the unused 2000 pixel high screen for alignment instead of the 1080 high screen in use. Only the top of the keyboard is visible at the bottom of the screen. If lightdm is configured to use 720p then the on screen keyboard is completely clipped and invisible. The problem only occurs when lightdm remembers that the on screen keyboard is on. Turning it on manually correctly displays it at the bottom of the screen. Toggling a misplaced keyboard off and back on unfortunately doesn't fix the problem. Workaround 1 When logging in, after typing password, turn off the on screen keyboard and click the small login arrow instead of clicking the on screen enter key. Each time logging in you'll need to turn the on screen keyboard on and off again. Turning off an invisible/clipped keyboard and rebooting will temporarily fix the problem. Workaround 2 Dangerous hack. Run a script to turn off the on screen keyboard in lightdm's dconf database. To make this script run as a startup application the sudo commands need to be removed and the lightdm group membership given to the user running it as well as r/w access to /var/lib/lightdm/.config/dconf/user. #!/bin/bash sudo cp /var/lib/lightdm/.config/dconf/user ~/.config/dconf/lightdm printf %s\\n "user-db:lightdm" > ~/db_profile_lightdm export ONSCREEN_KBD=$(DCONF_PROFILE=~/db_profile_lightdm dconf read /com/canonical/unity-greeter/onscreen-keyboard) #echo 'ONSCREEN_KBD=' $ONSCREEN_KBD if [ "$ONSCREEN_KBD" != "false" ]; then DCONF_PROFILE=~/db_profile_lightdm dconf write /com/canonical/unity-greeter/onscreen-keyboard false sudo cp ~/.config/dconf/lightdm /var/lib/lightdm/.config/dconf/user fi rm -f ~/db_profile_lightdm ~/.config/dconf/lightdm exit 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 3 09:16:31 2016 InstallationDate: Installed on 2014-07-09 (877 days ago) InstallationMedia: sonar 13.10 - Release amd64 SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-07-09 (877 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1647059/+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 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
** Changed in: mutter (Ubuntu Eoan) Status: Fix Committed => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1023 https://gitlab.gnome.org/GNOME/mutter/issues/1023 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/1023 Importance: Unknown Status: Unknown -- 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/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Confirmed Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Daniel, What should I do for this issue? -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1861409] [NEW] searching for irc takes more than 10 minutes
Public bug reported: A fresh install, searching for IRC and still waiting for the results after 10 minutes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.34.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 10:58:56 2020 InstallationDate: Installed on 2020-01-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.34.2-1ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champange focal ** Tags added: champange -- 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/1861409 Title: searching for irc takes more than 10 minutes Status in gnome-software package in Ubuntu: New Bug description: A fresh install, searching for IRC and still waiting for the results after 10 minutes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.34.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 10:58:56 2020 InstallationDate: Installed on 2020-01-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.34.2-1ubuntu1 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/1861409/+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 1861408] [NEW] firefox apparmor messages
Public bug reported:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5525.077960]
audit: type=1400 audit(1580226276.440:27): apparmor="DENIED"
operation="capable" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
pid=15948 comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5526.471731]
audit: type=1107 audit(1580226277.832:28): pid=735 uid=103
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5536.783313]
audit: type=1107 audit(1580226288.143:34): pid=735 uid=103
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send"
name=":1.120" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}"
peer_pid=16177 peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel: [10131.880788]
audit: type=1400 audit(1580237490.777:123): apparmor="DENIED"
operation="open" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
ouid=1000
these appeared while saving a file:
Jan 30 11:08:28 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1151]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=1584
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1301
peer_label="unconfined"
Jan 30 11:08:28 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 464.049675]
audit: type=1400 audit(1580371708.871:38): apparmor="DENIED"
operation="open" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.local/share/gvfs-metadata/
[Desktop-packages] [Bug 1861079] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
Ok, I tried this and I am now running the laptop for about 2 days (including putting it to sleep). Only disabling those extensions did not help when I tried before. Uninstalling those extensions prevents the unworkable behavior but I do not think it solves the root cause. At this moment I am seeing the following CPU usage in top: * Xorg: about 25% * gnome-shell: between 15% and 20% * nautilus: between 15% and 20% CPU usage keeps this high even during typing this comment. All other processes are below 5%, most even less than 1%. This seems to be very high for an almost idle system. Maybe this high CPU usage triggers a problem with the swap file when the extensions are enabled? Solution for the high CPU usage: closing Nautilus makes both Xorg and gnome-shell to drop to normal levels. -- 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/1861079 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: I can confirm the issue described in Bug #1827791 is existent in Ubuntu 18.04 LTS as well. When I issue the command "sudo swapoff /swapfile" the issue never shows up. I always issue that command as the laptop otherwise is barely usable and I need to use it for work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Uname: Linux 4.15.0-1066-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 09:14:31 2020 DisplayManager: gdm3 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-20180608-47+italia-whl+X31 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com', 'move_cl...@rmy.pobox.com', 'no-title-...@franglais125.gmail.com', 'gsconn...@andyholmes.github.io']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-01-29 (364 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash 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/1861079/+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 1861391] Re: Full-screen window flickers once when switching to it
I am not sure whether it is really the gnome-shell that it responsible. However, it happens with more than one application (Emacs and the terminal window), and I can exclude the graphics driver. ** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1861391 Title: Full-screen window flickers once when switching to it Status in gnome-shell package in Ubuntu: New Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+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 1861391] [NEW] Full-screen window flickers once when switching to it
You have been subscribed to a public bug: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Full-screen window flickers once when switching to it https://bugs.launchpad.net/bugs/1861391 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386
Hello Dan, or anyone else affected, Accepted network-manager into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.20.4-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-eoan ** Tags added: verification-needed verification-needed-eoan -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+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 1858092] Re: Network Manager not saving OpenVPN password
Hello Duarte, or anyone else affected, Accepted network-manager into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.20.4-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: network-manager (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1855009] Re: autopkgtests all fail on s390x
Hello Dan, or anyone else affected, Accepted network-manager into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.20.4-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-eoan ** Tags added: verification-needed verification-needed-eoan -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386
** Tags removed: block-proposed-eoan -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+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 1855009] Re: autopkgtests all fail on s390x
** Tags removed: block-proposed-eoan -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply
Well, have to wait for next bios update. If it help, attached you will find upower when discharging and charging, around 15 seconds between the 2 output ** Attachment added: "upower.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860761/+attachment/5324168/+files/upower.txt -- 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/1860761 Title: Dell XPS 13 - Bios upgrade not working - Always ask for power supply Status in gnome-software package in Ubuntu: Incomplete Bug description: Each time the notebook starts I'm advised that a new bios upgrade is out: XPS 13 7390 System Update 0.1.3.1 => 0.1.4.0 Problem is that when I ask for update, I always get this message (traduction from french): Not possible to upgrade "XPS 13 7390 System Update": connect power supply. Battery can be full, notebook connected on power supply, doesn't matter, will not upgrade. Daniel Ubuntu 18.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-software 3.28.1-0ubuntu4.18.04.14 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Uname: Linux 4.15.0-1066-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 09:15:31 2020 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-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (47 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.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/1860761/+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 1849135] Re: Clicking Activities in the corner doesn't work
Quite strange... I can confirm that the bug is fixed for me in Xorg session in Focal with regular upgrades and in Eoan after updgrade with proposed enabled. Version of mutter in Eoan is 3.34.3-1ubuntu1~19.10.1 Is there any useful information I can provide? -- 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/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Triaged Status in mutter source package in Eoan: Triaged Bug description: [ Impact ] Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan [ Test case ] - Move the mouse to the top-left corner pixel and click on it - Activities should open [ Regression potential ] Mouse picking location could be wrong in all clutter operations To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Hello Alberto, or anyone else affected, Accepted nvidia-settings into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- settings/440.44-0ubuntu0.19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-settings (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: In Progress Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect informa
[Desktop-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.132-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: In Progress Status in nvidia-settings source package in Eoan: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Up
[Desktop-packages] [Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop
** Changed in: thunderbird (Ubuntu) Status: New => Confirmed ** Changed in: thunderbird (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1861262 Title: Add message/rfc822 to thunderbird.desktop Status in thunderbird package in Ubuntu: Confirmed Bug description: Please add message/rfc822 to thunderbird.desktop: -MimeType=x-scheme-handler/mailto;application/x-xpinstall; +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822; It will allow to open *.eml files. I attach an example eml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+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 1861247] Re: Evince: Wrong font and wrong line height in PDF view
Thank you for your bug report. The rendering is done by poppler so probably an issue there, could you maybe also report it upstream on https://gitlab.freedesktop.org/poppler/poppler/issues ? ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Package changed: evince (Ubuntu) => poppler (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1861247 Title: Evince: Wrong font and wrong line height in PDF view Status in poppler package in Ubuntu: New Bug description: The attached pdf file is generated using Spyder 4, a Python IDE. The file contains embeded fonts UbuntuMono Regular and UbuntuMono Bold. When open with Evince, it seems using wrong font, and the line height is not correct. The file looks OK when open with other PDF viewer such as Firefox. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 29 11:53:43 2020 InstallationDate: Installed on 2019-12-14 (45 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1861247/+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 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply
Thank you for your reply, the 100% charged doesn't make much sense though, it you are on A/C it should be enough... without the debug informations hard to tell what the issue is though -- 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/1860761 Title: Dell XPS 13 - Bios upgrade not working - Always ask for power supply Status in gnome-software package in Ubuntu: Incomplete Bug description: Each time the notebook starts I'm advised that a new bios upgrade is out: XPS 13 7390 System Update 0.1.3.1 => 0.1.4.0 Problem is that when I ask for update, I always get this message (traduction from french): Not possible to upgrade "XPS 13 7390 System Update": connect power supply. Battery can be full, notebook connected on power supply, doesn't matter, will not upgrade. Daniel Ubuntu 18.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-software 3.28.1-0ubuntu4.18.04.14 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Uname: Linux 4.15.0-1066-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 09:15:31 2020 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-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (47 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.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/1860761/+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 1776447] Re: Xorg's Indirect GLX broken from upstream regression
The secondary crash doesn't occur without the first fix. You cannot reach it until the first fix is applied. However, I suppose it is in a different bit of code, but it is only reached when you use indirect GLX and prevents you using indirect GLX which is what this issue is attempting to fix. -- 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/1776447 Title: Xorg's Indirect GLX broken from upstream regression Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: [Impact] * IGLX is a way for an opengl application sending the 3D drawing GLX commands to the Xorg server for rendering instead of using the DRI infrastructure it is commonplace for High Performance Compute and Scientific institutions to use this feature of the Xorg server. (ref: https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX- Potential-Bye-Bye) * The feature is completely broken, currently, and any attempt to use it will cause the Xorg server to crash. This feature has been broken since a commit upstream in 2016. * The attached patch is from the revert commit entered into the upstream repository on 28 Jan 2020 following a git bisect of the bug discovering the offending commit. [Test Case] * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the following contents: ``` Section "ServerFlags" Option "IndirectGLX" "on" EndSection ``` * Log out of your Xorg session * Switch to a VT (Ctrl+Alt+F2) and login * Run `sudo systemctl restart gdm` to restart Xorg * Login to the graphical session * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils` * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears` * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting [Regression Potential] * This change is within DRI-related functionality and so might break all 3D accelerated applications. * There is a potential that the change is insufficient to fix the IGLX feature and so attempts to use it may still have undesirable and undefined results. * Upstream has run the patch through their CI system, which passed with no errors. This does not necessarily mean the patch will achieve the desired results, but at least indicates that the code does compile cleanly and can start an Xvfb headless instance. [Other Info] * This bug affects Ubuntu releases all the way back to, and including, Bionic 18.04. Original Bug Report Follows There's already an upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=99555 Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear: steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: 255 Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 1 (X_GLXRender) Serial number of failed request: 42 Current serial number in output stream: 936 I am trying to run what is effectively a traditional X Terminal, but as the hardware I am using has a 3D accelerated chipset it seems sensible to try to use it.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Jun 12 10:09:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2018-05-31 (11 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: AZW S I ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 00.12 dmi.board.asset.tag: Default string dmi.board.name: AB1 dmi.board.ve
[Desktop-packages] [Bug 1861322] Re: PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing
Thank you for your bug report. Is that issue new to focal? Could you add
a 'journalctl -b 0' log after triggering the error?
The code does
char *conntrack_module[] = { "/sbin/modprobe", "nf_conntrack_pptp",
NULL };
if (!g_spawn_sync (NULL, conntrack_module, NULL, 0, NULL, NULL, NULL,
NULL, NULL, &error)) {
_LOGW ("modprobing nf_conntrack_pptp failed: %s",
error->message);
so it should either load the module or print an error...
** Package changed: network-manager (Ubuntu) => network-manager-pptp
(Ubuntu)
** Changed in: network-manager-pptp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-pptp in Ubuntu.
https://bugs.launchpad.net/bugs/1861322
Title:
PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing
Status in network-manager-pptp package in Ubuntu:
Incomplete
Bug description:
PPTP based VPN doesn't work out of the box on Focal Fossa. From
syslog:
Jan 29 19:41:35 thinkpad pppd[8734]: Plugin
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:41:35 thinkpad NetworkManager[8734]: Plugin
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:41:35 thinkpad pptp[8739]: nm-pptp-service-8722
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1
'Start-Control-Connection-Request'
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7
'Outgoing-Call-Request'
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply.
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 44616,
peer's call ID 0).
Jan 29 19:42:03 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:976]: Call disconnect notification received (call id
44616)
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[logecho:pptp_ctrl.c:719]: Echo Request received.
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 6 'Echo-Reply'
Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722
warn[decaps_hdlc:pptp_gre.c:226]: short read (-1): Input/output error
Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722
warn[decaps_hdlc:pptp_gre.c:238]: pppd may have shutdown, see pppd log
Jan 29 19:42:06 thinkpad pppd[8734]: Child process /usr/sbin/pptp
161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722
(pid 8737) terminated with signal 15
Jan 29 19:42:06 thinkpad NetworkManager[8734]: Child process /usr/sbin/pptp
161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722
(pid 8737) terminated with signal 15
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled)
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 12
'Call-Clear-Request'
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[call_callback:pptp_callmgr.c:84]: Closing connection (call state)
Once nf_conntrack_pptp kernel module is loaded, VPN connection
succeeds:
Jan 29 19:44:02 thinkpad pppd[10166]: Plugin
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:44:02 thinkpad NetworkManager[10166]: Plugin
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:44:02 thinkpad pptp[10170]: nm-pptp-service-10156
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1
'Start-Control-Connection-Request'
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7
'Outgoing-Call-Request'
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply.
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 61223,
peer's call ID 0).
To manage notifications about this bug go to:
https://bu
[Desktop-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
> Is there a rough timeline when this will be available in eoan? It's been in the upload queue for Eoan since Jan 8, hopefully it will be reviewed/accepted soon. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.132-0ubuntu0.19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: In Progress Status in nvidia-settings source package in Eoan: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia
[Desktop-packages] [Bug 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
** Description changed: - The following command tells the files: + The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ + Only pulseaudio is a regular file; other ones are symbolic links, so it + is enough to modify the first one. + gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jarnos 1200 F pulseaudio - /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio - /dev/snd/controlC0: jarnos 1200 F pulseaudio - /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: jarnos 1200 F pulseaudio + /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio + /dev/snd/controlC0: jarnos 1200 F pulseaudio + /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Triaged Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/sha
[Desktop-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
P.S. The bug is indeed fixed in focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1858092] Re: Network Manager not saving OpenVPN password
Hi Pete, I will try to re-check the status of this for eoan today after work. Sorry for the delay, I have been very busy lately ;) Cheers. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/243 -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Triaged Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1200 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio /dev/snd/controlC0: jarnos 1200 F pulseaudio /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857708/+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 1857457] Re: Setting time automatically from the internet setting keeps getting lost
Has anyone looked at this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1857457 Title: Setting time automatically from the internet setting keeps getting lost Status in unity-control-center package in Ubuntu: New Bug description: I go into the time and date settings, and set the time to be automatically set from the internet. Then the next time time I go into the time and date settings, this setting has reverted to manual. I've set it to automatic many times, and the setting keeps getting lost. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Dec 24 14:04:00 2019 InstallationDate: Installed on 2017-08-16 (859 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: unity-control-center UpgradeStatus: Upgraded to eoan on 2019-10-04 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1857457/+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 1853007] Re: nsemail and nscopy files left in /tmp
Is there any news on fixing this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1853007 Title: nsemail and nscopy files left in /tmp Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Triaged Bug description: thunderbird leaves nsemail and nscopy files in /tmp: # ls -l /tmp/ns* -rw--- 1 alistair alistair 5522 Nov 18 08:42 /tmp/nscopy-1.tmp -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nscopy-2.tmp -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nscopy-3.tmp -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nscopy.tmp -rw--- 1 alistair alistair 25790 Nov 15 09:26 /tmp/nsemail-10.eml -rw--- 1 alistair alistair 5840 Nov 15 09:28 /tmp/nsemail-11.eml -rw--- 1 alistair alistair 25442 Nov 15 09:29 /tmp/nsemail-12.eml -rw--- 1 alistair alistair 2838 Nov 15 09:29 /tmp/nsemail-13.eml -rw--- 1 alistair alistair 8556 Nov 15 10:10 /tmp/nsemail-14.eml -rw--- 1 alistair alistair 1659 Nov 15 10:32 /tmp/nsemail-15.eml -rw--- 1 alistair alistair 3240 Nov 15 10:47 /tmp/nsemail-16.eml -rw--- 1 alistair alistair 3260 Nov 15 10:57 /tmp/nsemail-17.eml -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml -rw--- 1 alistair alistair 4878 Nov 15 13:44 /tmp/nsemail-19.eml -rw--- 1 alistair alistair 21150 Nov 13 08:43 /tmp/nsemail-1.eml -rw--- 1 alistair alistair 2974 Nov 18 08:41 /tmp/nsemail-1.html -rw--- 1 alistair alistair 6328 Nov 15 13:45 /tmp/nsemail-20.eml -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml -rw--- 1 alistair alistair 2733 Nov 15 17:15 /tmp/nsemail-22.eml -rw--- 1 alistair alistair 53857 Nov 16 09:23 /tmp/nsemail-23.eml -rw--- 1 alistair alistair 89392 Nov 16 09:39 /tmp/nsemail-24.eml -rw--- 1 alistair alistair 80120 Nov 17 10:52 /tmp/nsemail-25.eml -rw--- 1 alistair alistair 6361 Nov 17 18:45 /tmp/nsemail-26.eml -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nsemail-27.eml -rw--- 1 alistair alistair 5522 Nov 18 08:41 /tmp/nsemail-28.eml -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nsemail-29.eml -rw--- 1 alistair alistair 29937 Nov 13 09:37 /tmp/nsemail-2.eml -rw--- 1 alistair alistair 5057 Nov 18 08:43 /tmp/nsemail-2.html -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nsemail-30.eml -rw--- 1 alistair alistair 2015 Nov 13 09:40 /tmp/nsemail-3.eml -rw--- 1 alistair alistair 4949 Nov 18 08:49 /tmp/nsemail-3.html -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml -rw--- 1 alistair alistair 59817 Nov 15 08:41 /tmp/nsemail-5.eml -rw--- 1 alistair alistair 9751 Nov 15 08:47 /tmp/nsemail-6.eml -rw--- 1 alistair alistair 2967 Nov 15 08:49 /tmp/nsemail-7.eml -rw--- 1 alistair alistair 2983 Nov 15 08:54 /tmp/nsemail-8.eml -rw--- 1 alistair alistair 19780 Nov 15 09:14 /tmp/nsemail-9.eml -rw--- 1 alistair alistair 27900 Nov 13 08:34 /tmp/nsemail.eml -rw--- 1 alistair alistair 1317 Nov 18 08:38 /tmp/nsemail.html -rw--- 1 alistair alistair 1115 Nov 18 08:41 /tmp/nsmail-1.tmp -rw--- 1 alistair alistair 2424 Nov 18 08:43 /tmp/nsmail-2.tmp -rw--- 1 alistair alistair 2000 Nov 18 08:49 /tmp/nsmail-3.tmp -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.1.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2211 F pulseaudio BuildID: 20191010144232 Channel: Unavailable Date: Mon Nov 18 08:50:15 2019 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback dns-search integrics.com InstallationDate: Installed on 2017-08-16 (823 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 1.0.0.1 dev wlp58s0 proto dhcp metric 600 1.0.0.0/21 dev wlp58s0 proto kernel scope link src 1.0.1.146 metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 NoProfiles: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to eoan on 2019-10-04 (44 days ago) dmi.bios.date
[Desktop-packages] [Bug 1854753] Re: Unity menus aren't initially populated
Olivier, any news on this? It's still happening.
--
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/1854753
Title:
Unity menus aren't initially populated
Status in firefox package in Ubuntu:
Incomplete
Bug description:
If you navigate using the mouse to a menu that has a submenu, for
example View -> Toolbars, sometimes the first time you do so, the
submenu is empty and only shows as a very small grey rectangle. If you
then move the mouse pointer away from the menu, click in the middle of
a web page, wait a few seconds, and then try the submenu again, the
submenu is appears correctly.
Thunderbird 68.2.1 is also affected by this problem.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 70.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alistair 2189 F pulseaudio
BuildID: 20191031091608
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Dec 2 10:31:01 2019
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
dns-search integrics.com
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2017-08-16 (837 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
default via 172.20.0.1 dev wlp58s0 proto dhcp metric 600
169.254.0.0/16 dev wlp58s0 scope link metric 1000
172.20.0.0/20 dev wlp58s0 proto kernel scope link src 172.20.0.120 metric 600
MostRecentCrashID: bp-3d145359-2f62-4b35-a046-86be50191125
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=70.0.1/20191031091608 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to eoan on 2019-10-04 (58 days ago)
dmi.bios.date: 08/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET56W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1854753/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
This bug was fixed in the package ubuntu-meta - 1.417.4 --- ubuntu-meta (1.417.4) bionic; urgency=medium * Refreshed dependencies * Removed ubuntu-web-launchers from desktop-recommends (LP: #1860565) -- Iain Lane Wed, 22 Jan 2020 15:25:25 + ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Released Status in ubuntu-settings source package in Bionic: Fix Released Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860522] Re: Mesa 19.2.8 stable release
This bug was fixed in the package mesa - 19.2.8-0ubuntu0~19.10.1 --- mesa (19.2.8-0ubuntu0~19.10.1) eoan; urgency=medium * New bugfix release. (LP: #1860522) * Revert-meson-fix-logic-for-generating-.pc-files-with.patch: Dropped, fixed upstream. * rules: GLESv2 libs aren't built anymore, drop removing them. * mesa-common-dev: Drop mangled GL/GLX headers, they're not generated anymore. -- Timo Aaltonen Wed, 22 Jan 2020 11:57:11 +0200 ** Changed in: mesa (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Released Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1860565] Update Released
The verification of the Stable Release Update for ubuntu-settings has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-settings source package in Bionic: Fix Released Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860522] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Released Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
This bug was fixed in the package ubuntu-settings - 18.04.7 --- ubuntu-settings (18.04.7) bionic; urgency=medium * Make ubuntu-web-launchers an empty package and drop amazon launcher from favourites. For the bionic SRU, it is safest to leave this as an empty package. Users can remove it if they want to. (LP: #1860565) -- Iain Lane Wed, 22 Jan 2020 16:22:04 + ** Changed in: ubuntu-settings (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-settings source package in Bionic: Fix Released Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1775926] Re: Firefox cannot handle IPv6 addresses well
The upstream bug report (https://bugzilla.mozilla.org/show_bug.cgi?id=700999) was closed as RESOLVED WONTFIX because they want to follow the proposal for URLs by WhatWG which doesn’t mention link-local IPv6 address specifiers. ** Bug watch added: Mozilla Bugzilla #700999 https://bugzilla.mozilla.org/show_bug.cgi?id=700999 -- 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/1775926 Title: Firefox cannot handle IPv6 addresses well Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 60.0.1 (64-bit), Ubuntu 16.04.4 amd64 Link addresses for IPv6 are tricky. IPv6 address has to be extended with network interface (zone id), to signal OS what network interface to use. When I try to connect with Firefox to following URL http://[fe80::87f4:81fa:b481:d781]/test.html it is confused. It even doesn't report an error that it cannot do that. When I enter URL with zone information, Firefox returns "search" results, in means, it doesn't understand this syntax of IPv6 address... http://[fe80::87f4:81fa:b481:d781%enp4s0]/test.html Here is RFC describing zones, https://tools.ietf.org/html/rfc4007 Demo with CURL, that can handle such URLs without any problem: user@test:~$ curl http://[fe80::87f4:81fa:b481:d781]/test.html curl: (7) Couldn't connect to server user@test:~$ curl http://[fe80::87f4:81fa:b481:d781%enp4s0]/test.html TEST user@test:~$ curl http://[fe80::87f4:81fa:b481:d781%2]/test.html TEST user@test:~$ curl http://[::1]/test.html TEST user@test:~$ curl http://[::1%lo]/test.html TEST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1775926/+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
