[Desktop-packages] [Bug 1838893] Re: Sorry, the program "chrome" closed unexpectedly
Thanks for the report Alan. It appears you are running Chrome, not Chromium. Bugs and crashes against chrome should be reported against the upstream project at https://chromiumbugs.appspot.com. You should be able to inspect the crashes (and maybe even report them from there) by browsing to chrome://crashes/. I'm closing this bug now, feel free to re-open it if you can reproduce the same problem with Chromium. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1838893 Title: Sorry, the program "chrome" closed unexpectedly Status in chromium-browser package in Ubuntu: Invalid Bug description: When I walk away from my laptop for a half hour or so, Chrome Tab seems to crash. Seems to only affect one Tab if I have multiple Tabs open. Sorry, the program "chrome" closed unexpectedly. Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 10:35:14 2019 InstallationDate: Installed on 2018-08-31 (337 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=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838508] Re: [snap] chromium crashes when opening a URL from an external application
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1838508 Title: [snap] chromium crashes when opening a URL from an external application Status in chromium-browser package in Ubuntu: Fix Released Bug description: This appears to be a rather recent regression. I started observing this about 3 weeks ago (around July 10), and it was recently reported by another user (https://discourse.ubuntu.com/t/call-for-testing- chromium-browser-deb-to-snap-transition/11179/95). Steps to reproduce: 0) Make sure the chromium snap is your default browser 1) Open the chromium snap, and do your usual browsing activities 2) Open a terminal, and execute `xdg-open https://example.org` 2b) Repeat step 2 a few times until you get a notification that chromium crashed, offering to restore the previous session When the crash happens, I'm seeing this relevant error: [ERROR:process_singleton_posix.cc(207)] read() failed: Permission denied (13) and the corresponding entries in journalctl: juil. 31 09:53:07 bribon audit[25535]: AVC apparmor="DENIED" operation="file_perm" profile="snap.chromium.chromium" name="/run/user/1000/snap.chromium/.org.chromium.Chromium.LWcyoF/SingletonSocket" pid=25535 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 juil. 31 09:53:07 bribon audit[25535]: AVC apparmor="DENIED" operation="file_perm" profile="snap.chromium.chromium" name="/run/user/1000/snap.chromium/.org.chromium.Chromium.LWcyoF/SingletonSocket" pid=25535 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 410069] Re: Wrong font used to display Cyrillic text
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/410069 Title: Wrong font used to display Cyrillic text Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox-3.0 Ubuntu 8.04.3, kernel 2.6.24-24-generic, Gnome 2.22.3, Firefox 3.0.12 webpage: http://en.wikipedia.org/wiki/Alexander_Suvorov html: Алекса́ндр Васи́льевич Суво́ров, font: Verdana.ttf, modified 1998-11-12 07:18:40 (specified in Firefox preferences) In the Infobox to the right, the Cyrillic text "Александр Васильевич Суворов" is displayed using the Verdana font, but in the body of the page it is displayed using what looks like a very poor version of Courier. It This affects other Russian text on the same webpage, and I see it regularly on other webpages with Russian text. However, I note that oblique (="italic") Russian text on the same page is rendered correctly. I have checked to be sure that Verdana renders correctly in Open Office Writer 2.4.1 and it does regardless of what style is used, regular, bold, italic, or bolditalic. ProblemType: Bug Architecture: i386 Date: Thu Aug 6 11:31:22 2009 DistroRelease: Ubuntu 8.04 Package: firefox-3.0 3.0.12+build1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-24-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/410069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1547127] Re: Guest account option - feature request
** Tags removed: artful gnome-17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1547127 Title: Guest account option - feature request Status in gdm: Expired Status in Ubuntu GNOME: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gdm3 package in Baltix: New Bug description: Though I didn't have it enabled for security reasons when I was using Unity, I think that some may find it useful to have a 'guest account' option, though I think that it should be off by default and be reasonably easy to configure in the gnome-control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1547127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697021] Re: No mouse cursor on startup
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 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. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: unity (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1697021 Title: No mouse cursor on startup Status in gdm3 package in Ubuntu: Won't Fix Status in unity package in Ubuntu: Won't Fix Bug description: Most(but not all) of the time, after shutting down / starting up my pointer does not exist. It's not insvisible, it's just not there. Workaround: unplug, replug USB mouse and pointer appears. USB LED mouse, Manufactured for IBM model M032B0 (A) Bus 001 Device 009: ID 04b3:3107 IBM Corp. ThinkPad 800dpi Optical Travel Mouse eva1 description: Desktop Computer product: MS-7994 (Default string) vendor: MSI version: 1.0 serial: Default string width: 64 bits capabilities: smbios-3.0 dmi-3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=Default string sku=Default string uuid=----4CCC6A953B75 *-core description: Motherboard product: H110M GAMING (MS-7994) vendor: MSI physical id: 0 version: 1.0 serial: GA16496480 slot: Default string *-pci description: Host bridge product: Intel Corporation vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 05 width: 32 bits clock: 33MHz *-usb description: USB controller product: Sunrise Point-H USB 3.0 xHCI Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 31 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:120 memory:df23-df23 *-usb:1 description: Mouse product: ThinkPad 800dpi Optical Travel Mouse vendor: IBM Corp. physical id: 5 bus info: usb@1:5 version: 5.00 capabilities: usb-1.10 configuration: driver=usbhid maxpower=100mA speed=2Mbit/s Ubuntu 17.04 zesty 64 bit gnome/unity graphics: Intel® Kabylake GT2 xserver-xorg-video-intel: Installed: 2:2.99.917+git20170309-0ubuntu1 Candidate: 2:2.99.917+git20170309-0ubuntu1 xserver-xorg: Installed: 1:7.7+16ubuntu3 Candidate: 1:7.7+16ubuntu3 unity: Installed: 7.5.0+17.04.20170407.1-0ubuntu1 Candidate: 7.5.0+17.04.20170407.1-0ubuntu1 from Xorg.0.log on start up: [42.665] (II) config/udev: Adding input device HID 04b3:3107 (/dev/input/mouse0) [42.665] (II) No input driver specified, ignoring this device. [42.665] (II) This device may have been added with another device file. [42.771] (II) config/udev: Adding input device HID 04b3:3107 (/dev/input/event14) [42.771] (**) HID 04b3:3107: Applying InputClass "libinput pointer catchall" [42.771] (II) Using input driver 'libinput' for 'HID 04b3:3107' [42.771] (**) HID 04b3:3107: always reports core events [42.771] (**) Option "Device" "/dev/input/event14" [42.771] (**) Option "_source" "server/udev" [42.840] (II) input device 'HID 04b3:3107', /dev/input/event14 is tagged by udev as: Mouse [42.840] (II) input device 'HID 04b3:3107', /dev/input/event14 is a pointer caps [42.872] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:$ [42.872] (II) XINPUT: Adding extended input device "HID 04b3:3107" (type: MOUSE, id 12) [42.873] (**) Option "AccelerationScheme" "none" [42.874] (**) HID 04b3:3107: (accel) selected scheme none/0 [42.874] (**) HID 04b3:3107: (accel) acceleration factor: 2.000 [42.874] (**) HID 04b3:3107: (accel) acceleration threshold: 4 [42.932] (II) input device 'HID 04b3:3107', /dev/input/event14 is tagged by udev as: Mouse [42.932] (II)
[Desktop-packages] [Bug 1715811] Re: GDM crash loop Ubuntu 17.10 (Intel)
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. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1715811 Title: GDM crash loop Ubuntu 17.10 (Intel) Status in gdm3 package in Ubuntu: Won't Fix Bug description: GDM crash loop. All I see after boot is constant tty/"black screen with cursor" changing each other. After stopping GDM from tty I can start gnome session manually (both wayland and xorg works) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 7 23:20:33 2017 InstallationDate: Installed on 2017-08-02 (36 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170801) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-09-07T13:20:23.727938 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1715811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693992] Re: gdm-session-worker crashed with SIGABRT - "assertion failed: (manager->priv->accounts_proxy != NULL)" in load_users()
** Tags removed: artful yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1693992 Title: gdm-session-worker crashed with SIGABRT - "assertion failed: (manager->priv->accounts_proxy != NULL)" in load_users() Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.24.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/c0848264c9da4adaeb5da47a7aa34ce5bdd84909 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1693992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711538] Re: Tap-to-click does not work on the GDM login screen
** Tags removed: artful ** Tags added: bionic ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #124 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/124 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/124 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1711538 Title: Tap-to-click does not work on the GDM login screen Status in gdm: Expired Status in gnome-control-center: Unknown Status in GNOME Settings Daemon: Unknown Status in gdm3 package in Ubuntu: Triaged Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Tap-to-click does not work in GDM login ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 18 16:16:56 2017 InstallationDate: Installed on 2017-05-04 (105 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1711538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727466] Re: ubuntu 17.10 gdm numlockx cannot be activated
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. ** Changed in: gdm3 (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1727466 Title: ubuntu 17.10 gdm numlockx cannot be activated Status in gdm: Expired Status in gdm3 package in Ubuntu: Won't Fix Bug description: In ubuntu 17.10 i am not able to activate numlock on the login screen. Tried with and without wayland. Cannot get numlockx working as I always did in other *ubuntu's with gdm. /etc/gdm3/Init/Default is not working anymore. is there a way to do it? Guyd To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1727466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751182] Re: package gdm3 3.26.1-3ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10
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. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1751182 Title: package gdm3 3.26.1-3ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10 Status in gdm3 package in Ubuntu: Won't Fix Bug description: Description: Ubuntu 17.10 Release: 17.10 :~$ apt-cache policy pkgname N: Unable to locate package pkgname I was running sudo apt upgrade. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Thu Feb 22 16:33:39 2018 DpkgTerminalLog: Removing chrome-gnome-shell (9-0ubuntu1) ... Removing gdm3 (3.26.1-3ubuntu3) ... Please be sure to run "dpkg-reconfigure lxdm". dpkg: error processing package gdm3 (--remove): subprocess installed pre-removal script returned error exit status 10 DuplicateSignature: package:gdm3:3.26.1-3ubuntu3 Removing gdm3 (3.26.1-3ubuntu3) ... Please be sure to run "dpkg-reconfigure lxdm". dpkg: error processing package gdm3 (--remove): subprocess installed pre-removal script returned error exit status 10 ErrorMessage: subprocess installed pre-removal script returned error exit status 10 InstallationDate: Installed on 2018-02-20 (2 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: gdm3 Title: package gdm3 3.26.1-3ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10 UpgradeStatus: Upgraded to artful on 2018-02-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1751182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748036] Re: .pam_environment not applied if home directory is encrypted
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. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1748036 Title: .pam_environment not applied if home directory is encrypted Status in gdm3 package in Ubuntu: Won't Fix Bug description: Regression of bug #952185. Variables in ~/.pam_environment are not applied when I start my computer and login. When I then re-login, they _are_ applied. I have manually copied my ~/.pam_environment to the original, non- ecryptfs-mounted ~/ and then the file is always applied. After #952185, the fix seems to have been to change debian/*.pam to run pam_env after common-session. But I don't understand why the line in common-auth isn't enough to mount ecryptfs. Perhaps pam_ecryptfs.so only does the unmounting in the session phase. Ubuntu 17.10, gdm3 3.26.1-3ubuntu3 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: gdm3 3.26.1-3ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1748036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
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. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics Status in gdm3 package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in gdm3 package in Fedora: Confirmed Bug description: I've just upgraded to Ubuntu 17.10 and switched the login manager from sddm to gdm3. Unfortunately it doesn't list the -wayland sessions. The /usr/share/xsessions folder indeed only contains the -xorg -related sessions: $ ls -la /usr/share/xsessions total 36 drwxr-xr-x 2 root root 4096 okt 18 16:00 . drwxr-xr-x 427 root root 20480 okt 18 15:56 .. -rw-r--r-- 1 root root 201 okt 13 12:56 gnome-xorg.desktop -rw-r--r-- 1 root root 2354 aug 23 16:39 plasma.desktop -rw-r--r-- 1 root root 262 okt 13 12:56 ubuntu-xorg.desktop How can I enable the ubuntu-wayland session please? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 16:37:47 2017 InstallationDate: Installed on 2016-09-05 (408 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719002] Re: Using gdm3 causes plymouth to flicker to/from VT text
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. ** Changed in: gdm3 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1719002 Title: Using gdm3 causes plymouth to flicker to/from VT text Status in gdm3 package in Ubuntu: Won't Fix Bug description: I originally thought it was a kernel problem but please read this thread here. https://ubuntuforums.org/showthread.php?t=2372108 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 22 15:27:34 2017 InstallationDate: Installed on 2017-09-05 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1719002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726996] Re: gdm3 will not unlock session (or switch to a PTY) when out of inotify watches ["No space left on device"]
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. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1726996 Title: gdm3 will not unlock session (or switch to a PTY) when out of inotify watches ["No space left on device"] Status in gdm3 package in Ubuntu: Won't Fix Bug description: The log messages from around the time when I attempt an unlock look like this: Oct 24 13:38:13 surprise gdm-password]: AccountsService: Failed to monitor logind session changes: No space left on device Oct 24 13:38:31 surprise gdm-password]: message repeated 2 times: [ AccountsService: Failed to monitor logind session changes: No space left on device] Oct 24 13:38:32 surprise gsd-rfkill[1564]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput' Oct 24 13:38:32 surprise kernel: [16851.666217] rfkill: input handler enabled Oct 24 13:38:40 surprise gnome-shell[937]: JS WARNING: [resource:///org/gnome/shell/gdm/realmd.js 130]: reference to undefined property "_loginFormat" Oct 24 13:38:40 surprise gnome-shell[937]: JS WARNING: [resource:///org/gnome/shell/gdm/realmd.js 142]: reference to undefined property "_loginFormat" Oct 24 13:38:48 surprise gdm-password]: AccountsService: Failed to monitor logind session changes: No space left on device I run CrashPlan for backups, and https://bugzilla.redhat.com/show_bug.cgi?id=1081004 suggests that these messages are happening because I've run out of inotify watches on my system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 13:47:25 2017 InstallationDate: Installed on 2017-10-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1726996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715771] Re: package gdm3 (not installed) failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 10
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. ** Changed in: gdm3 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1715771 Title: package gdm3 (not installed) failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 10 Status in gdm3 package in Ubuntu: Won't Fix Bug description: When updating to ubuntu 17.10 I generated problems with my machine that has two cards one nvidia and another one of intel that loads with controller Skylake 530 GT2 after this I did not raise any graphical interface by command line decided to eliminate nvidia and i915 of intel load nouveau so I raised the interface, then entered and remains stuck in gnome control center I decided to remove the same gnome-shell that I had installed since synaptic and now I throw an error of a program that is not installed. Another issue had been completely eliminated in driver and therefore the local wired connection only had the interface lo and wlan0. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: gdm3 (not installed) ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Sep 7 18:16:32 2017 ErrorMessage: el subproceso instalado el script pre-removal devolvió el código de salida de error 10 InstallationDate: Installed on 2017-08-24 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~rc1~ubuntu1 SourcePackage: gdm3 Title: package gdm3 (not installed) failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1715771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1536158] Re: Upgrade to 1.1.1 that was released in March 2016
** Tags removed: yakkety ** Tags added: bionic eoan -- 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/1536158 Title: Upgrade to 1.1.1 that was released in March 2016 Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver-2.6.28-12 package in Ubuntu: Confirmed Bug description: Please, upgrade to 1.1.1 that was released in March 2016, see http://www.alsa-project.org/main/index.php/Changes_v1.1.0_v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1536158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635797] Re: Analog audio out not showing in GUI sound settings.
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. 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. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1635797 Title: Analog audio out not showing in GUI sound settings. Status in alsa-driver package in Ubuntu: Won't Fix Bug description: "aplay -Dplughw:0,0 -fcd sound.wav" works fine kes@vesta:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC1150 Analog [ALC1150 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 <...other cards which do appear in the System sound GUI...> ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 22 16:13:28 2016 InstallationDate: Installed on 2016-10-16 (6 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1150, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1810 dmi.board.asset.tag: Default string dmi.board.name: H170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1810:bd07/12/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637683] Re: ubuntu 16.10 internal speakers don't work, but headphones do
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. 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. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1637683 Title: ubuntu 16.10 internal speakers don't work, but headphones do Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Under sound settings only headphone output is listed as an option, no internal speakers are listed. Headphone playback does work. In alsamixer, speaker output was at 0 and muted, but unmuting and increasing volume does not produce playback in speakers. ASUS X550LB laptop ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 28 20:42:56 2016 InstallationDate: Installed on 2016-10-29 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550LB, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LB.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LB.403:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1637683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635668] Re: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. 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. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1635668 Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted Status in alsa-driver package in Ubuntu: Won't Fix Bug description: This defect is not apparent on two other Ubuntu 16.04 machines. The upgrade to 16.10 did not change the symptoms. lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 21 11:53:54 2016 InstallationDate: Installed on 2016-09-22 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0773VG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737279] Re: Greeter fails to start after upgrade, session is 'gdm-shell'
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. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1737279 Title: Greeter fails to start after upgrade, session is 'gdm-shell' Status in gdm3 package in Ubuntu: Won't Fix Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gdm3 gdm3: Installed: 3.26.1-3ubuntu3 I've had this problem on two different machines on which I ran upgrades to Artful. The greeter never appears after the system boots. It's possible to log in to a different tty, though. When using another tty and running "systemctl restart gdm3", the screen flashes a few times but then returns to the tty. After enabling GDM debugging by modifying "/etc/gdm3/custom.conf" the journal seems to show that gdm is trying to start a "gdm-shell" session whose file doesn't exist. To fix the problem, I tried adding these lines to /etc/gdm3/greeter .dconf-defaults: [org/gnome/desktop/session] session-name='gnome-login' However, this didn't make a difference. "apt get install --reinstall gdm3" also didn't solve the issue. On both affected systems, I finally found there was a file at "/etc/dconf/db/gdm.d/00-upstream-settings" containing these lines: [org/gnome/desktop/session] session-name='gdm-shell' Changing the configuration here to gnome-login was the only step that solved the problem of those I tried. I suspect there was some old configuration left around from one of my many upgrades. I found that the file "/etc/dconf/db/gdm.d/00-upstream- settings" doesn't exist after a fresh install of gdm on artful. Log from journalctl: Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): emitting SessionIsActive Dec 09 08:25:25 david-desktop gnome-session-binary[22563]: DEBUG(+): emitting SessionIsActive Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): fill: *** Getting session 'gdm-shell' Dec 09 08:25:25 david-desktop gnome-session-binary[22563]: DEBUG(+): fill: *** Getting session 'gdm-shell' Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): fill: *** Looking if /var/lib/gdm/.config/gnome-session/sessions/gdm-shell.session is a valid session file Dec 09 08:25:25 david-desktop gnome-session-binary[22563]: DEBUG(+): fill: *** Looking if /var/lib/gdm/.config/gnome-session/sessions/gdm-shell.session is a valid session file Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): Cannot use session '/var/lib/gdm/.config/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. Dec 09 08:25:25 david-desktop gnome-session-binary[22563]: DEBUG(+): Cannot use session '/var/lib/gdm/.config/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): fill: *** Looking if /etc/xdg/gnome-session/sessions/gdm-shell.session is a valid session file Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): Cannot use session '/etc/xdg/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): fill: *** Looking if /usr/share/gdm/greeter/gnome-session/sessions/gdm-shell.session is a valid session file Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): Cannot use session '/usr/share/gdm/greeter/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): fill: *** Looking if /usr/local/share/gnome-session/sessions/gdm-shell.session is a valid session file Dec 09 08:25:25 david-desktop /usr/lib/gdm3/gdm-wayland-session[22559]: gnome-session-binary[22563]: DEBUG(+): Cannot use session '/usr/local/share/gnome-session/sessions/gdm-shell.session': non-existing or invalid
[Desktop-packages] [Bug 1637837] Re: [Em28xx-Audio - Em28xx Audio, recording] WinTV HVR-900 no sound at all or distorted sound
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. 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. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1637837 Title: [Em28xx-Audio - Em28xx Audio, recording] WinTV HVR-900 no sound at all or distorted sound Status in alsa-driver package in Ubuntu: Won't Fix Bug description: The device is WinTV HVR-900 (actually Elgato EyeTV Hybrid). It has an additional dongle with Composite, S-Video and stereo audio inputs. lsusb: Bus 002 Device 006: ID 2040:6502 Hauppauge WinTV HVR-900 I use it together with TVTime, pavucontrol and module-loopback and it generally works well (barring bug #1637817 which I reported earlier today), provided sound is plugged into the computer's line-in input. I'd really like to make it work with the tuner's input, however. When connected, it appears in pavucontrol and can be configured as Analog Stereo Input, and in Input Devices I can select Line In or Video. Selecting either makes no difference: most times there's no sound at all, sometimes sound appears, but it's distorted (a bit like an echo together with overdrive). I'll try to make it work (plugging/unplugging the tuner, restarting pulseaudio usually makes it work after a few times) and post a sample. Interestingly, the volume slider in Input Devices in pavucontrol has no effect at all; sound level remains constant. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 30 15:00:08 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-02-02 (270 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Em28xxAudio failed Symptom_Card: WinTV HVR-900 - Em28xx Audio Symptom_Type: No sound at all Title: [Em28xx-Audio - Em28xx Audio, recording] No sound at all UpgradeStatus: Upgraded to yakkety on 2016-10-25 (5 days ago) dmi.bios.date: 09/23/15 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP61.88Z.0057.B11.1509232013 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B11.1509232013:bd09/23/15:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.name: MacBookPro6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1637837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639753] Re: USB-Audio - HyperX 7.1 Audio, playback Not detected at startup
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. 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. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1639753 Title: USB-Audio - HyperX 7.1 Audio, playback Not detected at startup Status in alsa-driver package in Ubuntu: Won't Fix Bug description: USB-Audio - HyperX 7.1 USB soundcard Output device is not detected at startup, need to manually unplug and re-plug the USB cable for the system to recognize it. After re- plugging, everything works normally. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: marco 2534 F...m pulseaudio /dev/snd/controlC2: marco 2534 F pulseaudio /dev/snd/controlC1: marco 2534 F pulseaudio /dev/snd/controlC0: marco 2534 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 7 11:34:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-20 (352 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: HyperX 7.1 Audio - HyperX 7.1 Audio Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marco 2534 F pulseaudio /dev/snd/controlC1: marco 2534 F pulseaudio /dev/snd/controlC0: marco 2534 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - HyperX 7.1 Audio, playback] No sound at all UpgradeStatus: Upgraded to yakkety on 2016-10-28 (9 days ago) dmi.bios.date: 04/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2401:bd04/24/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1639753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1641690] Re: [X7, Realtek ALC282, Speaker, Internal] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. 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. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1641690 Title: [X7, Realtek ALC282, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: no sound from built-in speakers, headphones fine ubuntu 16.10, frehs install laptop is this http://www.aorus.com/Product/Spec/X7 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tweichart 2752 F pulseaudio /dev/snd/controlC2: tweichart 2752 F pulseaudio /dev/snd/pcmC0D0p: tweichart 2752 F...m pulseaudio /dev/snd/controlC0: tweichart 2752 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 14 18:51:43 2016 InstallationDate: Installed on 2016-11-11 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tweichart 2752 F pulseaudio /dev/snd/controlC2: tweichart 2752 F pulseaudio /dev/snd/controlC0: tweichart 2752 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X7, Realtek ALC282, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X7.309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X7 dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX7.309:bd02/10/2014:svnGIGABYTE:pnX7:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnX7:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: X7 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1641690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750336] Re: Unable to log in (Caps Lock doesn't work on the login screen)
** Changed in: gdm3 (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1750336 Title: Unable to log in (Caps Lock doesn't work on the login screen) Status in gdm: Expired Status in gdm3 package in Ubuntu: Won't Fix Bug description: When I choose to use the Nvdia-340.104 driver, I can not login from the GDM screen. Steps to Reproduce: 1. Go to "Software and Updates > Additional Drivers", choose NVDIA Corporation: G86M [Quadro NVS 140M] - Use NVDIA binary driver version 340.104, apply. 2. Reboot. 3. Type in the correct password to login. Expected Result: Login should be successful. Current Result: Message says the password is incorrect. Additional Info: If I hit Ctrl+Alt+F3 to open a terminal and login from there, the login is successful. Also, The login is successful when I am using the xserver-xorg-video-nouveau opensource driver. $ lspci 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c) 00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c) 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03) 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M-E) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation G86M [Quadro NVS 140M] (rev a1) 03:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01) 05:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) 15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) GDM 3.26.1-3ubuntu3 Ubuntu 17.10.1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 16:32:40 2018 InstallationDate: Installed on 2018-02-18 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1750336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
** Tags removed: yakkety ** Tags added: bionic -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1641959] Re: [CMI8786 - Xonar DG, playback] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. 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. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1641959 Title: [CMI8786 - Xonar DG, playback] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: ubuntu 16.10 3.9Gb AMD Penim(TM) II X4 965 Processor x4 GeFofce GTX 5590 Ti/PCIe/SSE2 64 hdd 59 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: sergy113 2806 F...m pulseaudio /dev/snd/pcmC1D0p: sergy113 2806 F...m pulseaudio /dev/snd/controlC1: sergy113 2806 F pulseaudio /dev/snd/controlC0: sergy113 2806 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 15 17:07:14 2016 InstallationDate: Installed on 2016-11-09 (6 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DG failed Symptom_Card: CMI8788 [Oxygen HD Audio] (CMI8786 (Xonar DG)) - Xonar DG Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: sergy113 2806 F...m pulseaudio /dev/snd/pcmC1D0p: sergy113 2806 F...m pulseaudio /dev/snd/controlC1: sergy113 2806 F pulseaudio /dev/snd/controlC0: sergy113 2806 F pulseaudio Symptom_Type: No sound at all Title: [CMI8786 - Xonar DG, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2401:bd05/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-11-10T10:30:02.974053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1641959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808873] Re: gdm3 no greeter displayed until a VT switch is forced
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. 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. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1808873 Title: gdm3 no greeter displayed until a VT switch is forced Status in gdm3 package in Ubuntu: Won't Fix Bug description: Hello, Ubuntu 18.10, Intel integrated video, a monitor connected by DVI, a projector connected by HDMI. While all the boot messages appear on both devices (if they are turned on) the gdm3 greeter doesn't appear at all (black screens) UNTIL I switch to a virtual console and back (Ctrl+Alt+F2, Ctrl+Alt+F1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1808873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when desktop files are constantly created or deleted
** Summary changed: - gnome-shell high memory and CPU usage when desktop files are constantly created or deleted (like by zsh) + gnome-shell high memory and CPU usage when desktop files are constantly created or deleted -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1815550 Title: gnome-shell high memory and CPU usage when desktop files are constantly created or deleted Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons source package in Disco: In Progress Bug description: This *may* be an nvidia-specific problem, but the RSS of gnome-shell on my system grows without limit (over a couple of hours it's increased past 10G). At the same time, gnome-shell appears to become progressively less responsive. Restarting gnome-shell (via restart) drops shell RSS down to ~400MB and improves system responsiveness a bit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 4.20.0 Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 13:35:59 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1815550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838821] Re: [deb2snap] Upgrade fails when snap is already installed
** Tags added: snap ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1838821 Title: [deb2snap] Upgrade fails when snap is already installed Status in chromium-browser package in Ubuntu: Incomplete Bug description: I have the chromium-browser snap installed, and when upgrading to the new snap-based Chromium deb, it fails when the snap is already installed: Preparing to unpack .../chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap snap "chromium" is already installed, see 'snap help refresh' => Snap installation complete => Connecting the password-manager-service interface (LP: #1836616) error: cannot resolve connection, slot snap name is empty dpkg: error processing archive /var/cache/apt/archives/chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 Preparing to unpack .../libidn2-0_2.2.0-1_amd64.deb ... Unpacking libidn2-0:amd64 (2.2.0-1) over (2.0.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a blocker to SRUing the deb2snap transition to stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838876] Re: OBS Studio (snap) can't launch with GNOME on Wayland (there are no problems with X.org session)
** Package changed: gnome-shell (Ubuntu) => obs-studio (Ubuntu)
** Tags added: snap
--
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/1838876
Title:
OBS Studio (snap) can't launch with GNOME on Wayland (there are no
problems with X.org session)
Status in obs-studio package in Ubuntu:
New
Bug description:
artem@hp-250-g6-notebook-pc:~$ obs-studio
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva
error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit
/snap/obs-studio/525/usr/sbin:/snap/obs-studio/525/usr/bin:/snap/obs-studio/525/sbin:/snap/obs-studio/525/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
This application failed to start because it could not find or load the Qt
platform plugin "wayland-egl"
in "".
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, xcb.
Reinstalling the application may fix this problem.
Aborted (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.32.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 4 15:00:05 2019
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'app-picker-view' b'uint32 1'
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities',
'Sundry', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'ua')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2019-08-04 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1
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/obs-studio/+bug/1838876/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838809] Re: Full screen doesn't work with SDL2.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1838809 Title: Full screen doesn't work with SDL2. Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: When trying to enter full screen in SDL2 apps I just get a jittery mouse or a black screen. I've tried pygame2 apps and this simple C program: https://github.com/illume/pygame4000/blob/master/code/sdl2_basics_tutorial_fundamentals/hey.c But I replaced line 150 where it has SDL_WINDOW_RESIZABLE with SDL_WINDOW_FULLSCREEN. and I just get a black screen with a discolored bar at the top. I'm using Ubuntu 18.04.2 with sdl2.0.9 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 2 11:13:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21d0] NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0] InstallationDate: Installed on 2018-07-03 (394 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 4236B16 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=0f9f42c8-a36e-4919-a9ba-8ad037dc193a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET78WW (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236B16 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET78WW(1.48):bd01/21/2016:svnLENOVO:pn4236B16:pvrThinkPadT420:rvnLENOVO:rn4236B16:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4236B16 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 N/A 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/1838809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838818] Re: intel graphic
Thanks for the bug report. Can you please explain in more detail what the problem is? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838818 Title: intel graphic Status in xorg-server package in Ubuntu: Incomplete Bug description: i cant launch my intel graphic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) Uname: Linux 5.0.0-05-generic i686 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Fri Aug 2 20:42:57 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1854] InstallationDate: Installed on 2019-08-01 (1 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170216) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-05-generic root=UUID=55255409-9bb4-47d0-8b50-c96ca1a24f27 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.3C dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3465LBF dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.3C:bd10/11/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.sku: E9P66EA#BH4 dmi.product.version: 088F130059160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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+git1907241930.6f4972~oibaf~b 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/1838818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831384] Re: .desktop files not working in Ubuntu 19.04 Gnome
** Changed in: gnome-shell (Ubuntu) Status: Expired => New ** Tags added: disco -- 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/1831384 Title: .desktop files not working in Ubuntu 19.04 Gnome Status in gnome-shell package in Ubuntu: New Bug description: I use several instances of Firefox, that I usually launch from various launchers. For example, I have a `firefox-test.desktop` file in `~/.local/share/applications`, that contains: ``` [Desktop Entry] Version=1.0 Name=Firefox-Test StartupWMClass=firetest Exec=firefox --new-instance --no-remote -P Test --class firetest %u Icon=firefox-developer-icon Terminal=false Type=Application MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https; StartupNotify=true Categories=Network;WebBrowser; Keywords=web;browser;internet;pentest; Actions=new-window;new-private-window; ``` It worked for ages, in many DE, including GNOME in 18.04. But, in 19.04, clicking on my launchers does nothing. On the other hand, the commands works from the terminal: ``` firefox --new-instance --no-remote -P Test --class firetest ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838919] [NEW] Slow and lost keyboard and mouse events
Public bug reported: This was a fresh amd64 installation with 18.10 desktop, upgraded to 19.04 as soon as available. It has been getting worse over the last few weeks and is now so bad I can hardly type an email (or this bug report!) without having to fix many typos. journalctl shows many different gnome errors, so it is difficult to figure out which is the underlying cause and which are simply collateral damage. There are two sequences that appear first after a reboot, and the first of these has been reported many times on ubuntu releases going back for years:- Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module "canberra-gtk-module" and Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.89/org/ayatana/NotificationItem/software_update_available Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable to update overlay icon Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable to update overlay icon Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- Is this a recent regression? I know for sure the system wasn't this unresponsive 3 weeks ago, but I cannot be sure when it started to go wrong. My mouse/keyboard combo has a USB-wireless dongle and I've fiddled around with distance and battery state until I was sure the problem was somewhere else and started to check the system log. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.30.6-2ubuntu4.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 11:53:37 2019 InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu4.19.04.1 gnome-software-plugin-snap3.30.6-2ubuntu4.19.04.1 SourcePackage: gnome-software UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1838919 Title: Slow and lost keyboard and mouse events Status in gnome-software package in Ubuntu: New Bug description: This was a fresh amd64 installation with 18.10 desktop, upgraded to 19.04 as soon as available. It has been getting worse over the last few weeks and is now so bad I can hardly type an email (or this bug report!) without having to fix many typos. journalctl shows many different gnome errors, so it is difficult to figure out which is the underlying cause and which are simply
[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
I have three screens: 1) nVidia GTX 970M HDMI port of laptop. 1920x1080 2) USB-C, Thunderbolt III HDMI dongle. 3840x2160 3) Laptop eDP1 (i7 6700HQ, HD 530 iGPU). 1920x1080 Upon resume the 3840x2160 screen's wallpaper is **OK**. The two 1920x1080 screens wallpaper is all white. Ubuntu 16.04.6 LTS upgrade direct to 19.04 w/kernel 5.0.0-23 yesterday. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter source package in Bionic: Confirmed Status in mutter source package in Disco: Confirmed Status in mutter source package in Eoan: In Progress Bug description: https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1838912] [NEW] Bluetooth doesn't remember my Logitech MX Master mouse.
Public bug reported: I can pair my mouse, and sometimes Ubuntu will remember it, but more often it doesn't automatically connect when I turn the computer on or wake it up. I've noticed that it'll have the same BT address, so it should connect (?). When it DOES connect, it's when I've had the mouse turned off and don't turn it on until Ubuntu is completely awake and running. That doesn't always work, but if I have the mouse turned on before turning Ubuntu on, then it never connects. I have to re-pair them. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 18:40:38 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-01 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1838912 Title: Bluetooth doesn't remember my Logitech MX Master mouse. Status in gnome-control-center package in Ubuntu: New Bug description: I can pair my mouse, and sometimes Ubuntu will remember it, but more often it doesn't automatically connect when I turn the computer on or wake it up. I've noticed that it'll have the same BT address, so it should connect (?). When it DOES connect, it's when I've had the mouse turned off and don't turn it on until Ubuntu is completely awake and running. That doesn't always work, but if I have the mouse turned on before turning Ubuntu on, then it never connects. I have to re-pair them. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 18:40:38 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-01 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog
I can confirm, this bug is back. The password is saved, but the username is not. -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838902] Re: GNOME Control Center sticks when I add other keyboard in settings
Thanks for your report! I think that one reason for that delay is that "Other" opens a window with quite a few sources, and all the labels are processed for translation etc. But there is probably room for a design improvement to speed it up. It would be great if you could open an upstream issue, since this is an upstream design matter. https://gitlab.gnome.org/GNOME/gnome-control-center/issues If you do, please post the URL to it here for tracking purposes. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1838902 Title: GNOME Control Center sticks when I add other keyboard in settings Status in gnome-control-center package in Ubuntu: Confirmed Bug description: But then the list of languages opens and I can choose needing variant. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 22:30:32 2019 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
What is the result from terminal for cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval
[Desktop-packages] [Bug 1838902] [NEW] GNOME Control Center sticks when I add other keyboard in settings
Public bug reported: But then the list of languages opens and I can choose needing variant. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 22:30:32 2019 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Video that shows this bug" https://bugs.launchpad.net/bugs/1838902/+attachment/5280795/+files/2019-08-04%2017-20-09.flv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1838902 Title: GNOME Control Center sticks when I add other keyboard in settings Status in gnome-control-center package in Ubuntu: New Bug description: But then the list of languages opens and I can choose needing variant. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 22:30:32 2019 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838898] [NEW] auctex not found by emacs
Public bug reported: In ubuntu 19.04 with emacs 26.1, typing "M-x auctex" is not a valid command. This is reproducible even starting as "emacs -q". I've also tried evaluating (load "auctex"), which returns true, but the command "auctex" remains unavailable. The variable AUCTeX-version has value 11.91. The variable AUCTeX-date has value 2017-07-24. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: auctex 11.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: i3 Date: Sun Aug 4 21:16:49 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-23 (1381 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: auctex UpgradeStatus: Upgraded to disco on 2019-07-30 (5 days ago) ** Affects: auctex (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to auctex in Ubuntu. https://bugs.launchpad.net/bugs/1838898 Title: auctex not found by emacs Status in auctex package in Ubuntu: New Bug description: In ubuntu 19.04 with emacs 26.1, typing "M-x auctex" is not a valid command. This is reproducible even starting as "emacs -q". I've also tried evaluating (load "auctex"), which returns true, but the command "auctex" remains unavailable. The variable AUCTeX-version has value 11.91. The variable AUCTeX-date has value 2017-07-24. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: auctex 11.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: i3 Date: Sun Aug 4 21:16:49 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-23 (1381 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: auctex UpgradeStatus: Upgraded to disco on 2019-07-30 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/auctex/+bug/1838898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
The longer of your two attached log files, log-network-manager-without-
segmentation.txt, seems to contain at least one of your two tests, so I
extracted the part from your test starting (last start of network-
manager, with log verbosity set to contain and messages)
up to the end. I have attached this part to this posting as log-network-
manager-without-segmentation-2.txt.
When one searches for the string "current configuration:" one finds
where DNS configuration is changed due to network interfaces being added
or removed. The last of these occurrences is the only place where your
VPN (with your office's DNSes 172.27.0.42 and 172.27.0.33) gets added to
your phone's internet access (with DNS 192.168.42.129). Only in this
acase you get an error with pacrunner (PAC = Proxy Auto Configuration,
see https://wiki.gnome.org/Projects/NetworkManager/Proxies) but seems to
succeed later. There are also some other errors visible. Here are some
lines of the log:
--
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4886]
dns-mgr: current configuration: [{'nameservers': <['172.27.0.42',
'172.27.0.33']>, 'interface': <'tun2'>, 'priority': <50>, 'vpn': },
{'nameservers': <['192.168.42.129']>, 'interface': <'enp0s20f0u2'>, 'priority':
<100>, 'vpn': }]
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4895]
dispatcher: (32) (tun2) dispatching action 'vpn-up'
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4900]
pacrunner: call[0x563b6899bc30]: send: new config ({'Interface': <'tun2'>,
'Method': <'direct'>, 'BrowserOnly': , 'Domains': <['172.31.252.244/24',
'172.27.0.0/24', '172.27.240.0/20', '192.168.222.0/24', '185.48.32.186/32',
'80.247.66.0/24', '87.248.32.84/32', '178.239.180.149/32', '80.247.66.96/32',
'87.248.32.223/32', '10.6.0.0/16', '172.31.252.0/24']>},)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4900]
pacrunner: call[0x563b6899bc30]: sending...
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4907]
pacrunner: call[0x563b6899bc30]: sending failed:
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.pacrunner"
does not exist
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4907] prope
rties-changed[0x563b688b9c10]: type NMDeviceTun, iface NMDBusDeviceStatisticsSke
leton: {'TxBytes': }
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4908] prope
rties-changed[0x563b688b9c10]: type NMDeviceTun, iface NMDBusDeviceTunSkeleton:
{'Dhcp4Config': , 'Dhcp6Config': , 'Ip4Address':
, 'Ip4Config': , 'Ip6Config': , 'IpInterface': <''>, 'Managed': , 'State': ,
'StateReason': <(uint32 20, uint32 41)>}
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4909]
device[0x563b688b9c10] (tun2): ip4-config: update (commit=0,
new-config=0x563b688ab4a0)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4910]
device[0x563b688b9c10] (tun2): ip6-config: update (commit=0,
new-config=0x563b688b4940)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4912]
manager: (tun2): assume: generated connection 'tun2'
(7ddca237-b609-4f44-bf54-9f3705d663ce)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4917]
settings: Failed to add 7ddca237-b609-4f44-bf54-9f3705d663ce/'tun2': Plugin
does not support adding connections
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4922]
settings-connection[0x563b68793a80]: constructed (NMSKeyfileConnection)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4929]
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]:
update settings-connection flags to visible (was none)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4929]
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]:
update settings-connection flags to unsaved,visible (was visible)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4929]
keyfile: add connection in-memory (7ddca237-b609-4f44-bf54-9f3705d663ce,"tun2")
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.4935]
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]:
failed to read connection timestamp: Il file chiavi non presenta alcuna chiave
«7ddca237-b609-4f44-bf54-9f3705d663ce» nel gruppo «timestamps»
[...]
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5344]
dns-mgr: (device_state_changed): no DNS changes to commit (0)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5344]
device (tun2): Activation: successful, device activated.
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5344]
device[0x563b688b9c10] (tun2): set metered value 4
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5345]
dispatcher: (34) (tun2) dispatching action 'up'
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]: [1564066391.5350]
pacrunner: call[0x563b689a10c0]: send: new config ({'Interface': <'tun2'>,
'Method': <'direct'>, 'BrowserOnly': },)
lug
[Desktop-packages] [Bug 1838893] [NEW] Sorry, the program "chrome" closed unexpectedly
Public bug reported: When I walk away from my laptop for a half hour or so, Chrome Tab seems to crash. Seems to only affect one Tab if I have multiple Tabs open. Sorry, the program "chrome" closed unexpectedly. Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 10:35:14 2019 InstallationDate: Installed on 2018-08-31 (337 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=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1838893 Title: Sorry, the program "chrome" closed unexpectedly Status in chromium-browser package in Ubuntu: New Bug description: When I walk away from my laptop for a half hour or so, Chrome Tab seems to crash. Seems to only affect one Tab if I have multiple Tabs open. Sorry, the program "chrome" closed unexpectedly. Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 10:35:14 2019 InstallationDate: Installed on 2018-08-31 (337 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=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838890] [NEW] Suspected memory leak in xenial backport of fix for CVE-2019-13012
Public bug reported: (This is only from source code inspection, not tested in real use - I don't actually use Ubuntu.) The upstream fix for CVE-2019-13012 included this change: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700); However, g_file_peek_path() was only introduced in GLib 2.56. The backport in the xenial package has this instead: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700); This is not equivalent. The difference between g_file_peek_path() and the older g_file_get_path() is that g_file_get_path() makes a copy, which must be freed with g_free() after use. As a result, there is now a memory leak. A non-leaky backport would look something like this, which is what I've done in a proposed backport for Debian 9 'stretch': + char *dir; ... - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + dir = g_file_get_path (kfsb->dir); + g_mkdir_with_parents (dir, 0700); + g_free (dir); ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1838890 Title: Suspected memory leak in xenial backport of fix for CVE-2019-13012 Status in glib2.0 package in Ubuntu: New Bug description: (This is only from source code inspection, not tested in real use - I don't actually use Ubuntu.) The upstream fix for CVE-2019-13012 included this change: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700); However, g_file_peek_path() was only introduced in GLib 2.56. The backport in the xenial package has this instead: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700); This is not equivalent. The difference between g_file_peek_path() and the older g_file_get_path() is that g_file_get_path() makes a copy, which must be freed with g_free() after use. As a result, there is now a memory leak. A non-leaky backport would look something like this, which is what I've done in a proposed backport for Debian 9 'stretch': + char *dir; ... - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + dir = g_file_get_path (kfsb->dir); + g_mkdir_with_parents (dir, 0700); + g_free (dir); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1838890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
Just a silent reminder: I have created a PPA ( https://launchpad.net/~nrbrtx/+archive/ubuntu/xorg-hotkeys ) with patched packages for Ubuntu 16.04 LTS (xenial, with HWE) and upwards (including upcoming 19.10), use its description for instructions. -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Just a silent reminder: I have created a PPA ( https://launchpad.net/~nrbrtx/+archive/ubuntu/xorg-hotkeys ) with patched packages for Ubuntu 16.04 LTS (xenial, with HWE) and upwards (including upcoming 19.10), use its description for instructions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Unknown Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: In Progress Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1234968] Re: 3rd party openoffice-debian-menus package tries installing «/usr/bin/soffice » but does not define needed conflicts with packages in the official archive
** Summary changed: - http://buytramadol-online.mystrikingly.com/ >> «/usr/bin/soffice » but does not define needed conflicts with packages in the official archive + 3rd party openoffice-debian-menus package tries installing «/usr/bin/soffice » but does not define needed conflicts with packages in the official archive ** Description changed: - This issue is due to installing the unsupported Apache OpenOffice. Don't do that unless you are aware of how to remove this unsupported software. - http://buytramadol-online.mystrikingly.com/ + This issue is due to installing the unsupported Apache OpenOffice. Don't + do that unless you are aware of how to remove this unsupported software. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20 Uname: Linux 3.5.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Thu Oct 3 16:21:34 2013 DpkgHistoryLog: Start-Date: 2013-10-03 16:21:26 Commandline: apt-get -f install Install: libreoffice-common:amd64 (3.5.7-0ubuntu4, automatic) DpkgTerminalLog: Desempaquetando libreoffice-common (de .../libreoffice-common_1%3a3.5.7-0ubuntu4_all.deb) ... dpkg: error al procesar /var/cache/apt/archives/libreoffice-common_1%3a3.5.7-0ubuntu4_all.deb (--unpack): intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.0-9702 DuplicateSignature: package:libreoffice-common:(not installed):intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.0-9702 ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.0-9702 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.0-9702 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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1234968 Title: 3rd party openoffice-debian-menus package tries installing «/usr/bin/soffice » but does not define needed conflicts with packages in the official archive Status in libreoffice package in Ubuntu: Invalid Bug description: This issue is due to installing the unsupported Apache OpenOffice. Don't do that unless you are aware of how to remove this unsupported software. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20 Uname: Linux 3.5.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Thu Oct 3 16:21:34 2013 DpkgHistoryLog: Start-Date: 2013-10-03 16:21:26 Commandline: apt-get -f install Install: libreoffice-common:amd64 (3.5.7-0ubuntu4, automatic) DpkgTerminalLog: Desempaquetando libreoffice-common (de .../libreoffice-common_1%3a3.5.7-0ubuntu4_all.deb) ... dpkg: error al procesar /var/cache/apt/archives/libreoffice-common_1%3a3.5.7-0ubuntu4_all.deb (--unpack): intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.0-9702 DuplicateSignature: package:libreoffice-common:(not installed):intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.0-9702 ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.0-9702 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.0-9702 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1234968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 689349] Re: [Upstream] Draw file exported to PDF have erroneous pixel-sized dots in Acroread, not in Evince
** Description changed: Binary package hint: openoffice.org Binary package hint: libreoffice - >> http://yourrxstore.com/product-category/buy-soma-online/ 1) lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 2) apt-cache policy libreoffice-draw libreoffice-draw: Installed: 1:3.6.2~rc2-0ubuntu4 Candidate: 1:3.6.2~rc2-0ubuntu4 Version table: *** 1:3.6.2~rc2-0ubuntu4 0 900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 400 http://archive.ubuntu.com/ubuntu/ quantal-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:3.6.2~rc2-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages apt-cache policy acroread acroread: Installed: 9.5.1-1precise1 Candidate: 9.5.1-1precise1 Version table: *** 9.5.1-1precise1 0 100 /var/lib/dpkg/status apt-cache policy evince evince: Installed: 3.6.0-0ubuntu2 Candidate: 3.6.0-0ubuntu2 Version table: *** 3.6.0-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one performs at the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/689349/+attachment/1763870/+files/classnetwork.odg && unoconv --listener && unoconv -f pdf classnetwork.odg && acroread classnetwork.pdf is it looks as it does in Evince. 4) What happens instead is acroread displays erroneous pixel-sized dots as per screenshot https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/689349/+attachment/1763844/+files/garbagescreenshot.png , while evince does not. First reproduced in Maverick 1:3.3.1-1ubuntu3~maverick1, and reproduced in Natty, and Precise. Unconfirmed OOo WORKAROUND: The upstream version does _not_ produce these effects and is fine. ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CheckboxSubmission: 30b6638832e19720cfe8f7a91e5798a4 CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2012-06-11 (164 days ago) InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha i386 (20120131.1) MarkForUpload: True Package: libreoffice 1:3.6.2~rc2-0ubuntu4 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Tags: quantal Uname: Linux 3.5.0-17-generic i686 UpgradeStatus: Upgraded to quantal on 2012-09-14 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- 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/689349 Title: [Upstream] Draw file exported to PDF have erroneous pixel-sized dots in Acroread, not in Evince Status in libreoffice package in Ubuntu: Fix Released Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org Binary package hint: libreoffice 1) lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 2) apt-cache policy libreoffice-draw libreoffice-draw: Installed: 1:3.6.2~rc2-0ubuntu4 Candidate: 1:3.6.2~rc2-0ubuntu4 Version table: *** 1:3.6.2~rc2-0ubuntu4 0 900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 400 http://archive.ubuntu.com/ubuntu/ quantal-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:3.6.2~rc2-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages apt-cache policy acroread acroread: Installed: 9.5.1-1precise1 Candidate: 9.5.1-1precise1 Version table: *** 9.5.1-1precise1 0 100 /var/lib/dpkg/status apt-cache policy evince evince: Installed: 3.6.0-0ubuntu2 Candidate: 3.6.0-0ubuntu2 Version table: *** 3.6.0-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one performs at the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/689349/+attachment/1763870/+files/classnetwork.odg && unoconv --listener && unoconv -f pdf classnetwork.odg && acroread classnetwork.pdf is it looks as it does in Evince. 4) What happens instead is acroread displays erroneous pixel-sized dots as per screenshot https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/689349/+attachment/1763844/+files/garbagescreenshot.png , while evince does not. First reproduced in Maverick 1:3.3.1-1ubuntu3~maverick1, and reproduced in Natty, and Precise. Unconfirmed OOo WORKAROUND: The upstream version does _not_ produce these effects and is fine.
[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
So. This problem is still here. I found following situation: On older 16.04 layout is changing with releasing Control/Shift/Alt keys. In 18.04 layout is changing while pressing key combination. May be it is setting somewhere in X.org? Is it possible to find and change it? It can affect all people in the world, that have non latin-like language as basic language. -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838876] [NEW] OBS Studio (snap) can't launch with GNOME on Wayland (there are no problems with X.org session)
Public bug reported:
artem@hp-250-g6-notebook-pc:~$ obs-studio
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva
error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit
/snap/obs-studio/525/usr/sbin:/snap/obs-studio/525/usr/bin:/snap/obs-studio/525/sbin:/snap/obs-studio/525/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
This application failed to start because it could not find or load the Qt
platform plugin "wayland-egl"
in "".
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, xcb.
Reinstalling the application may fix this problem.
Aborted (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.32.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 4 15:00:05 2019
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'app-picker-view' b'uint32 1'
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'Sundry',
'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'ua')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2019-08-04 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan wayland-session
--
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/1838876
Title:
OBS Studio (snap) can't launch with GNOME on Wayland (there are no
problems with X.org session)
Status in gnome-shell package in Ubuntu:
New
Bug description:
artem@hp-250-g6-notebook-pc:~$ obs-studio
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva
error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit
/snap/obs-studio/525/usr/sbin:/snap/obs-studio/525/usr/bin:/snap/obs-studio/525/sbin:/snap/obs-studio/525/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
This application failed to start because it could not find or load the Qt
platform plugin "wayland-egl"
in "".
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, xcb.
Reinstalling the application may fix this problem.
Aborted (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.32.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 4 15:00:05 2019
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'app-picker-view' b'uint32 1'
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities',
'Sundry', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'ua')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2019-08-04 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838876/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
Sorru for the late reply, I had a lot to do. I am not sure whether you have correctly taken the logs. Both are taken on July 25 but when you look into them, they span the following time frames: log-network-manager-with-segmentation.txt:Jan 31 - July 1 log-network-manager-without-segmentation.txt: Jan 31 - July 25 A "diff" shows also that all content of of the first is also in the second. It seems that the first got cut off during the upload. As they contain all history back to January, is it possible that the longer one (log-network-manager-without-segmentation.txt) contains both tests? Could you tell in which order you did the tests and which parts of the log reflect which test? Or could you re-test but this time reading the time stamps in the log before and after each test and upload only the logs of these time spans? -- 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/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837801] Re: [MESA] mesa 19.2 release will best support IceLake
** Package changed: ubuntu => mesa (Ubuntu) ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1837801 Title: [MESA] mesa 19.2 release will best support IceLake Status in intel: New Status in mesa package in Ubuntu: New Bug description: Description: MESA 19.2 release will best support IceLake platform. We'd better not miss it. 19.10 feature freeze is 08/22. 19.2-rc4 scheduled in 08/27, it should be the last release. 19.10 should can catch up with the final release of mesa 19.2. Target Release: 19.10 Target Package: 19.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1837801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837801] [NEW] [MESA] mesa 19.2 release will best support IceLake
You have been subscribed to a public bug: Description: MESA 19.2 release will best support IceLake platform. We'd better not miss it. 19.10 feature freeze is 08/22. 19.2-rc4 scheduled in 08/27, it should be the last release. 19.10 should can catch up with the final release of mesa 19.2. Target Release: 19.10 Target Package: 19.2 ** Affects: intel Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: intel-upkg-19.10 -- [MESA] mesa 19.2 release will best support IceLake https://bugs.launchpad.net/bugs/1837801 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838867] [NEW] Bionic HWE kernel 5.0.0.23 breaks nvidia driver 340.107
Public bug reported: When updating my system, I got the new 5.0.0.23 kernel (coming from 4.18.0-25). DKMS fails for the nvidia 340 driver. I need to use this for my generation card (ION). Make log included. X starts, but low-res. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-340 340.107-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Aug 4 11:35:26 2019 SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to bionic on 2018-05-08 (452 days ago) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kernel-bug nvidia ** Attachment added: "DKMS make.log (/var/lib/dkms/nvidia-340/340.107/build/make.log)" https://bugs.launchpad.net/bugs/1838867/+attachment/5280709/+files/make.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1838867 Title: Bionic HWE kernel 5.0.0.23 breaks nvidia driver 340.107 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: When updating my system, I got the new 5.0.0.23 kernel (coming from 4.18.0-25). DKMS fails for the nvidia 340 driver. I need to use this for my generation card (ION). Make log included. X starts, but low-res. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-340 340.107-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Aug 4 11:35:26 2019 SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to bionic on 2018-05-08 (452 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1838867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838868] [NEW] Desktop Bookmark from sidebar is removed and user-dirs.dirs config not working.
Public bug reported: All of a sudden I found that the Desktop bookmark from Nautilus's sidebar is removed. Please check the image bellow. https://raw.githubusercontent.com/devKamrul007/Nautilus-Bug- images/eaf3ef9517d4aa63e49dff4fc58ee49279e67a36/Screenshot%20from%202019-08-04%2013-42-44.png There is no desktop under Home. Moreover, I tried to fix the problem by editing ~/.config/user-dirs.dirs like bellow image. But, this seems to has no effect at all. https://raw.githubusercontent.com/devKamrul007/Nautilus-Bug- images/eaf3ef9517d4aa63e49dff4fc58ee49279e67a36/Screenshot%20from%202019-08-04%2013-29-43.png I am using Ubuntu 19.04 Disco Dingo latest 5.0.0-23. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2019-08-04 13-42-44.png" https://bugs.launchpad.net/bugs/1838868/+attachment/5280713/+files/Screenshot%20from%202019-08-04%2013-42-44.png -- 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/1838868 Title: Desktop Bookmark from sidebar is removed and user-dirs.dirs config not working. Status in nautilus package in Ubuntu: New Bug description: All of a sudden I found that the Desktop bookmark from Nautilus's sidebar is removed. Please check the image bellow. https://raw.githubusercontent.com/devKamrul007/Nautilus-Bug- images/eaf3ef9517d4aa63e49dff4fc58ee49279e67a36/Screenshot%20from%202019-08-04%2013-42-44.png There is no desktop under Home. Moreover, I tried to fix the problem by editing ~/.config/user-dirs.dirs like bellow image. But, this seems to has no effect at all. https://raw.githubusercontent.com/devKamrul007/Nautilus-Bug- images/eaf3ef9517d4aa63e49dff4fc58ee49279e67a36/Screenshot%20from%202019-08-04%2013-29-43.png I am using Ubuntu 19.04 Disco Dingo latest 5.0.0-23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
I have the same problem on Ubuntu 18.04 and Samsung Galaxy S9 (Android 9). -- 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/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1279060] Re: MIssing voicemail info for French provider Free
Please submit this change upstream, see: https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders#How_to_Contribute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mobile-broadband-provider-info in Ubuntu. https://bugs.launchpad.net/bugs/1279060 Title: MIssing voicemail info for French provider Free Status in mobile-broadband-provider-info package in Ubuntu: New Bug description: I'm not sure if I just need to add 666 in the xml or if there are some wizardries to do, so I just open a bug for now. Provider is Free Mobile, country is France, and voicemail number is 666. Thanks :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1279060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)
Hello everyone! No I have already tested Ubuntu 19.10 on Wayland. I have noticed that I don't see the problem with window flickering to black. Animations are more smoothly and beautiful: https://photos.app.goo.gl/1WiGYQziTSnrjrfz9 . I think Ubuntu 20.04 LTS should go with Wayland session as default. Why? Debian and Fedora use Wayland as a default. GNOME 3.34 will support good launching of X programms with XWayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I see the black zones, small windows breaks. For additional details, I use eoan-proposed and eoan-backports packages. You can see this problem in my video: https://photos.app.goo.gl/3rvLkqJj6hZwSscw9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 5 13:39:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (3 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
