[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing
the fix released in gnome-shell 3.30.1 only available for Ubuntu 18.10. is right? if it possible to released patch for Ubuntu 18.04? -- 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/1774957 Title: Network icons in status menu disappearing Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 --- Ever since the update to Ubuntu 18.04 I'm having issues with the status menu at the top right of the screen. Normally you'd have a wired network connection icon displayed at the top without opening the menu. In my case it is not displayed half of the time. In the menu list no icon nor label is displayed for the wired connection menu item. When talking about half of the time it means that I can randomly make it display again when removing the USB network adapter and reconnecting it e.g. This does not work reliably though. When connecting to a VPN, normally you'd get an additional icon at the top. This is not the case any more, nor does the switch behind an activated VPN turns change to an active state. The result is that you can activate a VPN using the switch, but you can verify that it is activated, nor can you de-active the VPN through the menu. This does change in settings though. Wireless settings are no longer displayed in the menu at all. So no way to activate it or connect to a specific network. I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as network-manager-gnome, to no avail. Attached you'll find a screenshot illustrating the issue. You'll see two icons missing to the left of the volume icon, as well as the wireless menu missing completely and no icon and text label for the wired connection menu item. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 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 CurrentDesktop: GNOME Date: Mon Jun 4 10:47:05 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-07 (604 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803078] Re: Screensaver unlock screen shown twice after playing video
** No longer affects: totem (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1803078 Title: Screensaver unlock screen shown twice after playing video Status in cinnamon-session package in Ubuntu: New Bug description: Observed behaviour: resuming from screensaver, after unlocking the screen with a password, the desktop is shown briefly and is immediately locked again, but with a different look-and-feel lock screen. Entering the password once more will finally show the desktop. This started happening seemingly sporadically, and would continue to happen consistently until end of session (logout or shutdown). Digging further, it was found that a `gnome-screensaver` process was running in addition to the normal `cinnamon-screensaver`. It was a child process of `systemd --user`, so a `ps -o pid,comm,cgroup` found that it was running as part of `dbus.service`. Finally, the culprit was found in the journal for that unit (`dbus.service`): Nov 12 15:03:40 laptop dbus-daemon[1696]: [session uid=1000 pid=1696] Activating service name='org.gnome.ScreenSaver' requested by ':1.206' (uid=1000 pid=3445 comm="/usr/bin/totem --gapplication-service " label="unconfined") So, the workaround (which I am quite happy with, frankly) is to use VLC instead of Totem. ☺ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cinnamon-session 3.6.1-1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Nov 13 08:56:37 2018 InstallationDate: Installed on 2018-10-31 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: cinnamon-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-session/+bug/1803078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery
Thanks George for testing, the existing tags verification-needed are the ones to edit & change in verification-done, I'm doing that now ** 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 totem in Ubuntu. https://bugs.launchpad.net/bugs/1798399 Title: totem silently fails to create screenshot gallery Status in totem package in Ubuntu: Fix Released Status in totem source package in Bionic: Fix Committed Status in totem source package in Cosmic: Fix Released Bug description: *Impact The gallery plugin/menu option doesn't work * Test case - open a video - open the menu and click on the gallery option - validate making a gallery with the default options -> the picked filename should exist and be a gallery if pictures from the video * Regression potential The changes are restricted to the screenshot plugin, so make sure that one works -- https://gitlab.gnome.org/GNOME/totem/issues/268 --- https://gitlab.gnome.org/GNOME/totem/merge_requests/18/ --- Package totem 3.26.0-0ubuntu6 totem 3.26.0 running on Ubuntu 18.04 silently fails to create screenshot gallery. I'm assuming that this has something to do with totem-video-thumbnailer. Steps to reproduce: totem-video-thumbnailer -g 20 inputvideo outputpng I can reproduce this result with both HEVC and AVC encoded videos. I haven't been able to test other codecs, but the error indicates the codec isn't the problem. totem 3.18.1 under Ubuntu 16.04 does not have this problem. Any further information required I will be happy to produce within my abilities. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-19 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: totem 3.26.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing
Fix released in gnome-shell 3.30.1 (Ubuntu 18.10 onward). ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774957 Title: Network icons in status menu disappearing Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 --- Ever since the update to Ubuntu 18.04 I'm having issues with the status menu at the top right of the screen. Normally you'd have a wired network connection icon displayed at the top without opening the menu. In my case it is not displayed half of the time. In the menu list no icon nor label is displayed for the wired connection menu item. When talking about half of the time it means that I can randomly make it display again when removing the USB network adapter and reconnecting it e.g. This does not work reliably though. When connecting to a VPN, normally you'd get an additional icon at the top. This is not the case any more, nor does the switch behind an activated VPN turns change to an active state. The result is that you can activate a VPN using the switch, but you can verify that it is activated, nor can you de-active the VPN through the menu. This does change in settings though. Wireless settings are no longer displayed in the menu at all. So no way to activate it or connect to a specific network. I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as network-manager-gnome, to no avail. Attached you'll find a screenshot illustrating the issue. You'll see two icons missing to the left of the volume icon, as well as the wireless menu missing completely and no icon and text label for the wired connection menu item. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 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 CurrentDesktop: GNOME Date: Mon Jun 4 10:47:05 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-07 (604 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803293] Re: icon network not showing in gnome-shell
*** This bug is a duplicate of bug 1774957 *** https://bugs.launchpad.net/bugs/1774957 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1774957, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1774957 Network icons in status menu disappearing -- 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/1803293 Title: icon network not showing in gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: see more info in https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 I think it is critical BUG that make the user experience terrible. I hope the gnome-shell with this fix for Ubuntu can be upgraded as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637420] Re: closing gedit in 16.10 sometimes closes whole gnome-fallback session
Absolutely disagree. Bug was not invalid, invalid is no efforts to solve problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1637420 Title: closing gedit in 16.10 sometimes closes whole gnome-fallback session Status in gedit package in Ubuntu: Invalid Bug description: Hello! Don't know how to reproduce it, but hit this several times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1637420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803293] [NEW] icon network not showing in gnome-shell
Public bug reported: see more info in https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 I think it is critical BUG that make the user experience terrible. I hope the gnome-shell with this fix for Ubuntu can be upgraded as soon as possible. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-desktop3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1803293 Title: icon network not showing in gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: see more info in https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 I think it is critical BUG that make the user experience terrible. I hope the gnome-shell with this fix for Ubuntu can be upgraded as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788021] Re: changing keyborad brightness doesn't work
Using Mainline Kernel 4.19.0 or above, it works. So it's a bug in the Ubuntu 18.10 Kernel Version. Maybe it's this 4.19 patch. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61c4fc1eaf736344904767d201b0d4f7a2ebaf79 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1788021 Title: changing keyborad brightness doesn't work Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Checking 'journalctl' I get this error message: gsd-power[1924]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Running on an Asus UX490UA (7th-gen Intel CPU), and before upgrading to 18.10 everything worked fine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.29.90.1-1~ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 21:22:13 2018 InstallationDate: Installed on 2018-08-15 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to cosmic on 2018-08-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1788021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803078] Re: Screensaver unlock screen shown twice after playing video
It may be considered a bug in Totem, actually. Is it OK for it to ask D-Bus to launch the Gnome screensaver in the first place, while not running in a Gnome session? +Bastien Nocera, what do you think[1]? [1] https://gitlab.gnome.org/GNOME/totem/commit/336154c47dc415299e54b260c5438def6afd6f8b -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1803078 Title: Screensaver unlock screen shown twice after playing video Status in cinnamon-session package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Observed behaviour: resuming from screensaver, after unlocking the screen with a password, the desktop is shown briefly and is immediately locked again, but with a different look-and-feel lock screen. Entering the password once more will finally show the desktop. This started happening seemingly sporadically, and would continue to happen consistently until end of session (logout or shutdown). Digging further, it was found that a `gnome-screensaver` process was running in addition to the normal `cinnamon-screensaver`. It was a child process of `systemd --user`, so a `ps -o pid,comm,cgroup` found that it was running as part of `dbus.service`. Finally, the culprit was found in the journal for that unit (`dbus.service`): Nov 12 15:03:40 laptop dbus-daemon[1696]: [session uid=1000 pid=1696] Activating service name='org.gnome.ScreenSaver' requested by ':1.206' (uid=1000 pid=3445 comm="/usr/bin/totem --gapplication-service " label="unconfined") So, the workaround (which I am quite happy with, frankly) is to use VLC instead of Totem. ☺ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cinnamon-session 3.6.1-1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Nov 13 08:56:37 2018 InstallationDate: Installed on 2018-10-31 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: cinnamon-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-session/+bug/1803078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803078] Re: Screensaver unlock screen shown twice after playing video
** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1803078 Title: Screensaver unlock screen shown twice after playing video Status in cinnamon-session package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Observed behaviour: resuming from screensaver, after unlocking the screen with a password, the desktop is shown briefly and is immediately locked again, but with a different look-and-feel lock screen. Entering the password once more will finally show the desktop. This started happening seemingly sporadically, and would continue to happen consistently until end of session (logout or shutdown). Digging further, it was found that a `gnome-screensaver` process was running in addition to the normal `cinnamon-screensaver`. It was a child process of `systemd --user`, so a `ps -o pid,comm,cgroup` found that it was running as part of `dbus.service`. Finally, the culprit was found in the journal for that unit (`dbus.service`): Nov 12 15:03:40 laptop dbus-daemon[1696]: [session uid=1000 pid=1696] Activating service name='org.gnome.ScreenSaver' requested by ':1.206' (uid=1000 pid=3445 comm="/usr/bin/totem --gapplication-service " label="unconfined") So, the workaround (which I am quite happy with, frankly) is to use VLC instead of Totem. ☺ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cinnamon-session 3.6.1-1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Nov 13 08:56:37 2018 InstallationDate: Installed on 2018-10-31 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: cinnamon-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-session/+bug/1803078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789356] Re: Dark purple (noise) background flashes up briefly during the login animation since Yaru was introduced
I found the problem yesterday. The regression is that the gradient (which didn't appear at all before) now only occupies the middle 50% of the screen. This means it looks squashed and different to the login screen. The top and bottom 25% of the screen are solid colours. It looks like a problem with texture coordinates and GL clamp-to-edge, since the gradient is really only a 1x2 two pixel texture rendered with linear filtering. ** Tags added: regression-release ** Summary changed: - Dark purple (noise) background flashes up briefly during the login animation since Yaru was introduced + The wrong background flashes up briefly during the login animation since Yaru was introduced ** Description changed: [Impact] - Dark purple (noise) background flashes up briefly (for a split second) during the login animation. + The wrong background flashes up briefly (for a split second) during the login animation. The login screen and gnome-shell's system background are meant to be the same image so that the login procedure can VT switch without the user noticing. Then the final desktop expands over the system background. However it appears the login background and system background are not the same image any more, causing a visible glitch during login. [Test Case] 1. Install new version, logout 2. Log in into GDM -> Check that at login startup, the background matches GDM ones (same color, same gradient) 3. Logout, install gnome-session 4. Reboot so that GDM takes gnome-session into account 5. Select GNOME session and login -> At login startup, the background will matche the GNOME default one (from the lockscreen: grey noise), which matches GDM one if reset to default GNOME via update-alternatives. [Regression Potential] This code is loaded at session startup, if there is a syntax error, the session wouldn't start at all. This has been of course tested before committed (both on ubuntu and GNOME sessions) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.2 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Aug 28 14:19:48 2018 Dependencies: InstallationDate: Installed on 2018-05-26 (93 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1789356 Title: The wrong background flashes up briefly during the login animation since Yaru was introduced Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] The wrong background flashes up briefly (for a split second) during the login animation. The login screen and gnome-shell's system background are meant to be the same image so that the login procedure can VT switch without the user noticing. Then the final desktop expands over the system background. However it appears the login background and system background are not the same image any more, causing a visible glitch during login. [Test Case] 1. Install new version, logout 2. Log in into GDM -> Check that at login startup, the background matches GDM ones (same color, same gradient) 3. Logout, install gnome-session 4. Reboot so that GDM takes gnome-session into account 5. Select GNOME session and login -> At login startup, the background will matche the GNOME default one (from the lockscreen: grey noise), which matches GDM one if reset to default GNOME via update-alternatives. [Regression Potential] This code is loaded at session startup, if there is a syntax error, the session wouldn't start at all. This has been of course tested before committed (both on ubuntu and GNOME sessions) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.2 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Aug 28 14:19:48 2018 Dependencies: InstallationDate: Installed on 2018-05-26 (93 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1803271] Re: [regression] Much higher CPU during some gnome-shell operations
The more current fix for this bug is: --- gjs-1.54.1/gjs/context.cpp 2018-09-24 04:22:18.0 + +++ gjs-1.54.2/gjs/context.cpp 2018-10-22 14:10:59.0 + @@ -636,9 +636,9 @@ if (js_context->auto_gc_id > 0) return; -js_context->auto_gc_id = g_idle_add_full(G_PRIORITY_LOW, - trigger_gc_if_needed, - js_context, NULL); +js_context->auto_gc_id = g_timeout_add_seconds_full(G_PRIORITY_LOW, 10, +trigger_gc_if_needed, +js_context, NULL); } ** Changed in: gjs (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Description changed: - Since fixing bug 1672297 we experience much higher CPU during gnome- - shell JavaScript operations, such as the icon spring animation. + Since fixing bug 1672297 in release 18.04 we experience much higher CPU + during gnome-shell JavaScript operations, such as the icon spring + animation. The fix for this regression is https://gitlab.gnome.org/GNOME/gjs/merge_requests/236 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1803271 Title: [regression] Much higher CPU during some gnome-shell operations Status in gjs package in Ubuntu: Fix Released Bug description: Since fixing bug 1672297 in release 18.04 we experience much higher CPU during gnome-shell JavaScript operations, such as the icon spring animation. The fix for this regression is https://gitlab.gnome.org/GNOME/gjs/merge_requests/236 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803271] Re: [regression] Much higher CPU during some gnome-shell operations
Also, the fix is already in 19.04 here: https://launchpad.net/ubuntu/+source/gjs/1.54.2-1 ** Changed in: gjs (Ubuntu) Status: New => Fix Released ** Tags added: bionic cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1803271 Title: [regression] Much higher CPU during some gnome-shell operations Status in gjs package in Ubuntu: Fix Released Bug description: Since fixing bug 1672297 we experience much higher CPU during gnome- shell JavaScript operations, such as the icon spring animation. The fix for this regression is https://gitlab.gnome.org/GNOME/gjs/merge_requests/236 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803271] [NEW] [regression] Much higher CPU during some gnome-shell operations
Public bug reported: Since fixing bug 1672297 we experience much higher CPU during gnome- shell JavaScript operations, such as the icon spring animation. The fix for this regression is https://gitlab.gnome.org/GNOME/gjs/merge_requests/236 ** Affects: gjs (Ubuntu) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: Fix Released ** Tags: bionic cosmic disco performance regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1803271 Title: [regression] Much higher CPU during some gnome-shell operations Status in gjs package in Ubuntu: Fix Released Bug description: Since fixing bug 1672297 we experience much higher CPU during gnome- shell JavaScript operations, such as the icon spring animation. The fix for this regression is https://gitlab.gnome.org/GNOME/gjs/merge_requests/236 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799266] Re: gnome-shell uses 44% cpu when simply moving windows
The GJS fix is now in 19.04 here: https://launchpad.net/ubuntu/+source/gjs/1.54.2-1 ** Changed in: gjs (Ubuntu) Status: In Progress => Fix Released ** Changed in: gjs (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1799266 Title: gnome-shell uses 44% cpu when simply moving windows Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: After doing a stock install Ubuntu 18.04.1 LTS on an imac 27" 2010 8G ram, Intel® Core™ i7 CPU 870 @ 2.93GHz × 8 Simply moving a window around on the screen increases the cpu usage by gnome-shell to 44%. When displaying a movie, totem takes 10%, gnome-shell takes 22%. etc etc System:Host: oldie Kernel: 4.15.0-36-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Machine: Device: desktop System: Apple product: iMac11 3 v: 1.0 serial: N/A Mobo: Apple model: Mac-F2238BAE v: iMac11 3 serial: N/A UEFI: Apple v: IM112.88Z.0057.B01.1112090906 date: 12/09/11 CPU: Quad core Intel Core i7 870 (-MT-MCP-) cache: 8192 KB clock speeds: max: 2927 MHz 1: 1271 MHz 2: 1206 MHz 3: 1374 MHz 4: 1271 MHz 5: 1377 MHz 6: 1266 MHz 7: 1693 MHz 8: 1279 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Broadway PRO [Mobility Radeon HD 5850] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 2560x1440@59.95hz OpenGL: renderer: AMD JUNIPER (DRM 2.50.0 / 4.15.0-36-generic, LLVM 6.0.0) version: 3.3 Mesa 18.0.5 Audio: Card-1 Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel Card-2 Advanced Micro Devices [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series] driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic Network: Card-1: Broadcom Limited NetXtreme BCM5764M Gigabit Ethernet PCIe driver: tg3 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: c4:2c:03:30:ce:8e Card-2: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k IF: wls1 state: down mac: d8:30:62:67:2a:19 Drives:HDD Total Size: 2500.5GB (38.0% used) ID-1: /dev/sda model: WDC_WD1001FALS size: 1000.2GB ID-2: USB /dev/sdb model: MK1059GSM size: 1000.2GB ID-3: USB /dev/sdd model: Elements_10B8 size: 500.1GB Partition: ID-1: / size: 226G used: 125G (58%) fs: ext4 dev: /dev/sda2 ID-2: /home size: 701G used: 876M (1%) fs: btrfs dev: /dev/sda4 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 56.0C mobo: N/A Fan Speeds (in rpm): cpu: 936 Info: Processes: 342 Uptime: 3:07 Memory: 2087.3/7967.4MB Client: Shell (bash) inxi: 2.3.56 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 19:09:59 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-10-22 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.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/gjs/+bug/1799266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
I don't know what I was thinking... This bug is clearly declared fixed
in 18.04 already:
gjs (1.52.1-1ubuntu1) bionic; urgency=medium
* Add fix-crashes-lp1763878-revert-575f1e2e077.patch to fix shutdown
crashes (LP: #1763878)
* Add some patches to solve large memory leaks (LP: #1672297)
- fix-leaks-lp1672297-1-context-Add-API-to-force-GC-schedule.patch
- fix-leaks-lp1672297-2-object-Queue-a-forced-GC-when-toggling-down.patch
- Note: More such patches are under review so this list may grow in future.
-- Daniel van Vugt Mon, 16 Apr 2018
14:30:31 +0800
If anyone experiences new leaks in 18.10 then please see bug 1800165.
For anything else, please open a new bug.
** Changed in: gjs (Ubuntu Bionic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Bionic:
Fix Released
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42,
[Desktop-packages] [Bug 1803270] [NEW] Support for Snap Apps
Public bug reported: I can't type Vietnamese in some Snap Apps like Skype, Rocket.Chat+. But for apps were installed by deb packet, it's ok (I can type Vietnamese). ** Affects: ibus-unikey (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-unikey in Ubuntu. https://bugs.launchpad.net/bugs/1803270 Title: Support for Snap Apps Status in ibus-unikey package in Ubuntu: New Bug description: I can't type Vietnamese in some Snap Apps like Skype, Rocket.Chat+. But for apps were installed by deb packet, it's ok (I can type Vietnamese). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1803270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768408] Re: Desktop content
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1768408 Title: Desktop content Status in gnome-shell package in Ubuntu: Expired Bug description: By dragging a desktop content into a folder on the system, the desktop gets stuck and only comes back with the system reboot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 2 01:10:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a] InstallationDate: Installed on 2018-04-27 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 820 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1d729abd-93bc-472e-89ed-243524756bc7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.21 dmi.board.name: 225A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.5B dmi.chassis.asset.tag: 5CG6257W70 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.21:bd07/13/2017:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009D510303:rvnHewlett-Packard:rn225A:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G2 dmi.product.version: A3009D510303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759009] Re: software bug
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1759009 Title: software bug Status in Ubuntu: Incomplete Bug description: I ran the installed x diagnosis software. The software found the bug. I have no idea what the problem is. My Ubuntu Apps application will not work. I tried removing and reinstall the application but it still will not work. I installed gnome-software as a work around but that doesn't seem to work either. I believe my Ubuntu 16.04 lts original installation is faulty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 26 12:02:22 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053e] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K2000M] [1028:153e] InstallationDate: Installed on 2018-03-23 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Precision M4700 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=6126fabd-0eaf-4345-ac41-42b5013ac682 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 082H3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/09/2017:svnDellInc.:pnPrecisionM4700:pvr01:rvnDellInc.:rn082H3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4700 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1759009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761084] Re: NA
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761084 Title: NA Status in Ubuntu: Incomplete Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Apr 4 12:48:47 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3809] InstallationDate: Installed on 2018-03-04 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b50e Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Q7 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=6443b635-7581-4cac-989d-220941f038da ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN47WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD5CN47WW:bd08/26/2016:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK: dmi.product.name: 80Q7 dmi.product.version: Lenovo ideapad 300-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Apr 4 15:51:47 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5574 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1761084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759193] Re: 2 mistakes
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1759193 Title: 2 mistakes Status in xorg-server package in Ubuntu: Won't Fix Bug description: when I start i cannot open ubuntu and gnome but only Xorg gnome Xorg ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 27 11:28:36 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:2b43] InstallationDate: Installed on 2017-12-04 (113 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: HP 23-q112nf ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=5527cad1-6d63-4e37-9df8-21296e5bba7f ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2015 dmi.bios.vendor: AMI dmi.bios.version: A0.04 dmi.board.asset.tag: CZC6167BD6 dmi.board.name: 2B43 dmi.board.vendor: HP dmi.board.version: 000 dmi.chassis.asset.tag: CZC6167BD6 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrA0.04:bd08/04/2015:svnHP:pn23-q112nf:pvr:rvnHP:rn2B43:rvr000:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 23-q112nf dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Mar 25 09:15:19 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1759193/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761210] Re: help
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761210 Title: help Status in Ubuntu: Incomplete Bug description: help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Apr 4 22:28:18 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:110f] InstallationDate: Installed on 2018-03-28 (6 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-475 ProcEnviron: LANGUAGE=en_PH:en TERM=xterm-256color PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=59957697-26e9-4c70-89af-17906e8edf33 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: AntMan_SK dmi.board.vendor: Acer dmi.board.version: V1.01 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-475 dmi.product.version: V1.01 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 4 22:16:25 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1761210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761575] Re: bug
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761575 Title: bug Status in linux package in Ubuntu: New Bug description: Web cam dosn't work, totem either. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Apr 5 21:12:15 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 1100/1150] [1458:d000] InstallationDate: Installed on 2018-02-28 (35 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) MachineType: FUJITSU SIEMENS GA-K8RS482M ProcEnviron: LANGUAGE=hu PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2005 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: GA-K8RS482M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr: dmi.product.name: GA-K8RS482M dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Apr 5 20:20:48 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSIGMACHIP Usb Mouse MOUSE, id 8 inputHID 1267:0103KEYBOARD, id 9 inputHID 1267:0103KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801832] Re: Input method toggled when using the numeric pad
IBus 1.5.17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1801832 Title: Input method toggled when using the numeric pad Status in ibus package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 LTS During the Chinese character input mode, when I enter numbers using the numeric pad, the input method will be switched to English automatically, which is very annoying. Any suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1801832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803222] Re: keyboard
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - keyboard + keyboard is not typing anymore after walking up from suspend ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Tags added: resume suspend-resume -- 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/1803222 Title: keyboard is not typing anymore after walking up from suspend Status in xorg-server package in Ubuntu: New Bug description: my keyboard is not typing anymore after walking up from suspend ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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: Wed Nov 14 01:18:20 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:90b8] InstallationDate: Installed on 2018-11-08 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Sony Corporation SVF1421E2EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=9e5fff3a-5a47-425f-aff8-0e05ed437a1c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0250DA dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0250DA:bd07/19/2016:svnSonyCorporation:pnSVF1421E2EW:pvrC10JBKXD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVF1421E2EW dmi.product.version: C10JBKXD dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Nov 14 01:04:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803208] Re: gnome-shell[4614]: gtk_action_observer_action_removed: assertion 'GTK_IS_ACTION_OBSERVER (observer)' failed
It's unlikely that assertion message is related to gnome-shell rejecting mouse clicks. So I will reword the bug title... The first thing to try is always to remove/disable your custom extensions since extensions cause a large number of bugs. You have: b'org.gnome.shell' b'enabled-extensions' b"['dash-to- pa...@jderose9.github.com', 'all-in-one-places@jofer']" Please disable or remove those and see if the problem reoccurs. ** Tags added: noclick ** Summary changed: - gnome-shell[4614]: gtk_action_observer_action_removed: assertion 'GTK_IS_ACTION_OBSERVER (observer)' failed + GNOME Shell unresponsive (could move my cursor but clicking anything didn't produce any actual effects) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1803208 Title: GNOME Shell unresponsive (could move my cursor but clicking anything didn't produce any actual effects) Status in gnome-shell package in Ubuntu: Incomplete Bug description: GNOME Shell was unresponsive (could move my cursor and I think Shell elements were changing colour etc as I hovered over them but clicking anything didn't produce any actual effects) after trying to log into an email account on the Geary Flatpak and opening Firefox (Deb) pretty much simultaneously. Not sure this is reproducible. I checked `journalctl -r` and I had 150,000 repeats (in a short period of time) of `adam-thinkpad-t430 gnome-shell[4614]: gtk_action_observer_action_removed: assertion 'GTK_IS_ACTION_OBSERVER (observer)' failed`, I don't think this has come up in the logs aside from for that crash... Pretty sure that Shell is to blame, not Geary or Firefox... ``` $ flatpak info org.gnome.Geary/x86_64/stable Ref: app/org.gnome.Geary/x86_64/stable ID: org.gnome.Geary Arch: x86_64 Branch: stable Origin: flathub Collection ID: org.flathub.Stable Date: 2018-08-29 14:38:53 + Subject: Update for 0.12.4. (c4d8833e) Commit: c6deb6487b655567845fe8a71442c1d04841cc7064dbbf58c93e5164296a87e8 Parent: 5de6d62d384c0213ea3998249b9c28bcf0d75a17a1c52c29da85c7588ed0aa89 Location: /var/lib/flatpak/app/org.gnome.Geary/x86_64/stable/c6deb6487b655567845fe8a71442c1d04841cc7064dbbf58c93e5164296a87e8 Installed size: 6.9 MB Runtime: org.gnome.Platform/x86_64/3.28 Sdk: org.gnome.Sdk/x86_64/3.28 ``` ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 22:46:13 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-03 (467 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-21 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803192] Re: Internal MIC stopped to work on 18.10
Please run this command to send us more information about the system: apport-collect 1803192 ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) ** Tags added: cosmic ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1803192 Title: Internal MIC stopped to work on 18.10 Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the internal Mic stop to work. Everything works well (speakers, etc) however no more sound comes as entry from Internal Mic. I checked and she has chipset ALC269VB i update to alsa-driver 1.1.7 without success. i checked alsamixer and everything seems ok as with pavucontrol. I upgraded my laptop too to 18.10 and i have no issue with internal mic but i do not have the same chipset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802950] Re: X.org crashes after upgrade to 18.10
If you are unable to open a web browser then please try using 'apport- cli' instead of 'ubuntu-bug'. -- 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/1802950 Title: X.org crashes after upgrade to 18.10 Status in xorg-server package in Ubuntu: Incomplete Bug description: After the upgrade from 18.04 to 18.10, SDDM fails to start. This happens with kernel 4.18.0-10 and 4.15.0-36 (it was the chance to discover grub-reboot) See SDDM crash file attached. The machine is a virtual machine, and PCI devices use virtio-pci driver for example. I looked into /var/log/Xorg.0.log and found many error messages, the first one being : (EE) open /dev/dri/card0: No such file or directory See Xorg log file and crash file attached. Then I looked at the output of 'lspci -vvnn' and it seems that no kernel driver manages the VGA Controller. See output of 'lspci -vvnn' attached According to the following message, the missing kernel driver may be : bochs-drm or virtio-vga https://www.redhat.com/archives/libvir-list/2015-August/msg00220.html # lsb_release -rd Description:Ubuntu 18.10 Release:18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803236] [NEW] network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS
Public bug reported: During the do-release-upgrade from 16.04 to 18.04, if the user chooses to preserve the old NetworkManager.conf having "dns=dnsmasq", it does not preserve dnsmasq as the local resolver. It results in a broken DNS configuration, with /etc/resolv.conf set to 127.0.0.53 but NetworkManager set to dnsmasq. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1803236 Title: network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS Status in network-manager package in Ubuntu: New Bug description: During the do-release-upgrade from 16.04 to 18.04, if the user chooses to preserve the old NetworkManager.conf having "dns=dnsmasq", it does not preserve dnsmasq as the local resolver. It results in a broken DNS configuration, with /etc/resolv.conf set to 127.0.0.53 but NetworkManager set to dnsmasq. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1803236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802950] Re: X.org crashes after upgrade to 18.10
Please try running: apport-cli _usr_lib_xorg_Xorg.0.crash and then copy and paste the link it (eventually) gives you into a web browser on a different machine. If for any reason that doesn't work then the next option is to look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1802950 Title: X.org crashes after upgrade to 18.10 Status in xorg-server package in Ubuntu: Incomplete Bug description: After the upgrade from 18.04 to 18.10, SDDM fails to start. This happens with kernel 4.18.0-10 and 4.15.0-36 (it was the chance to discover grub-reboot) See SDDM crash file attached. The machine is a virtual machine, and PCI devices use virtio-pci driver for example. I looked into /var/log/Xorg.0.log and found many error messages, the first one being : (EE) open /dev/dri/card0: No such file or directory See Xorg log file and crash file attached. Then I looked at the output of 'lspci -vvnn' and it seems that no kernel driver manages the VGA Controller. See output of 'lspci -vvnn' attached According to the following message, the missing kernel driver may be : bochs-drm or virtio-vga https://www.redhat.com/archives/libvir-list/2015-August/msg00220.html # lsb_release -rd Description:Ubuntu 18.10 Release:18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] Re: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: New Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803123] Re: Xorg Crash information for bug #1802950
*** This bug is a duplicate of bug 1802950 *** https://bugs.launchpad.net/bugs/1802950 Unfortunately there is no crash information here so I am closing this bug as a duplicate of bug 1802950. ** This bug has been marked a duplicate of bug 1802950 X.org crashes after upgrade to 18.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1803123 Title: Xorg Crash information for bug #1802950 Status in xorg package in Ubuntu: New Bug description: Crash information for bug #1802950 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Nov 13 12:09:38 2018 DistUpgraded: 2018-11-12 00:10:48,691 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANGUAGE=fr_FR: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=d102c16e-db6d-44ff-8cac-7f933ab930c0 ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to cosmic on 2018-11-11 (1 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.11 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.11 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1803123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so
This bug is about sound only. If you want to talk about other things then please create new bugs for those. -- 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/1788471 Title: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so Status in pulseaudio package in Ubuntu: Expired Bug description: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 22:04:28 2018 InstallationDate: Installed on 2018-08-13 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.version: Default string dmi.sys.vendor: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I hope you can fix it. This is super annoying for me and also a security issue because I don't always notice that the dock got unresponsive and also the locking does not work properly. I often press 'super+L' and rush away from my desk and then later see that the laptop didn't properly lock. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell source package in Cosmic: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Disco: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803222] [NEW] keyboard
Public bug reported: my keyboard is not typing anymore after walking up from suspend ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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: Wed Nov 14 01:18:20 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:90b8] InstallationDate: Installed on 2018-11-08 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Sony Corporation SVF1421E2EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=9e5fff3a-5a47-425f-aff8-0e05ed437a1c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0250DA dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0250DA:bd07/19/2016:svnSonyCorporation:pnSVF1421E2EW:pvrC10JBKXD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVF1421E2EW dmi.product.version: C10JBKXD dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Nov 14 01:04:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1803222 Title: keyboard Status in xorg package in Ubuntu: New Bug description: my keyboard is not typing anymore after walking up from suspend ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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: Wed Nov 14 01:18:20 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:90b8] InstallationDate: Installed on 2018-11-08 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Sony Corporation SVF1421E2EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=9e5fff3a-5a47-425f-aff8-0e05ed437a1c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0250DA dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation
[Desktop-packages] [Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
@Seb - also I rebuilt gvfs locally for bionic with that upstream patch added and can confirm it does not segfault after that - would be happy to test your SRUd version and confirm it as well if needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf Status in gvfs package in Ubuntu: Fix Committed Bug description: * Impact gvfs can be made to segfault by being provided an invalid autorun.inf * Test Case Use the proof of concept from bellow to generate an invalid autorun.inf and place it on an usb drive, connect the drive to the computer, gvfs shouldn't hit a segfault * Regression potential Check that the autorun feature keeps working --- Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
@Seb - so there is an autorun.inf in the original tarball which can be used (I will attach it separately here as well) - and this reproduces the crash for me - I just copied it to a FAT formatted USB drive, plugged it in and then in dmesg: [ 40.361136] gvfs-udisks2-vo[1563]: segfault at 7f3c60a485e0 ip 7f3c6099ef86 sp 7ffe34884e10 error 4 in libpcre.so.3.13.3[7f3c60983000+7] [ 51.023933] gvfs-udisks2-vo[1805]: segfault at 7fb5ef2205e0 ip 7fb5ef176f86 sp 7fff3e059160 error 4 in libpcre.so.3.13.3[7fb5ef15b000+7] And eventually apport popped up as well (gvfs-udisks2-volume-monitor crashed with SIGSEGV in pcre_exec()). ** Attachment added: "autorun.inf" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+attachment/5212446/+files/autorun.inf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf Status in gvfs package in Ubuntu: Fix Committed Bug description: * Impact gvfs can be made to segfault by being provided an invalid autorun.inf * Test Case Use the proof of concept from bellow to generate an invalid autorun.inf and place it on an usb drive, connect the drive to the computer, gvfs shouldn't hit a segfault * Regression potential Check that the autorun feature keeps working --- Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery
Hello Brian, I tested totem 3.26.0-0ubuntu6.1 on amd64 arch. The create gallery works just fine. I'm not fully conversant on how to add a tag, so if I've done it wrong, feel free to bring me up to speed. Tags: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1798399 Title: totem silently fails to create screenshot gallery Status in totem package in Ubuntu: Fix Released Status in totem source package in Bionic: Fix Committed Status in totem source package in Cosmic: Fix Released Bug description: *Impact The gallery plugin/menu option doesn't work * Test case - open a video - open the menu and click on the gallery option - validate making a gallery with the default options -> the picked filename should exist and be a gallery if pictures from the video * Regression potential The changes are restricted to the screenshot plugin, so make sure that one works -- https://gitlab.gnome.org/GNOME/totem/issues/268 --- https://gitlab.gnome.org/GNOME/totem/merge_requests/18/ --- Package totem 3.26.0-0ubuntu6 totem 3.26.0 running on Ubuntu 18.04 silently fails to create screenshot gallery. I'm assuming that this has something to do with totem-video-thumbnailer. Steps to reproduce: totem-video-thumbnailer -g 20 inputvideo outputpng I can reproduce this result with both HEVC and AVC encoded videos. I haven't been able to test other codecs, but the error indicates the codec isn't the problem. totem 3.18.1 under Ubuntu 16.04 does not have this problem. Any further information required I will be happy to produce within my abilities. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-19 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: totem 3.26.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803208] [NEW] gnome-shell[4614]: gtk_action_observer_action_removed: assertion 'GTK_IS_ACTION_OBSERVER (observer)' failed
Public bug reported: GNOME Shell was unresponsive (could move my cursor and I think Shell elements were changing colour etc as I hovered over them but clicking anything didn't produce any actual effects) after trying to log into an email account on the Geary Flatpak and opening Firefox (Deb) pretty much simultaneously. Not sure this is reproducible. I checked `journalctl -r` and I had 150,000 repeats (in a short period of time) of `adam-thinkpad-t430 gnome-shell[4614]: gtk_action_observer_action_removed: assertion 'GTK_IS_ACTION_OBSERVER (observer)' failed`, I don't think this has come up in the logs aside from for that crash... Pretty sure that Shell is to blame, not Geary or Firefox... ``` $ flatpak info org.gnome.Geary/x86_64/stable Ref: app/org.gnome.Geary/x86_64/stable ID: org.gnome.Geary Arch: x86_64 Branch: stable Origin: flathub Collection ID: org.flathub.Stable Date: 2018-08-29 14:38:53 + Subject: Update for 0.12.4. (c4d8833e) Commit: c6deb6487b655567845fe8a71442c1d04841cc7064dbbf58c93e5164296a87e8 Parent: 5de6d62d384c0213ea3998249b9c28bcf0d75a17a1c52c29da85c7588ed0aa89 Location: /var/lib/flatpak/app/org.gnome.Geary/x86_64/stable/c6deb6487b655567845fe8a71442c1d04841cc7064dbbf58c93e5164296a87e8 Installed size: 6.9 MB Runtime: org.gnome.Platform/x86_64/3.28 Sdk: org.gnome.Sdk/x86_64/3.28 ``` ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 22:46:13 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-03 (467 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-21 (23 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic package-from-proposed third-party-packages ** Description changed: - GNOME Shell crashed after trying to log into an email account on the - Geary Flatpak and opening Firefox (Deb) pretty much simultaneously. + GNOME Shell was unresponsive (could move my cursor and I think Shell + elements were changing colour etc as I hovered over them but clicking + anything didn't produce any actual effects) after trying to log into an + email account on the Geary Flatpak and opening Firefox (Deb) pretty much + simultaneously. Not sure this is reproducible. I checked `journalctl -r` and I had 150,000 repeats (in a short period of time) of `adam-thinkpad-t430 gnome-shell[4614]: gtk_action_observer_action_removed: assertion 'GTK_IS_ACTION_OBSERVER (observer)' failed`, I don't think this has come up in the logs aside from for that crash... Pretty sure that Shell is to blame, not Geary or Firefox... ``` $ flatpak info org.gnome.Geary/x86_64/stable Ref: app/org.gnome.Geary/x86_64/stable ID: org.gnome.Geary Arch: x86_64 Branch: stable Origin: flathub Collection ID: org.flathub.Stable Date: 2018-08-29 14:38:53 + Subject: Update for 0.12.4. (c4d8833e) Commit: c6deb6487b655567845fe8a71442c1d04841cc7064dbbf58c93e5164296a87e8 Parent: 5de6d62d384c0213ea3998249b9c28bcf0d75a17a1c52c29da85c7588ed0aa89 Location: /var/lib/flatpak/app/org.gnome.Geary/x86_64/stable/c6deb6487b655567845fe8a71442c1d04841cc7064dbbf58c93e5164296a87e8 Installed size: 6.9 MB Runtime: org.gnome.Platform/x86_64/3.28 Sdk: org.gnome.Sdk/x86_64/3.28 ``` ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 22:46:13 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-03 (467 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-21 (23 days ago) -- 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/1803208 Title: gnome-shell[4614]: gtk_action_observer_action_removed: assertion 'GTK_IS_ACTION_OBSERVER (observer)' failed Status in gnome-shell package in Ubuntu: New Bug description: GNOME Shell was unresponsive (could move my cursor and I think Shell elements were changing colour etc as I hovered over them but clicking anything didn't produce any actual effects) after trying to log into an email account on the Geary Flatpak and opening Firefox (Deb) pretty much simultaneously. Not sure this is reproducible. I checked `journalctl -r` and I had 150,000 repeats (in a short period of time) of `adam-thinkpad-t430 gnome-shell[4614]:
[Desktop-packages] [Bug 1799293] Re: gnome session: Must ask twice to lock the screen
I've also had this issue and do not have auto-login enabled, it might be worth nothing that the upper panel from my second monitor has disappeared both times this has happened. -- 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/1799293 Title: gnome session: Must ask twice to lock the screen Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 18.10 (new install) 2) gdm3 3.30.1-1ubuntu5 Preconditions The session's user has auto-login enabled (i.e. the system starts and the user is not prompted for a password but directly presented with the desktop) 3) What should happen: Unlocked desktop is showing. Lock screen is invoked (via WIN+L or via top right corner menu) and the lock screen is engaged (that is, lock screen clock shade drops down and screen fades to dark). Pressing ENTER brings back the lock screen and the password is prompted. 4) What happens: First Win + L lets the system in a half locked state in which the contents of the desktop are seen although no interaction is possible. A second Win + L correctly invokes the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803207] [NEW] Missing alias for locale eo.UTF-8
Public bug reported: When downloading and running the latest kitty terminal with LANG=eo.UTF-8, I get an error that it can't find a composition for this locale. This is fixed by adding this line eo.UTF-8: eo_EO.UTF-8 to /usr/share/X11/locale/locale.alias ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libx11-data 2:1.6.7-1 [modified: usr/share/X11/locale/locale.alias] ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 15:07:11 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-11-07 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 007: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=dffdd333-04ee-4748-ab06-f138a6bf751a ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1803207 Title: Missing alias for locale eo.UTF-8 Status in libx11 package in Ubuntu: New Bug description: When downloading and running the latest kitty terminal with LANG=eo.UTF-8, I get an error that it can't find a composition for this locale. This is fixed by adding this line eo.UTF-8: eo_EO.UTF-8 to /usr/share/X11/locale/locale.alias ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libx11-data 2:1.6.7-1 [modified: usr/share/X11/locale/locale.alias] ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 15:07:11 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-11-07 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 007: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=dffdd333-04ee-4748-ab06-f138a6bf751a ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version:
[Desktop-packages] [Bug 1797769] Re: LCD backlight brighness reset to maximum after boot / resume / login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1797769 Title: LCD backlight brighness reset to maximum after boot / resume / login Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: The laptop LCD backlight brightness level is not preserved. The screen brightness always gets reset to 2-steps below the maximum level after login or resume from suspend. This is particularly annoying when working on battery, because after each resume, I have to make screen darker in order to preserve energy. It is possible to control brightness by keyboard buttons and by status-bar slider, so brightness control mostly works. The status-bar slider behaves a bit erratically when moved, but not sure if it is related. The problem seems to be not related to kernel version. The problem existed in 18.04 as well as 18.10. Hardware: Dell Precision 5520. Graphics driver: Intel, using integrated GPU. Nvidia card turned off on boot, no proprietary Nvidia drivers loaded. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 14:25:37 2018 DisplayManager: gdm3 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-04-12 (549 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.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-settings-daemon/+bug/1797769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788021] Re: changing keyborad brightness doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1788021 Title: changing keyborad brightness doesn't work Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Checking 'journalctl' I get this error message: gsd-power[1924]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Running on an Asus UX490UA (7th-gen Intel CPU), and before upgrading to 18.10 everything worked fine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.29.90.1-1~ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 21:22:13 2018 InstallationDate: Installed on 2018-08-15 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to cosmic on 2018-08-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1788021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
Hello Ioanna, or anyone else affected, Accepted ghostscript into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ghostscript/9.25~dfsg+1-0ubuntu0.16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: ghostscript (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: Fix Committed Bug description: [Impact] ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. [Test Case] To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck [Regression Potential] Might cause problems when upgrading or installing ghostscript or libgs9 [Other Info] This bug affects trusty and xenial. It is already fixed in bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Unfortunately I have no clue what triggers the bug as of yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell source package in Cosmic: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Disco: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803192] [NEW] Internal MIC stopped to work on 18.10
Public bug reported: After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the internal Mic stop to work. Everything works well (speakers, etc) however no more sound comes as entry from Internal Mic. I checked and she has chipset ALC269VB i update to alsa-driver 1.1.7 without success. i checked alsamixer and everything seems ok as with pavucontrol. I upgraded my laptop too to 18.10 and i have no issue with internal mic but i do not have the same chipset. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/1803192 Title: Internal MIC stopped to work on 18.10 Status in alsa-driver package in Ubuntu: New Bug description: After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the internal Mic stop to work. Everything works well (speakers, etc) however no more sound comes as entry from Internal Mic. I checked and she has chipset ALC269VB i update to alsa-driver 1.1.7 without success. i checked alsamixer and everything seems ok as with pavucontrol. I upgraded my laptop too to 18.10 and i have no issue with internal mic but i do not have the same chipset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1803192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792878] Re: gvfs lockup due to max number of connections
The issue is fixed in >= cosmic, the change is being SRUed to bionic ** Changed in: gvfs (Ubuntu) Importance: Undecided => High ** Changed in: gvfs (Ubuntu) Status: New => Fix Released ** Description changed: + * Impact + dav backend lockups if two files are opened. + + * Test case + + connect to a webdav share and opens more than 2 files + + * Regression potential + + the change is in the webdav backend, check that those shares still work + correctly + + + Currently, the default value of max-conns-per-host libsoup property is used, which causes dav backend lockups if two files are opened. see: https://gitlab.gnome.org/GNOME/gvfs/commit/7b991137b8a820f018ddaa970d54f91d1f411a0f I've managed to fix the problem by changig the code of Version 1.36 (current ubuntu version) an compile it. As long as the version of gvfs is not updated to a version with fixing the problem, the patch described in the link above should be backported into version 1.36. quit urgent for us 'cause our system is heavely dependend on webdav Thanks Ueli ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 17 10:02:36 2018 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792878 Title: gvfs lockup due to max number of connections Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact dav backend lockups if two files are opened. * Test case connect to a webdav share and opens more than 2 files * Regression potential the change is in the webdav backend, check that those shares still work correctly Currently, the default value of max-conns-per-host libsoup property is used, which causes dav backend lockups if two files are opened. see: https://gitlab.gnome.org/GNOME/gvfs/commit/7b991137b8a820f018ddaa970d54f91d1f411a0f I've managed to fix the problem by changig the code of Version 1.36 (current ubuntu version) an compile it. As long as the version of gvfs is not updated to a version with fixing the problem, the patch described in the link above should be backported into version 1.36. quit urgent for us 'cause our system is heavely dependend on webdav Thanks Ueli ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 17 10:02:36 2018 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1792878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803190] Re: non-empty directory will not delete
It's fixed in the cosmic version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1803190 Title: non-empty directory will not delete Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact Summary: Deleting a directory containing 1+ files doesn't succeed. Nautilus shows the directory as deleted, but upon refresh it reappears (it was never deleted). * Test case Connect to a smb share and delete a directory * Regression potential The change is in the smb backend, check that this work still work fine Reported on https://bugzilla.gnome.org/show_bug.cgi?id=792147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1803190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803190] [NEW] non-empty directory will not delete
Public bug reported: * Impact Summary: Deleting a directory containing 1+ files doesn't succeed. Nautilus shows the directory as deleted, but upon refresh it reappears (it was never deleted). * Test case Connect to a smb share and delete a directory * Regression potential The change is in the smb backend, check that this work still work fine Reported on https://bugzilla.gnome.org/show_bug.cgi?id=792147 ** Affects: gvfs (Ubuntu) Importance: High Status: Fix Released ** Changed in: gvfs (Ubuntu) Importance: Undecided => High ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1803190 Title: non-empty directory will not delete Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact Summary: Deleting a directory containing 1+ files doesn't succeed. Nautilus shows the directory as deleted, but upon refresh it reappears (it was never deleted). * Test case Connect to a smb share and delete a directory * Regression potential The change is in the smb backend, check that this work still work fine Reported on https://bugzilla.gnome.org/show_bug.cgi?id=792147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1803190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
@Alex, I've uploaded to disco and since I was doing a SRU for cosmic/bionic I included it there, would be nice if you could help with a better testcase though? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf Status in gvfs package in Ubuntu: Fix Committed Bug description: * Impact gvfs can be made to segfault by being provided an invalid autorun.inf * Test Case Use the proof of concept from bellow to generate an invalid autorun.inf and place it on an usb drive, connect the drive to the computer, gvfs shouldn't hit a segfault * Regression potential Check that the autorun feature keeps working --- Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
** Description changed: + * Impact + + gvfs can be made to segfault by being provided an invalid autorun.inf + + * Test Case + + Use the proof of concept from bellow to generate an invalid autorun.inf + and place it on an usb drive, connect the drive to the computer, gvfs + shouldn't hit a segfault + + * Regression potential + + Check that the autorun feature keeps working + + --- + Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh - $ ./PoC + $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf Status in gvfs package in Ubuntu: Fix Committed Bug description: * Impact gvfs can be made to segfault by being provided an invalid autorun.inf * Test Case Use the proof of concept from bellow to generate an invalid autorun.inf and place it on an usb drive, connect the drive to the computer, gvfs shouldn't hit a segfault * Regression potential Check that the autorun feature keeps working --- Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803186] Re: update to 1.38.1
The new version is in disco ** Changed in: gvfs (Ubuntu) Importance: Undecided => High ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1803186 Title: update to 1.38.1 Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact That's a standard GNOME bugfix update, we should includ eit * Test case Make sure nautilus handling of files, mounts, device is still correct. The SRU is a GNOME one so follows the standard GNOME testing * Regression potentiel The changes are limited, mostly to camera and smb handling so those backend need the most testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1803186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803186] [NEW] update to 1.38.1
Public bug reported: * Impact That's a standard GNOME bugfix update, we should includ eit * Test case Make sure nautilus handling of files, mounts, device is still correct. The SRU is a GNOME one so follows the standard GNOME testing * Regression potentiel The changes are limited, mostly to camera and smb handling so those backend need the most testing ** Affects: gvfs (Ubuntu) Importance: High Status: Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1803186 Title: update to 1.38.1 Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact That's a standard GNOME bugfix update, we should includ eit * Test case Make sure nautilus handling of files, mounts, device is still correct. The SRU is a GNOME one so follows the standard GNOME testing * Regression potentiel The changes are limited, mostly to camera and smb handling so those backend need the most testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1803186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
** Changed in: gvfs (Ubuntu) Importance: Undecided => High ** Changed in: gvfs (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf Status in gvfs package in Ubuntu: Fix Committed Bug description: * Impact gvfs can be made to segfault by being provided an invalid autorun.inf * Test Case Use the proof of concept from bellow to generate an invalid autorun.inf and place it on an usb drive, connect the drive to the computer, gvfs shouldn't hit a segfault * Regression potential Check that the autorun feature keeps working --- Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1433984] Re: nautilus crashed with SIGSEGV in discovered_cb()
Hello emk2203, or anyone else affected, Accepted totem into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/totem/3.26.0-0ubuntu6.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: totem (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1433984 Title: nautilus crashed with SIGSEGV in discovered_cb() Status in Totem: Expired Status in nautilus package in Ubuntu: Confirmed Status in totem package in Ubuntu: Fix Released Status in totem source package in Bionic: Fix Committed Bug description: * Impact nautilus segfaults sometime when closing the property dialog on a video * Test case - open nautilus - open the file properties of a mp3 - close the dialog nautilus should not segfault (close directly by hitting esc to increase the chances to hit the bug) the errors should also stop with the new version https://errors.ubuntu.com/problem/d154b3cfc3985b5a6c5c8f1b1e2dfc670aa1e5d7 * Regression potential The changes are in the nautilus properties page, check that this one still works correctly --- Tried to open a file ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: totem 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 10:23:11 2015 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2011-10-03 (1263 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcCmdline: nautilus -n ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 LANGUAGE=de_DE XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f04073a4c2b:mov(%rcx),%rdi PC (0x7f04073a4c2b) ok source "(%rcx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown Title: nautilus crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to vivid on 2014-12-24 (84 days ago) UserGroups: adm admin bumblebee cdrom dialout lpadmin plugdev sambashare scanner To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1433984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798399] Please test proposed package
Hello George, or anyone else affected, Accepted totem into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/totem/3.26.0-0ubuntu6.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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1798399 Title: totem silently fails to create screenshot gallery Status in totem package in Ubuntu: Fix Released Status in totem source package in Bionic: Fix Committed Status in totem source package in Cosmic: Fix Released Bug description: *Impact The gallery plugin/menu option doesn't work * Test case - open a video - open the menu and click on the gallery option - validate making a gallery with the default options -> the picked filename should exist and be a gallery if pictures from the video * Regression potential The changes are restricted to the screenshot plugin, so make sure that one works -- https://gitlab.gnome.org/GNOME/totem/issues/268 --- https://gitlab.gnome.org/GNOME/totem/merge_requests/18/ --- Package totem 3.26.0-0ubuntu6 totem 3.26.0 running on Ubuntu 18.04 silently fails to create screenshot gallery. I'm assuming that this has something to do with totem-video-thumbnailer. Steps to reproduce: totem-video-thumbnailer -g 20 inputvideo outputpng I can reproduce this result with both HEVC and AVC encoded videos. I haven't been able to test other codecs, but the error indicates the codec isn't the problem. totem 3.18.1 under Ubuntu 16.04 does not have this problem. Any further information required I will be happy to produce within my abilities. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-19 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: totem 3.26.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery
@Daniel - it's written here - https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: totem (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1798399 Title: totem silently fails to create screenshot gallery Status in totem package in Ubuntu: Fix Released Status in totem source package in Bionic: Fix Committed Status in totem source package in Cosmic: Fix Released Bug description: *Impact The gallery plugin/menu option doesn't work * Test case - open a video - open the menu and click on the gallery option - validate making a gallery with the default options -> the picked filename should exist and be a gallery if pictures from the video * Regression potential The changes are restricted to the screenshot plugin, so make sure that one works -- https://gitlab.gnome.org/GNOME/totem/issues/268 --- https://gitlab.gnome.org/GNOME/totem/merge_requests/18/ --- Package totem 3.26.0-0ubuntu6 totem 3.26.0 running on Ubuntu 18.04 silently fails to create screenshot gallery. I'm assuming that this has something to do with totem-video-thumbnailer. Steps to reproduce: totem-video-thumbnailer -g 20 inputvideo outputpng I can reproduce this result with both HEVC and AVC encoded videos. I haven't been able to test other codecs, but the error indicates the codec isn't the problem. totem 3.18.1 under Ubuntu 16.04 does not have this problem. Any further information required I will be happy to produce within my abilities. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-19 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: totem 3.26.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1552792] Please test proposed package
Hello Kev, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.7 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. -- 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/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in packagekit source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785240] Re: Cancelling snapd authorization triggers error notification
Hello Andrea, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.7 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. ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- 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/1785240 Title: Cancelling snapd authorization triggers error notification Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Bug description: To reproduce: 1. Open gnome-software 2. Try to install a snap application 3. Cancel the polkit authorization Expected results: Nothing happens Actual results: An error notification is shown as per attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1785240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
Hello Kev, or anyone else affected, Accepted packagekit into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/packagekit/1.1.9-1ubuntu2.18.04.4 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. ** Tags added: verification-needed verification-needed-bionic -- 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/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in packagekit source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801757] Re: all app indicators disappear
Just discovered the typing Alt-F2 r RET brings the app indicators back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Occasionally all of my app indicators just disappear. Right now, for example the only icons in my top bar are the wifi icon, the volume icon, and the battery charge icon. Everything else is gone. The applications associated with the missing indicators, e.g., Dropbox, Cloud Station Drive, Pritunl, Shutter, are still running, but their app indicators are no longer there. The only way I've found to get them back is to log out and log back in. I have no idea what provokes this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 11:37:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (39 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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-extension-appindicator/+bug/1801757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803176] Re: Search in Nautilus does not work correctly when called from other apps
I've attached this screencast to help visualize this behavior. ** Attachment added: "Screencast 2018-11-13 13:15:31.mp4" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1803176/+attachment/5212390/+files/Screencast%202018-11-13%2013%3A15%3A31.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1803176 Title: Search in Nautilus does not work correctly when called from other apps Status in nautilus package in Ubuntu: New Bug description: When Nautilus is called from another app, e.g., Thunderbird > Attach File to email (or Gedit > Save file) the search (via the magnifying glass icon in the top right) only allows for 1 character to be entered, and then jumps to the bottom right and subsequent characters appear there. This behavior, of course, messes up the expected search results as the search is split into two fields/areas of the panel. In contrast, when opening up a Nautilus browser panel directly, any search query entered from the magnifying glass icon stays in the text entry area as expected, and the search results work well. The expectation is that when another app calls Nautilus, the search function works as if it does when working directly out of Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 13:05:42 2018 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'1165x787+417+87'" b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-10-27 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1803176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803176] [NEW] Search in Nautilus does not work correctly when called from other apps
Public bug reported: When Nautilus is called from another app, e.g., Thunderbird > Attach File to email (or Gedit > Save file) the search (via the magnifying glass icon in the top right) only allows for 1 character to be entered, and then jumps to the bottom right and subsequent characters appear there. This behavior, of course, messes up the expected search results as the search is split into two fields/areas of the panel. In contrast, when opening up a Nautilus browser panel directly, any search query entered from the magnifying glass icon stays in the text entry area as expected, and the search results work well. The expectation is that when another app calls Nautilus, the search function works as if it does when working directly out of Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 13:05:42 2018 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'1165x787+417+87'" b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-10-27 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1803176 Title: Search in Nautilus does not work correctly when called from other apps Status in nautilus package in Ubuntu: New Bug description: When Nautilus is called from another app, e.g., Thunderbird > Attach File to email (or Gedit > Save file) the search (via the magnifying glass icon in the top right) only allows for 1 character to be entered, and then jumps to the bottom right and subsequent characters appear there. This behavior, of course, messes up the expected search results as the search is split into two fields/areas of the panel. In contrast, when opening up a Nautilus browser panel directly, any search query entered from the magnifying glass icon stays in the text entry area as expected, and the search results work well. The expectation is that when another app calls Nautilus, the search function works as if it does when working directly out of Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 13:05:42 2018 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'1165x787+417+87'" b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-10-27 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1803176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so
Hello I forgot how to report a bug. Can you help me? I updated my GPD pocket to Ubuntu 18.10 cosmic (x86-64). I tried ubuntu, cinnamon. Everything works fine. The problem is one. It is very difficult to turn on or restart the PC. I can turn on only after many tests. When I press the restart, the PC shuts down and needs to press again to turn on. I can turn on only after many attempts. I will be grateful for the help. Jonas zika...@gmail.com 2018-10-31, tr, 06:26 Launchpad Bug Tracker <1788...@bugs.launchpad.net> rašė: > [Expired for pulseaudio (Ubuntu) because there has been no activity for > 60 days.] > > ** Changed in: pulseaudio (Ubuntu) >Status: Incomplete => Expired > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1788471 > > Title: > There is no sound when you turn on the tube. Sometimes the sound is. I > do not understand why this is so > > Status in pulseaudio package in Ubuntu: > Expired > > Bug description: > There is no sound when you turn on the tube. Sometimes the sound is. I > do not understand why this is so > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: pulseaudio 1:11.1-1ubuntu7.1 > Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', > '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', > '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', > '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit > code 1: > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 22 22:04:28 2018 > InstallationDate: Installed on 2018-08-13 (8 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 > (20180105.1) > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > SourcePackage: pulseaudio > Symptom: audio > UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago) > dmi.bios.date: 08/07/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 5.11 > dmi.board.asset.tag: Default string > dmi.board.name: Default string > dmi.board.vendor: AMI Corporation > dmi.board.version: Default string > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: Default string > dmi.product.name: Default string > dmi.product.version: Default string > dmi.sys.vendor: Default string > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788471/+subscriptions > -- 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/1788471 Title: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so Status in pulseaudio package in Ubuntu: Expired Bug description: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 22:04:28 2018 InstallationDate: Installed on 2018-08-13 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Desktop-packages] [Bug 1740894] [xkeyboard-config/cosmic] possible regression found
As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of xkeyboard-config from cosmic- proposed was performed and bug 1800727 was found. Please investigate that bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed-cosmic" tag from this bug report and add the tag "bot-stop-nagging" to bug 1800727 (not this bug). Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1674089] Re: Tamil 99 keyboard layout
This bug was fixed in the package language-selector - 0.191 --- language-selector (0.191) disco; urgency=medium * data/pkg_depends: Pull ibus-m17n for Tamil to bring tamil99 (LP: #1674089). -- Gunnar Hjalmarsson Tue, 13 Nov 2018 18:07:00 +0100 ** Changed in: language-selector (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1674089 Title: Tamil 99 keyboard layout Status in ibus-m17n package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Fix Released Status in ibus-m17n source package in Disco: Invalid Status in language-selector source package in Disco: Fix Released Bug description: Tamil 99 keyboard layout which is the default keyboard layout prescribed by the Indian State of Tamil Nadu is not present. Selecting Tamil layout selects the Tamil Inscript layout which is prescribed by the Government of India. However, considering that Tamil is used only in the state of Tamil Nadu and that most keyboards are manufactured with Tamil 99, the layout by the Tamil Nadu government is the only one sold currently (usually by a company called TVS-e). This can be verified by Googling for Tamil+English bilingual keyboards. The current Inscript layout is useless for actual users and the lack of Tamil 99 layout forces people to switch to Google Input tools. I have observed this on Ubuntu 16.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/1674089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798053] [gnome-software/cosmic] possible regression found
As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of gnome-software from cosmic- proposed was performed and bug 1800286 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed-cosmic" tag from this bug report and add the tag "bot-stop-nagging" to bug 1800286 (not this bug). Thanks! ** Tags added: verification-failed-cosmic -- 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/1798053 Title: [SRU] Click on the back icon in gnome-software doesn't work Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Cosmic: Fix Released Bug description: [Test Case] 1. Open gnome-software 2. Press Ctrl+F and type "firefox" or any string that will return results 3. Click any result in the list (snap package or deb, already installed or not, it doesn't matter) 4. Observe that a new page is open showing details about the application 5. Close gnome-software 6. Open gnome-software again 7. Observe that the application is open on the last open page (details view about the application) 8. Click the back button (top-left corner) Expected result: the application goes back to the list of search results (or perhaps to the home screen) Current result: nothing happens Please note that the upstream fix reverts a new behaviour and as a result, when opening again gnome-software at step 6, the application opens on the home screen instead of resuming the last open page. This is consistent with how gnome-software behaves in bionic. So after applying the patch, steps 7 and 8 can be folded into one single step: "Observe that the application is open on the home screen". [Regression Potential] Low. This is a cherry-pick of a self-contained trivial upstream commit that is already released in gnome-software 3.30.3 (https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774). As noted above, it does change the behaviour of re-opening the application after closing it, but it reverts it to the behaviour it had in bionic, so I don't think it should be considered a regression. Re-opening the application after closing it in a number of different situations should be thoroughly exercised to make sure that this doesn't introduce any functional regression. [Original Description] Searched for Chromium, installed Chromium (snap version), clicked Launched and used chromium. Went back to gnome-software and clicked the back button. Nothing happened. Restarted gnome-software and clicked the back button. Nothing happened. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu3 [modified: usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini] ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 11:22:16 2018 InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu3 LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181016) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803149] Re: Update to 2.2.9
OdyX, can you do the 2.2.9 for Debian, so that it syncs into Ubuntu? Thanks. -- 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/1803149 Title: Update to 2.2.9 Status in cups package in Ubuntu: Triaged Bug description: There is a new 2.2.9 version available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1803149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Bug description: On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that Nautilus displays "Empty Folder" when clicking "Windows Network" Nautilus should show smbtree nad host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor) smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the processing engine) smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5708) smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo) smb-network: send_reply(0x55b19a2e7820), failed=0 () smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708) smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate) smb-network: send_reply(0x55b19a2c30c0), failed=0 () Proposed solution: Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394 which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe NT1 which most users are doing to correct this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630905] Re: Loss of lan connection causes applications using gvfsd-sftp to hang until demon is killed
** Description changed: + * Impact + + The gvfsd-sftp service sometime hangs + + * Test case + - connect to a ssh server from nautilus + - suspend the computer for longer than the ssh timeout (1 hour for example) + - resume and try to use the connection + + * Regression potential + Check that nautilus access to remote servers still work correctly + + - + + This affects an installation of Ubuntu 14.04 on a Lenovo laptop. - When applications like nautilus or Bluefish are connected to a remote fileshare using sftp (ssh) via a lan connection, if the connection is lost and re-established the old process seems to hang blocking attempts to save data or use Nautilus in any way. + When applications like nautilus or Bluefish are connected to a remote fileshare using sftp (ssh) via a lan connection, if the connection is lost and re-established the old process seems to hang blocking attempts to save data or use Nautilus in any way. This typically occurs when the connection is either lost accidentally or when the laptop is suspended and then unsuspended causing a loss of wireless connection. The workaround is to kill the gvsftp process manually and then recreate the remote connection using Nautilus. This bug leads to data loss if, for instance, the laptop is closed (starting suspend mode) while in the middle of a task that must be saved. ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: called for pid 3309, signal 6, core limit 0 ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: executable: /usr/lib/gvfs/gvfsd-sftp (command line "/usr/lib/gvfs/gvfsd-sftp --spawner :1.4 /org/gtk/gvfs/exec_spaw/28") ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: debug: session gdbus call: (true,) ERROR: apport (pid 5064) Thu Oct 6 17:38:30 2016: wrote report /var/crash/_usr_lib_gvfs_gvfsd-sftp.1000.crash Description: Ubuntu 14.04.5 LTS Release: 14.04 - gvfs: - Installed: 1.20.3-0ubuntu1.2 - Candidate: 1.20.3-0ubuntu1.2 - Version table: - *** 1.20.3-0ubuntu1.2 0 - 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.20.1-1ubuntu1 0 - 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + Installed: 1.20.3-0ubuntu1.2 + Candidate: 1.20.3-0ubuntu1.2 + Version table: + *** 1.20.3-0ubuntu1.2 0 + 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1.20.1-1ubuntu1 0 + 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1630905 Title: Loss of lan connection causes applications using gvfsd-sftp to hang until demon is killed Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact The gvfsd-sftp service sometime hangs * Test case - connect to a ssh server from nautilus - suspend the computer for longer than the ssh timeout (1 hour for example) - resume and try to use the connection * Regression potential Check that nautilus access to remote servers still work correctly - This affects an installation of Ubuntu 14.04 on a Lenovo laptop. When applications like nautilus or Bluefish are connected to a remote fileshare using sftp (ssh) via a lan connection, if the connection is lost and re-established the old process seems to hang blocking attempts to save data or use Nautilus in any way. This typically occurs when the connection is either lost accidentally or when the laptop is suspended and then unsuspended causing a loss of wireless connection. The workaround is to kill the gvsftp process manually and then recreate the remote connection using Nautilus. This bug leads to data loss if, for instance, the laptop is closed (starting suspend mode) while in the middle of a task that must be saved. ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: called for pid 3309, signal 6, core limit 0 ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: executable: /usr/lib/gvfs/gvfsd-sftp (command line "/usr/lib/gvfs/gvfsd-sftp --spawner :1.4 /org/gtk/gvfs/exec_spaw/28") ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: debug: session gdbus call: (true,) ERROR: apport (pid 5064) Thu Oct 6 17:38:30 2016: wrote report /var/crash/_usr_lib_gvfs_gvfsd-sftp.1000.crash Description: Ubuntu 14.04.5 LTS Release: 14.04 gvfs: Installed: 1.20.3-0ubuntu1.2 Candidate: 1.20.3-0ubuntu1.2 Version table: *** 1.20.3-0ubuntu1.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.20.1-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about
[Desktop-packages] [Bug 1674089] Re: Tamil 99 keyboard layout
** Changed in: language-selector (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1674089 Title: Tamil 99 keyboard layout Status in ibus-m17n package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Fix Committed Status in ibus-m17n source package in Disco: Invalid Status in language-selector source package in Disco: Fix Committed Bug description: Tamil 99 keyboard layout which is the default keyboard layout prescribed by the Indian State of Tamil Nadu is not present. Selecting Tamil layout selects the Tamil Inscript layout which is prescribed by the Government of India. However, considering that Tamil is used only in the state of Tamil Nadu and that most keyboards are manufactured with Tamil 99, the layout by the Tamil Nadu government is the only one sold currently (usually by a company called TVS-e). This can be verified by Googling for Tamil+English bilingual keyboards. The current Inscript layout is useless for actual users and the lack of Tamil 99 layout forces people to switch to Google Input tools. I have observed this on Ubuntu 16.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/1674089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630905] Re: Loss of lan connection causes applications using gvfsd-sftp to hang until demon is killed
There was a similar issue fixed in https://gitlab.gnome.org/GNOME/gvfs/commit/1b591b50c338c974d11a53d31356475dcda8bfcd That's in cosmic and backported to bionic ** Changed in: gvfs (Ubuntu) Importance: Undecided => High ** Changed in: gvfs (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1630905 Title: Loss of lan connection causes applications using gvfsd-sftp to hang until demon is killed Status in gvfs package in Ubuntu: Fix Released Bug description: This affects an installation of Ubuntu 14.04 on a Lenovo laptop. When applications like nautilus or Bluefish are connected to a remote fileshare using sftp (ssh) via a lan connection, if the connection is lost and re-established the old process seems to hang blocking attempts to save data or use Nautilus in any way. This typically occurs when the connection is either lost accidentally or when the laptop is suspended and then unsuspended causing a loss of wireless connection. The workaround is to kill the gvsftp process manually and then recreate the remote connection using Nautilus. This bug leads to data loss if, for instance, the laptop is closed (starting suspend mode) while in the middle of a task that must be saved. ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: called for pid 3309, signal 6, core limit 0 ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: executable: /usr/lib/gvfs/gvfsd-sftp (command line "/usr/lib/gvfs/gvfsd-sftp --spawner :1.4 /org/gtk/gvfs/exec_spaw/28") ERROR: apport (pid 5064) Thu Oct 6 17:38:29 2016: debug: session gdbus call: (true,) ERROR: apport (pid 5064) Thu Oct 6 17:38:30 2016: wrote report /var/crash/_usr_lib_gvfs_gvfsd-sftp.1000.crash Description: Ubuntu 14.04.5 LTS Release: 14.04 gvfs: Installed: 1.20.3-0ubuntu1.2 Candidate: 1.20.3-0ubuntu1.2 Version table: *** 1.20.3-0ubuntu1.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.20.1-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1630905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
The fix is in https://launchpad.net/ubuntu/+source/gvfs/1.38.1-1ubuntu1 And being backported to cosmic and bionic ** Changed in: gvfs (Ubuntu) Importance: Undecided => Low ** Changed in: gvfs (Ubuntu) Status: Confirmed => Fix Released ** Description changed: - On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of - that Nautilus displays "Empty Folder" when clicking "Windows Network" + * Impact + On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that Nautilus displays "Empty Folder" when clicking "Windows Network" + + * Test case + Try to browse a smb share from a bionic client + + * Regression potential + Check that smb browsing/mounts still work as they should + + --- Nautilus should show smbtree nad host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor) smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the processing engine) smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5708) smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo) smb-network: send_reply(0x55b19a2e7820), failed=0 () smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708) smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate) smb-network: send_reply(0x55b19a2c30c0), failed=0 () Proposed solution: Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394 which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe NT1 which most users are doing to correct this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Invalid Bug description: * Impact On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that Nautilus displays "Empty Folder" when clicking "Windows Network" * Test case Try to browse a smb share from a bionic client * Regression potential Check that smb browsing/mounts still work as they should --- Nautilus should show smbtree nad host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor) smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the processing engine) smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5708) smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo) smb-network: send_reply(0x55b19a2e7820), failed=0 () smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708) smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate) smb-network: send_reply(0x55b19a2c30c0), failed=0 () Proposed solution: Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394 which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe NT1 which most users are doing to correct this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797421] Re: Hebrew layout in Onboard Keyboard lacks some letters
** Also affects: libmatekbd (Ubuntu) Importance: Undecided Status: New ** No longer affects: libmatekbd (Ubuntu) ** Also affects: onboard (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1797421 Title: Hebrew layout in Onboard Keyboard lacks some letters Status in onboard package in Ubuntu: New Bug description: The Hebrew keyboard layout is missing several letters when used on systems with low resolutions. In my case the system is an HTPC connected to an HD TV at 1360 by 768 resolution. On higher resolutions (checked with a 22" Samsung monitor running at 1920 by 1200) this problem does not manifest itself. Both systems running Ubuntu Mate 18.04. Attached screenshots illustrate the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1797421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773114] Re: Cannot copy file using 'cp' on a gvfs mount
Could be the same as https://bugzilla.gnome.org/show_bug.cgi?id=795805, is that a SMB2 mount? ** Changed in: gvfs (Ubuntu) Importance: Undecided => High ** Bug watch added: GNOME Bug Tracker #795805 https://bugzilla.gnome.org/show_bug.cgi?id=795805 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1773114 Title: Cannot copy file using 'cp' on a gvfs mount Status in gvfs package in Ubuntu: Confirmed Bug description: On Ubuntu 18.04, I can't anymore copy a file using the 'cp' command on a gvfs smb mount. For example, If I try to copy the file test.odp on a SMB shared folder, like this: cp -v test.odp /run/user/1000/gvfs/smb- share:domain=X,server=x,share=xxx,user=x/ I get the following error: cp: cannot fstat '/run/user/1000/gvfs/smb- share:domain=X,server=x,share=xxx,user=x//test.odp': Invalid argument A file 'test.odp' is created, but with size 0. I can delete any file on the shared folder using the 'rm' command. If I copy the file using the command 'gio copy', then it works as expected. This used to work in Ubuntu 16.04. Of course, I don't know if the problem is in the gvfs package or in some underlying component... System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit Kernel: 4.15.0-22-generic x86_64 Package: gvfs 1.36.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1773114/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803158] Re: Copying file to Windows server (SMB2) via gvfsd-fuse and gvfsd-smb fails with EINVAL
The issue is fixed in cosmic, let's SRU to bionic ** Changed in: gvfs (Ubuntu) Importance: Undecided => Low ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1803158 Title: Copying file to Windows server (SMB2) via gvfsd-fuse and gvfsd-smb fails with EINVAL Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact If a share on a Windows file server (not a Samba server) is mounted and uses the SMB2 protocol, any attempt to copy or create a file for writing (e.g. using the cp or cat commands from the bash shell) on the mount point via FUSE will create a zero-length file but the open will return with an EINVAL error. * Test case - mount a sahre using smb2 - try to copy a file on the mount from e.g a command line * Regression potential Check that samba interactions keep working as they should The bug was reported upstream on https://bugzilla.gnome.org/show_bug.cgi?id=795805 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1803158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802039] Re: Firefox without titlebar has visual glitches when maximizing/unmaximizing
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- 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/1802039 Title: Firefox without titlebar has visual glitches when maximizing/unmaximizing Status in firefox package in Ubuntu: New Bug description: There is a relatively new feature in Firefox that allows you to hide the title bar (I'm running Firefox 63.0), which is very helpful when you have a low resolution screen. However, when changing the maximization state, some visual gitches occur. I didn't notice this glitching when running Kubuntu or Ubuntu Budgie on two separate systems. To try this, go to your Firefox Menu, click Customize, and uncheck "Title Bar" at the bottom left. Then unmaximize the window and then remaximize it. What it's supposed to look like: https://pasteboard.co/HM0h8oB.png Unmaximized (note the large transparent section): https://pasteboard.co/HM0hpud.png Remaximized (note the duplicate set of close buttons): https://pasteboard.co/HM0hCf5.png Also another interesting bug I noticed...if you try to use Firefox in the no titlebar state with the global menu enabled (e.g. Contemporary, Cupertino, or Mutiny panel layouts), the window buttons are not placed correctly, being on the window border. Systems tried on: Laptop, Dell Latitude E5430 - Intel Core i3-3120M dual core with hyperthreading, 12 GB DDR3 Memory, Intel 4000 Graphics, Built-in LCD at 1366x768 (screenshots from this system) Desktop, Lenovo ThinkCentre M79 - AMD A4-6300B 3.7 GHz dual core, 8 GB DDR3 Memory, AMD 8370D Graphics, HP 2009f Monitor at 1600x900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1802039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803158] [NEW] Copying file to Windows server (SMB2) via gvfsd-fuse and gvfsd-smb fails with EINVAL
Public bug reported: * Impact If a share on a Windows file server (not a Samba server) is mounted and uses the SMB2 protocol, any attempt to copy or create a file for writing (e.g. using the cp or cat commands from the bash shell) on the mount point via FUSE will create a zero-length file but the open will return with an EINVAL error. * Test case - mount a sahre using smb2 - try to copy a file on the mount from e.g a command line * Regression potential Check that samba interactions keep working as they should The bug was reported upstream on https://bugzilla.gnome.org/show_bug.cgi?id=795805 ** Affects: gvfs (Ubuntu) Importance: Low Status: Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1803158 Title: Copying file to Windows server (SMB2) via gvfsd-fuse and gvfsd-smb fails with EINVAL Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact If a share on a Windows file server (not a Samba server) is mounted and uses the SMB2 protocol, any attempt to copy or create a file for writing (e.g. using the cp or cat commands from the bash shell) on the mount point via FUSE will create a zero-length file but the open will return with an EINVAL error. * Test case - mount a sahre using smb2 - try to copy a file on the mount from e.g a command line * Regression potential Check that samba interactions keep working as they should The bug was reported upstream on https://bugzilla.gnome.org/show_bug.cgi?id=795805 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1803158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1674089] Re: Tamil 99 keyboard layout
Well, the ibus-m17n package does provide a tamil99 input method, so unless I'm missing something, you can install ibus-m17n, relogin, and add the "Tamil (tamil99 (m17n))" input source. One thing that could be done is to let language-selector's pkg_depends pull ibus-m17n when the Tamil language is installed. That should bring ibus-m17n (which is a main package) in case of a Tamil install if there is an Internet connection. Adding a language-selector task. ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Changed in: ibus-m17n (Ubuntu Disco) Importance: High => Undecided ** Changed in: ibus-m17n (Ubuntu Disco) Status: New => Invalid ** Changed in: ibus-m17n (Ubuntu Disco) Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned) ** Changed in: language-selector (Ubuntu Disco) Importance: Undecided => High ** Changed in: language-selector (Ubuntu Disco) Status: New => In Progress ** Changed in: language-selector (Ubuntu Disco) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-m17n in Ubuntu. https://bugs.launchpad.net/bugs/1674089 Title: Tamil 99 keyboard layout Status in ibus-m17n package in Ubuntu: Invalid Status in language-selector package in Ubuntu: In Progress Status in ibus-m17n source package in Disco: Invalid Status in language-selector source package in Disco: In Progress Bug description: Tamil 99 keyboard layout which is the default keyboard layout prescribed by the Indian State of Tamil Nadu is not present. Selecting Tamil layout selects the Tamil Inscript layout which is prescribed by the Government of India. However, considering that Tamil is used only in the state of Tamil Nadu and that most keyboards are manufactured with Tamil 99, the layout by the Tamil Nadu government is the only one sold currently (usually by a company called TVS-e). This can be verified by Googling for Tamil+English bilingual keyboards. The current Inscript layout is useless for actual users and the lack of Tamil 99 layout forces people to switch to Google Input tools. I have observed this on Ubuntu 16.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/1674089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1010000] Re: gedit hangs when opening files padded with null characters
Reported upstream: https://gitlab.gnome.org/GNOME/gedit/issues/95 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/101 Title: gedit hangs when opening files padded with null characters Status in gedit package in Ubuntu: Confirmed Bug description: Opening the attached file using gedit 3.4.1 causes gedit to hang. The file opens correclty using medit and LibreOffice Calc. This file comes from a data logger that uses fixed length files, padding the unused area at the end of the file with null characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802911] Re: [snap] LibreOffice 6.1.3.2 (90) doesn't launch
FYI, '@{PROC}/version r,' is in the default apparmor template.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1802911
Title:
[snap] LibreOffice 6.1.3.2 (90) doesn't launch
Status in libreoffice package in Ubuntu:
Invalid
Bug description:
LibreOffice doesn't launch on 6.1.3.2 (90) in `candidate` on core
16-2.36.1+git1007.f72779e (5920) in `edge`, it just hangs, with no
Terminal output, but has the following denials in `journalctl -f`:
```
Nov 12 12:38:19 adam-thinkpad-t430 audit[31984]: AVC apparmor="DENIED"
operation="open" profile="snap-update-ns.libreoffice" name="/proc/version"
pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Nov 12 12:38:19 adam-thinkpad-t430 kernel: audit: type=1400
audit(1542026299.589:542): apparmor="DENIED" operation="open"
profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
```
```
$ snap info libreoffice
tracking: candidate
refresh-date: 6 days ago, at 08:50 GMT
channels:
stable:6.1.2.1 (86) 501MB -
candidate: 6.1.3.2 (90) 507MB - <
beta: ↑
edge: ↑
installed: 6.1.3.2 (90) 507MB -
$ snap version
snap2.36.1+git1007.f72779e~ubuntu16.04.1
snapd 2.36.1+git1007.f72779e~ubuntu16.04.1
series 16
ubuntu 18.10
kernel 4.18.0-11-generic
$ snap info core
tracking: edge
refresh-date: today at 12:08 GMT
channels:
stable:16-2.35.5 (5742) 92MB -
candidate: 16-2.35.5 (5742) 92MB -
beta: 16-2.36.1 (5897) 92MB -
edge: 16-2.36.1+git1007.f72779e (5920) 92MB -<
installed: 16-2.36.1+git1007.f72779e (5920) 92MB core
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802911/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803149] [NEW] Update to 2.2.9
Public bug reported: There is a new 2.2.9 version available ** Affects: cups (Ubuntu) Importance: Wishlist Assignee: Till Kamppeter (till-kamppeter) Status: Triaged ** Tags: upgrade-software-version ** Changed in: cups (Ubuntu) Status: New => Triaged -- 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/1803149 Title: Update to 2.2.9 Status in cups package in Ubuntu: Triaged Bug description: There is a new 2.2.9 version available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1803149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1433984] Re: nautilus crashed with SIGSEGV in discovered_cb()
The bug was fixed in 3.26.2 in cosmic, the errors summary confirms there is no report on this serie, I've uploaded a SRU to bionic now ** Description changed: + * Impact + nautilus segfaults sometime when closing the property dialog on a video + + * Test case + + - open nautilus + - open the file properties of a mp3 + - close the dialog + + nautilus should not segfault (close directly by hitting esc to increase + the chances to hit the bug) + + the errors should also stop with the new version https://errors.ubuntu.com/problem/d154b3cfc3985b5a6c5c8f1b1e2dfc670aa1e5d7 + * Regression potential + + The changes are in the nautilus properties page, check that this one still works correctly --- Tried to open a file ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: totem 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 10:23:11 2015 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2011-10-03 (1263 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcCmdline: nautilus -n ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 LANGUAGE=de_DE XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f04073a4c2b:mov(%rcx),%rdi PC (0x7f04073a4c2b) ok source "(%rcx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown Title: nautilus crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to vivid on 2014-12-24 (84 days ago) UserGroups: adm admin bumblebee cdrom dialout lpadmin plugdev sambashare scanner ** Changed in: totem (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1433984 Title: nautilus crashed with SIGSEGV in discovered_cb() Status in Totem: Expired Status in nautilus package in Ubuntu: Confirmed Status in totem package in Ubuntu: Fix Released Bug description: * Impact nautilus segfaults sometime when closing the property dialog on a video * Test case - open nautilus - open the file properties of a mp3 - close the dialog nautilus should not segfault (close directly by hitting esc to increase the chances to hit the bug) the errors should also stop with the new version https://errors.ubuntu.com/problem/d154b3cfc3985b5a6c5c8f1b1e2dfc670aa1e5d7 * Regression potential The changes are in the nautilus properties page, check that this one still works correctly --- Tried to open a file ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: totem 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 10:23:11 2015 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2011-10-03 (1263 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcCmdline: nautilus -n ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 LANGUAGE=de_DE XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f04073a4c2b:mov(%rcx),%rdi PC (0x7f04073a4c2b) ok source "(%rcx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown Title: nautilus crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to vivid on 2014-12-24 (84 days ago) UserGroups: adm admin bumblebee cdrom dialout lpadmin plugdev sambashare scanner To manage notifications about this bug go to:
[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04
@seb128: The missing UI refers to the reconfiguration UI which was part of lirc up to 0.9.0. This reflected even older code containing kernel modules where lirc was rebuilt from source depending on configuration. Nowadays lirc is a just a server with configuration files and there is no need to make anything special at configuration time. There are new tools available to assist in configuration, but these can and should be used after installation. Bottom line seems to be that the expectation was that nothing is changed. However, it is. The decision to make a breaking change was not taken lightly, it actually took several years, but eventually it became necessary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 Status in lirc package in Ubuntu: Confirmed Bug description: Lirc 0.10.0-2 is never configured after installation. Manually running "dpkg-reconfigure lirc " also does not do anything. I also noticed that /usr/share/lirc/remotes is empty, which is where I had my config file for Ubuntu 16.04. This was an upgrade install from 16.04. Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1674089] Re: Tamil 99 keyboard layout
Gunnar, do you have any opinion about that one and how we can fix it? ** Changed in: ibus-m17n (Ubuntu Disco) Importance: Undecided => High ** Changed in: ibus-m17n (Ubuntu Disco) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-m17n in Ubuntu. https://bugs.launchpad.net/bugs/1674089 Title: Tamil 99 keyboard layout Status in ibus-m17n package in Ubuntu: Confirmed Status in ibus-m17n source package in Disco: New Bug description: Tamil 99 keyboard layout which is the default keyboard layout prescribed by the Indian State of Tamil Nadu is not present. Selecting Tamil layout selects the Tamil Inscript layout which is prescribed by the Government of India. However, considering that Tamil is used only in the state of Tamil Nadu and that most keyboards are manufactured with Tamil 99, the layout by the Tamil Nadu government is the only one sold currently (usually by a company called TVS-e). This can be verified by Googling for Tamil+English bilingual keyboards. The current Inscript layout is useless for actual users and the lack of Tamil 99 layout forces people to switch to Google Input tools. I have observed this on Ubuntu 16.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/1674089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk
** Changed in: network-manager (Ubuntu Disco) Importance: Undecided => High ** Changed in: network-manager (Ubuntu Disco) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- 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/1796622 Title: NetworkManager IPv6 DAD lifetime behavior introduce security risk Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Disco: New Bug description: Description: When performing IPv6 certification test, two DAD test cases (3.2.5c and d) check the remaining lifetime feature of the IPv6 packets. The Network trace shows that the remaining lifetime becomes infinite when running these test cases. Hence when running in IPv6 environment with Network Manager enabled, there is a risk of packets travelling in network which has valid lifetime always. If these packets are snooped by a hacker he can reply to these packets and they can send legitimate packets which are actually not. According to https://tools.ietf.org/search/rfc4862, page 19: "The above rules address a specific denial-of-service attack in which a bogus advertisement could contain prefixes with very small Valid Lifetimes. Without the above rules, a single unauthenticated advertisement containing bogus Prefix Information options with short Valid Lifetimes could cause all of a node's addresses to expire prematurely. The above rules ensure that legitimate advertisements (which are sent periodically) will "cancel" the short Valid Lifetimes before they actually take effect." Other notes: - 2 test cases pass without NetworkManager. - Tested with different Linux Desktop Distributions, as long as NetworkManager is running, those DAD test cases fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800294] Re: Xorg freeze black screen hang up
I followed the instructions at https://forums.virtualbox.org/viewtopic.php?f=3=87526#p418088 where I disabled "Wayland in /etc/gdm3/custom.conf by uncommenting 'WaylandEnable = False'." This seems to work around the issue. -- 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/1800294 Title: Xorg freeze black screen hang up Status in xorg-server package in Ubuntu: Incomplete Bug description: i've had this issue twice this morning where during boot up my screen turns black and i can't get it to come back, then i'm forced to to a hard reboot, this issue often times happens about 99% of the time at the login screen if i don't log in with in about 10 seconds, my screen goes black and i can not get it to come back and i need to do a hard reboot. also sometimes the issue happens during boot up the screen goes purple for a few seconds then black and stay's like that and the can't get it to comes back and have to do a hard reboot, but this happens about 1 or 2 times out of ten boots i would say. so i'm hoping that this issue can be resolved in some way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 12:40:06 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7620G] [103c:808d] InstallationDate: Installed on 2018-10-27 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=45d6254a-e97a-4d45-b9a9-37afad8da3df ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 808D dmi.board.vendor: Hewlett-Packard dmi.board.version: 90.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096C120800405F0620180:rvnHewlett-Packard:rn808D:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 096C120800405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730765] Re: Mounted external devices do not appear in dock
While that would be nice to have it isn't an high priority request at the moment and didn't get accounted on the features list for the disco cycle, setting as rls-dd-wontfixing then ** Tags removed: rls-dd-incoming ** Tags added: rls-dd-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1730765 Title: Mounted external devices do not appear in dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Hi, when plugging a usb-thumb or external hard drive or any other storage media ( phone… ) I expected them to appear in the dock. Instead, they appear on desktop which forces - to leave current activity to look at the desktop, - or to open nautilus to find the new device. Dock is a very nice place for these plugged-in devices ;-) maybe at its bottom end, where trash used to be located in Unity dock ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796361] Re: autopkgtests fail with openjdk 11~28-3ubuntu1 in cosmic-proposed
autopkgtests for libreoffice 1:6.1.2-0ubuntu1.1 in cosmic-proposed all passed (see http://autopkgtest.ubuntu.com/packages/libreoffice). Based on this, marking verified. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic ** Changed in: libreoffice (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1796361 Title: autopkgtests fail with openjdk 11~28-3ubuntu1 in cosmic-proposed Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Committed Bug description: libreoffice 6.1.2 autopkgtests pass with openjdk 10.0.2+13-1ubuntu1 that's currently in cosmic. When upgrading openjdk to 11~28-3ubuntu1 in cosmic-proposed, the test called odk-build-examples reliably fails. I'm attaching the log of the failed test, ran separately in an up-to- date amd64 cosmic VM with cosmic-proposed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 17:55:10 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (824 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to cosmic on 2018-09-14 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1796361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1803016/+attachment/5212318/+files/Dependencies.txt -- 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/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
** Also affects: gnome-shell (Ubuntu Disco) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- 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/1725384 Title: On touch screens, the apps icon in the dock does not open when touched Status in Dash to dock: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: I have an Bangho AERO 1104 with touch screen, when I try to open the application drawer from the applications icon in the dock, it does not open. 1)- Ubuntu 17.10 Artful Aardvark 64 bit 2)- gnome-shell-extension-ubuntu-dock_0.7 3)- What should happen is that touching the applications icon in the dock, opens the application drawer. 4)- Instead, what has happened is that absolutely nothing happened To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] Re: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds
** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+attachment/5212324/+files/allpackages.txt -- 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/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1803016/+attachment/5212319/+files/ProcCpuinfoMinimal.txt -- 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/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gnome-shell (Ubuntu Cosmic) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell source package in Cosmic: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Disco: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
** Also affects: gnome-shell (Ubuntu Disco) Importance: High Status: Incomplete ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Disco) Importance: High Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Also affects: gnome-shell (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell source package in Cosmic: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Disco: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800294] Re: Xorg freeze black screen hang up
I am still running into this issue under Bionic Beaver running within VirtualBox. The system is functioning, but UI is frozen. There are no files within the /var/crash directory for me to submit. -- 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/1800294 Title: Xorg freeze black screen hang up Status in xorg-server package in Ubuntu: Incomplete Bug description: i've had this issue twice this morning where during boot up my screen turns black and i can't get it to come back, then i'm forced to to a hard reboot, this issue often times happens about 99% of the time at the login screen if i don't log in with in about 10 seconds, my screen goes black and i can not get it to come back and i need to do a hard reboot. also sometimes the issue happens during boot up the screen goes purple for a few seconds then black and stay's like that and the can't get it to comes back and have to do a hard reboot, but this happens about 1 or 2 times out of ten boots i would say. so i'm hoping that this issue can be resolved in some way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 12:40:06 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7620G] [103c:808d] InstallationDate: Installed on 2018-10-27 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=45d6254a-e97a-4d45-b9a9-37afad8da3df ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 808D dmi.board.vendor: Hewlett-Packard dmi.board.version: 90.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096C120800405F0620180:rvnHewlett-Packard:rn808D:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 096C120800405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758459] Re: Getting transmission 2.93 in Bionic
The report got no duplicate or user activity so it doesn't seem important for our users, also there is no testcase so it's difficult to verify a SRU until we get one, tagging as rls-not-fixing but we can still do the update later if someone describe how to trigger the issue ** Tags removed: rls-bb-incoming ** Tags added: rls-bb-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1758459 Title: Getting transmission 2.93 in Bionic Status in transmission package in Ubuntu: Confirmed Status in transmission package in Debian: Fix Released Bug description: As referenced on #1752940 some trackers have started blacklisting Transmission versions below 2.93 on the basis that they have no way of telling if an older version has been patched for CVE-2018-5702 or not. Can we try to get 2.93 in Bionic before the final freeze, especially since this is an LTS and 2.92 is starting to get old (Apr 9, 2016). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1758459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1803016/+attachment/5212321/+files/PulseList.txt -- 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/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1803016/+attachment/5212320/+files/ProcEnviron.txt -- 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/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1803016/+attachment/5212317/+files/CurrentDmesg.txt -- 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/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
