[Desktop-packages] [Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 >Aside from anything else, JournalErrors.txt above is showing this bug is from Nvidia driver version 364.19 which doesn't seem to have ever been officially released so is not supported: It was from the unofficial "official" Ubuntu Nvidia driver PPA. I remember issues with resuming from suspend was a noted problem on Nvidia's website at the time although I don't know if they were referring to this bug specifically. >But regardless of the driver version, Nvidia is closed source so neither Canonical nor the community have any power to fix it. We can only track its bugs. Fine. What about the hundred(thousands?) of other critical bugs with open source software that Ubuntu could fix? Like https://bugs.launchpad.net/ubuntu/+source/gnome- software/+bug/1575426 OR https://bugs.launchpad.net/ubuntu/xenial/+source/gnome- session/+bug/1575434 Which was marked as "fixed" because it was fixed in a newer Gnome version. Presumably it's still an issue on 16.04. What the actual hell? -- 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/1576859 Title: [nvidia] Graphics corruption when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Resuming from suspend results in graphical glitches. These glitches, at least on the cover screen(shows date/time) go away when the Hard Drive spins back up. Additional corruption can occur in overview on currently active applications(Such as Chromium). Description: Ubuntu 16.04 LTS Release: 16.04 gnome-shell: Installed: 3.18.4-0ubuntu3 Candidate: 3.18.4-0ubuntu3 Version table: *** 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 29 15:56:14 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-23 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1819306] Re: 100% cpu in libreoffice
Hi Olivier Tilloy. That bug of the laptop overheating like crazy when LibreOffice is running (which seemed to be that LibreOffice was hogging a bunch of CPU all the sudden) seems to not be happening anymore. This is in reference to https://bugs.launchpad.net/bugs/1819306 . Thanks again. B On Wed, Mar 20, 2019 at 1:31 PM Olivier Tilloy wrote: > Can you share the output of: > > apt policy libreoffice-core > > Were you editing relatively big files when this happened? > > Could you try running libreoffice with the --safe-mode parameter and see > if this happens again? > > ** Changed in: libreoffice (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1819306 > > Title: > 100% cpu in libreoffice > > Status in libreoffice package in Ubuntu: > Incomplete > > Bug description: > I've been seeing high cpu from libreoffice in the last week (today is > 3/9/2019). I had a bunch of files open, but nothing actively > happening. The circumstances don't seem to match the other reports of > high cpu. > > It's happened twice. Each time, the only solution I found was to > restart libreoffice. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: libreoffice (not installed) > ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 > Uname: Linux 4.15.0-45-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 9 23:51:06 2019 > InstallationDate: Installed on 2018-12-01 (98 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: libreoffice > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819306/+subscriptions > -- 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/1819306 Title: 100% cpu in libreoffice Status in libreoffice package in Ubuntu: Incomplete Bug description: I've been seeing high cpu from libreoffice in the last week (today is 3/9/2019). I had a bunch of files open, but nothing actively happening. The circumstances don't seem to match the other reports of high cpu. It's happened twice. Each time, the only solution I found was to restart libreoffice. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 23:51:06 2019 InstallationDate: Installed on 2018-12-01 (98 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: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Sounds reasonable. Thanks for letting me know. -- 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/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in gnome-shell source package in Cosmic: Triaged Status in mutter source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Triaged Status in mutter source package in Disco: Triaged Bug description: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log-out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822254] [NEW] Can't drag and drop files to Desktop on Disco 19.04 beta
You have been subscribed to a public bug: Summary: Can't drag and drop files to Desktop on Disco 19.04 beta Steps to reproduce: 1. Click "Files" on luncher 2. Select some files 3. Drag and drop the files to desktop (Disco Dingo wallpaper) Expected result: Drag and drop the files to desktop successfully Actual result: Can't drap and drop files to desktop Addtional information: Drag and drog the files in "Files" to "Desktop" folder were succesful and the files show on desktop (Disco Dingo wallpapaer) Failure rate: 100% - CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x) system-product-name: Precision 5530 bios-version: 1.6.0 system-manufacturer: Dell Inc. GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: ce-qa-concern disco -- Can't drag and drop files to Desktop on Disco 19.04 beta https://bugs.launchpad.net/bugs/1822254 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons 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 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta
** Package changed: ubuntu => gnome-shell-extension-desktop-icons (Ubuntu) -- 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/1822254 Title: Can't drag and drop files to Desktop on Disco 19.04 beta Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Summary: Can't drag and drop files to Desktop on Disco 19.04 beta Steps to reproduce: 1. Click "Files" on luncher 2. Select some files 3. Drag and drop the files to desktop (Disco Dingo wallpaper) Expected result: Drag and drop the files to desktop successfully Actual result: Can't drap and drop files to desktop Addtional information: Drag and drog the files in "Files" to "Desktop" folder were succesful and the files show on desktop (Disco Dingo wallpapaer) Failure rate: 100% - CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x) system-product-name: Precision 5530 bios-version: 1.6.0 system-manufacturer: Dell Inc. GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1822254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Neither of those bugs are critical or affecting many people at all. So that's why no developers seem to have fixed them for 16.04 yet. We have several orders of magnitude more bugs than we can possibly hope to fix. But I do understand your frustration -- I made exactly the same complaint to Canonical years before joining Canonical. As for Gnome Shell bugs, those are especially unlikely to ever get touched because Ubuntu only really started supporting Gnome Shell properly in 17.10 (which is already past end of life). So Gnome Shell bugs will generally be fixed in Ubuntu 18.04 and later. I know Ubuntu- GNOME existed long before that, but it's not a flavor that the main desktop team supports. -- 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/1576859 Title: [nvidia] Graphics corruption when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Resuming from suspend results in graphical glitches. These glitches, at least on the cover screen(shows date/time) go away when the Hard Drive spins back up. Additional corruption can occur in overview on currently active applications(Such as Chromium). Description: Ubuntu 16.04 LTS Release: 16.04 gnome-shell: Installed: 3.18.4-0ubuntu3 Candidate: 3.18.4-0ubuntu3 Version table: *** 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 29 15:56:14 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-23 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822258] [NEW] package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet
Public bug reported: unable to use my fingerprint ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libfprint-dev (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 AptOrdering: aes2501-wy:amd64: Install libfprint-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 29 08:48:45 2019 ErrorMessage: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: libfprint Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1822258 Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 Status in libfprint package in Ubuntu: New Bug description: unable to use my fingerprint ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libfprint-dev (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 AptOrdering: aes2501-wy:amd64: Install libfprint-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 29 08:48:45 2019 ErrorMessage: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: libfprint Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1822258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted
Is this a regression from older releases? when you say that disabling switchable graphics makes it use nvidia, I'd doubt that.. it should use intel then? ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (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/1821882 Title: Screen is very dark and brightness cannot be adjusted Status in linux package in Ubuntu: Incomplete Bug description: Device: Dell Precision 7530 In the BIOS, the Switchable Graphics option is deactived, which means only the nVidia GPU is used. When booting 19.04 beta live USB, the screen becomes very dark and brightness cannot be adjusted. (The same issue happens with 18.04.2) There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no intel_backlight): $ ll /sys/class/backlight/ total 0 drwxr-xr-x 2 root root 0 Mar 27 09:36 ./ drwxr-xr-x 74 root root 0 Mar 27 09:28 ../ lrwxrwxrwx 1 root root 0 Mar 27 09:28 nv_backlight -> ../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/ Trying to manually change brightness doesn't do anything: $ sudo su root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight root@ubuntu:/sys/class/backlight/nv_backlight# ll total 0 drwxr-xr-x 3 root root0 Mar 27 09:28 ./ drwxr-xr-x 4 root root0 Mar 27 09:28 ../ -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/ -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness drwxr-xr-x 2 root root0 Mar 27 09:28 power/ lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> ../../../../../../../../class/backlight/ -r--r--r-- 1 root root 4096 Mar 27 09:28 type -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness 50 Although the value is changed, the screen brightness doesn't change. in dmesg, I can see the following: [0.241878] ACPI: Added _OSI(Module Device) [0.241878] ACPI: Added _OSI(Processor Device) [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions) [0.241878] ACPI: Added _OSI(Processor Aggregator Device) [0.241878] ACPI: Added _OSI(Linux-Dell-Video) [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [0.286326] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.286336] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287096] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287102] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287858] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287864] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.288614] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.288619] ACPI: Skipping parse of AML opcode: Met
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
No additional scaling is set, everything is 100%. It does feel like there is some acceleration going on though. The offset seems consistent to shell, apps and the backdrop. e.g. I position a window on the right hand screen and I can grab the top of it by dragging on the left screen. -- 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/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: New Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
It sounds like touches are being scaled to stage coordinates instead of view coordinates. So a touch halfway across the touch screen gets mapped to a desktop location halfway across all monitors. Just a guess. ** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: New Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's
leaving cosmic out, this will only be needed in disco and bionic. ** Description changed: + [Impact] + Please make it happen in the coming oem-kernel as there will be a flood - of Intel CML platforms that would need it. Thank you. + of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. + + [Test case] + + Test that i915 graphics works on CML. + + [Regression potential] + + None really, these only add a bunch of new pci-id's across the stack. ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libdrm (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: xorg-server (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Description changed: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. + + CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and + doesn't need other changes than pci-id's and support for the PCH + (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's
** Changed in: linux (Ubuntu Bionic) Status: New => Invalid -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821863] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1821863 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723039] Re: with 2 monitors, touchscreen is not disabled when the internal display is disabled
Actually it sounds like this might be a feature added after: https://bugzilla.gnome.org/show_bug.cgi?id=766762 ** Bug watch added: GNOME Bug Tracker #742598 https://gitlab.gnome.org/742598 ** Also affects: mutter via https://gitlab.gnome.org/742598 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1723039 Title: with 2 monitors, touchscreen is not disabled when the internal display is disabled Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Fix Released Bug description: With an external monitor attached and the internal display being a touch screen, set the output to the external display only. The internal display is disabled (it is turned off) but the touch screen is still active. The actions are visible on the external display (eg selection, osk) but it not useful (for example the osk is displayed but cannot be used) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 10:47:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2014-07-23 (1176 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-06-13 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1723039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723039] Re: with 2 monitors, touchscreen is not disabled when the internal display is disabled
Apparently Fix Released in disco (mutter 3.31.4 onward) -- 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/1723039 Title: with 2 monitors, touchscreen is not disabled when the internal display is disabled Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Fix Released Bug description: With an external monitor attached and the internal display being a touch screen, set the output to the external display only. The internal display is disabled (it is turned off) but the touch screen is still active. The actions are visible on the external display (eg selection, osk) but it not useful (for example the osk is displayed but cannot be used) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 10:47:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2014-07-23 (1176 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-06-13 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1723039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723039] Re: With 2 monitors, touches to the touch screen appear across both (and in the wrong place)
Touches should never be reaching the external monitor regardless of whether the internal screen is on or off. So we're tracking that as bug 1821933 now. ** Bug watch added: GNOME Bug Tracker #766762 https://gitlab.gnome.org/766762 -- 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/1723039 Title: with 2 monitors, touchscreen is not disabled when the internal display is disabled Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Fix Released Bug description: With an external monitor attached and the internal display being a touch screen, set the output to the external display only. The internal display is disabled (it is turned off) but the touch screen is still active. The actions are visible on the external display (eg selection, osk) but it not useful (for example the osk is displayed but cannot be used) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 10:47:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2014-07-23 (1176 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-06-13 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1723039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723039] Re: with 2 monitors, touchscreen is not disabled when the internal display is disabled
The fix was https://gitlab.gnome.org/GNOME/mutter/commit/d30301c0 ** Also affects: mutter (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Tags removed: artful -- 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/1723039 Title: with 2 monitors, touchscreen is not disabled when the internal display is disabled Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Fix Released Bug description: With an external monitor attached and the internal display being a touch screen, set the output to the external display only. The internal display is disabled (it is turned off) but the touch screen is still active. The actions are visible on the external display (eg selection, osk) but it not useful (for example the osk is displayed but cannot be used) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 10:47:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2014-07-23 (1176 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-06-13 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1723039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
I can also confirm the problem. The Ubuntu 18.04LTS (updated everything) does NOT sense when I disconnect the HDMI. There is no change in /sys. This uis the mainb problem, I guess. The events does not generate screen switching. Very annoying when the screen locked and disconnected from external monitor, the notebook display remaions black! I checked the status, and it STILL shown connected but the HDMI monitor was disconnected: root@notebook:~# cat /sys/class/drm/card0-HDMI-A-1/status connected root@notebook:~# cat /sys/class/drm/card0-HDMI-A-1/status connected root@notebook:~# cat /sys/class/drm/card0-HDMI-A-1/status HW: Dell Lattitude 7490 Sometimes work, sometimes NOT. It is very annoying when I work with the notebook, it's screen remains black after I disconnect the external monitor. I created Keyboard shortucts to force screen UP: Lspci: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 (rev 21) 00:15.3 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #3 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:16.3 Serial controller: Intel Corporation Device 9d3d (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) -- root@notebook:~# uname -a Linux notebook 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- -- 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/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in xorg-server package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
The problem appears to be that clutter_input_device_evdev_translate_coordinates has no idea that the stage might include multiple monitors: https://gitlab.gnome.org/GNOME/mutter/blob/master/clutter/clutter/evdev /clutter-input-device-evdev.c#L1509 Sadly I can't see any information that would help to correct it either. It would be a bit of a redesign. -- 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/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
Hello Matthias, or anyone else affected, Accepted libidn into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libidn/1.33-2.2ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libidn (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: In Progress Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: In Progress Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
That would be a consequence of the "touch screen" input device not having any relation in software to the "screen" output device. They are very separate things :( -- 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/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
Experimental fix: https://gitlab.gnome.org/GNOME/mutter/commit/4a06424b9c1de7242cec0613bc1fd53c832d9144.patch -- 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/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
Hello Matthias, or anyone else affected, Accepted libidn into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libidn/1.33-2.1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libidn (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: libunistring (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco
Um, good question. The volume in Gnome shell top right panel, as well in Gnome settings, appears muted (and it is muted when I try to play things). All I need to do is unmute / press volume up or down to fix this, it's just a small niggle. The only extension that I have is extended-gestures. The startup applications are `Snap user application autostart helper` and `SSH Key Agent`. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1821904 Title: Gnome Shell always started muted on Disco Status in pulseaudio package in Ubuntu: Incomplete Bug description: On Disco, Gnome Shell always starts muted. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe4766 F pulseaudio /dev/snd/pcmC0D0p: joe4766 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-09-15 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco wayland-session Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813587] Please test proposed package
Hello Matthias, or anyone else affected, Accepted libunistring into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libunistring/0.9.10-1ubuntu1.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
Untested fix as a PPA: https://launchpad.net/~vanvugt/+archive/ubuntu/lp1821933 -- 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/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
Sorry, ignore the above, they are wrong. It is a bit more non-trivial than that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic
Thanks Daniel - I have raised the issue here https://gitlab.gnome.org/GNOME/mutter/issues/536 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #536 https://gitlab.gnome.org/GNOME/mutter/issues/536 -- 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/1811900 Title: SRU 3.28 latest git to bionic Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] 3.28 gnome git branch has various upstream approved fixes for many months now, but no release has been done yet, thus we're releasing a git snapshot of the latest approved fixes. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been included in upstream git now, various optimizations to clutter actors could cause drawing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794425] Re: doesn't work with i3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screenshot (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1794425 Title: doesn't work with i3 Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: `gnome-screenshot` doesn't work with i3 $ gnome-screenshot --area --clipboard ** Message: 17:12:05.576: Unable to select area using GNOME Shell's builtin screenshot interface, resorting to fallback X11. ** Message: 17:12:09.870: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11. Selection works, but buffer is empty. Checking file size: $ xsel -po > 1 && xsel -so > 2 && xsel -bo > 3 && ls -l 1 2 3 -rw-rw-r-- 1 techtonik techtonik 2 Sep 25 17:14 1 -rw-rw-r-- 1 techtonik techtonik 0 Sep 25 17:14 2 -rw-rw-r-- 1 techtonik techtonik 0 Sep 25 17:14 3 `i3` developers told that it is not a bug in `i3` - https://github.com/i3/i3/issues/3422 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screenshot 3.25.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18 Uname: Linux 4.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: i3 Date: Wed Sep 26 09:56:49 2018 SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to bionic on 2018-08-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1794425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822276] [NEW] Folder where a document was saved last is not saved
Public bug reported: This is probably a "duplicate" of a bug, which was fixed in evince 2.27, but now in evince 3.30 it seems to reappear again. Additionally, I am not sure if this is an evince bug or a gtk3 bug. The main problem is that the folder where a document was saved last is never stored. So for me a common workflow is downloading a pdf of a scientific publication and I need to store it somewhere in my filesystem. In many other instances (sumatrapdf on windows) the folder where I saved the last pdf is always stored. This means after I saved the first document for all subsequent documents I don't need to navigate the file system again. At the moment evince always starts in the home folder and I need to navigate through my filesystem again. This is on fedora 29 with evince 3.30.2 and gtk3 3.24.1. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1822276 Title: Folder where a document was saved last is not saved Status in evince package in Ubuntu: New Bug description: This is probably a "duplicate" of a bug, which was fixed in evince 2.27, but now in evince 3.30 it seems to reappear again. Additionally, I am not sure if this is an evince bug or a gtk3 bug. The main problem is that the folder where a document was saved last is never stored. So for me a common workflow is downloading a pdf of a scientific publication and I need to store it somewhere in my filesystem. In many other instances (sumatrapdf on windows) the folder where I saved the last pdf is always stored. This means after I saved the first document for all subsequent documents I don't need to navigate the file system again. At the moment evince always starts in the home folder and I need to navigate through my filesystem again. This is on fedora 29 with evince 3.30.2 and gtk3 3.24.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1822276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
More testing: Testing on Fedora with GNOME 3.32 under their default wayland session, touch events seem to be positioned correctly. Testing on Disco under the Wayland session touch on the dock and parts of shell that are on the left of the screen seems to work, but touch- dragging on the background doesnt seem to work at all. -- 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/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using touch input with one screen seems fine. However, when connecting a second screen the touch event happens at the wrong coordinates. Steps to reproduce 1. Starting with a single screen touch and hold on the background and drag. The rubber band selector shows up with the moving corner at your finger. 2. Connect a second screen 3. Do the same touch and drag as in step 1 and notice that the moving corner is offset to the right and slightly below where the touch is happening. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco Uname: Linux 5.0.0-7-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/gnome-shell/+bug/1821933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822306] [NEW] PCI/internal sound card not detected
Public bug reported: Can't open "alsamixer". Can't fix my laptop's sound. My laptop sound stoped working after upgrading Ubuntu 14.04.6 LTS. I checked Alsamixer but I could't open it. I tryed to reinstall pulse audio and Alsa but yet, Alsamixer doesn't open. I'm getting the following error message when I try to open Alsamixer: me@me-Inspiron-15-3552:~$ alsamixer cannot open mixer: No such file or directory I would appreciate some help ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 12:38:04 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1822306 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Can't open "alsamixer". Can't fix my laptop's sound. My laptop sound stoped working after upgrading Ubuntu 14.04.6 LTS. I checked Alsamixer but I could't open it. I tryed to reinstall pulse audio and Alsa but yet, Alsamixer doesn't open. I'm getting the following error message when I try to open Alsamixer: me@me-Inspiron-15-3552:~$ alsamixer cannot open mixer: No such file or directory I would appreciate some help ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 12:38:04 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240336] Re: Buy Tramadol Online and Familiarize Yourself with Pain Medication
** Summary changed: - After release upgrade, the user loses permissions for several basic actions in the system + Buy Tramadol Online and Familiarize Yourself with Pain Medication ** Description changed: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. + + https://usapillspharma.com/ RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges 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 policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Buy Tramadol Online and Familiarize Yourself with Pain Medication Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. https://usapillspharma.com/ RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
This is something that is currently fixing just a build failure, not something that the end user is affected... Marking as verification done (and I'm using the package because my system is on bionic) ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
** Summary changed: - Buy Tramadol Online and Familiarize Yourself with Pain Medication + After release upgrade, the user loses permissions for several basic actions in the system ** Description changed: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. - - https://usapillspharma.com/ RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges 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 policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Hi, I don't know if that's correct because in Ubuntu 18.10 I had no issue, I will provide more information once I'll get on my PC -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: New Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1522727] Re: Work Mechanism and Dosage
** Summary changed: - X.org crashes intermittently, randomly, back to the login screen + Work Mechanism and Dosage ** Description changed: Since upgrading to Ubuntu 15.10, X.org crashes intermittently. The screen will suddenly turn black, and after a few seconds, the LightDM login screen appears. All unsaved work is lost of course. + + https://usapillspharma.com/product-category/buy-phentermine-online/ A clean install of 15.10 did not help, the problem persists. It happens absolutely randomly. I haven't been able to figure out any pattern related to time or specific user interaction that would cause this, except that I believe the crash is always triggered by some kind of input device action, i.e. mouse click or key press. The system won't crash if I don't actively do any work. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-core 2:1.17.2-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: - Scanning for Btrfs filesystems - fsck from util-linux 2.26.2 - /dev/sda1: clean, 365974/2501856 files, 2841542/755 blocks + Scanning for Btrfs filesystems + fsck from util-linux 2.26.2 + /dev/sda1: clean, 365974/2501856 files, 2841542/755 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Dec 4 08:50:28 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 4.2.0-18-generic, x86_64: installed - acpi-call, 1.1.0, 4.2.0-19-generic, x86_64: installed - vboxhost, 5.0.8, 4.2.0-18-generic, x86_64: installed - vboxhost, 5.0.8, 4.2.0-19-generic, x86_64: installed + acpi-call, 1.1.0, 4.2.0-18-generic, x86_64: installed + acpi-call, 1.1.0, 4.2.0-19-generic, x86_64: installed + vboxhost, 5.0.8, 4.2.0-18-generic, x86_64: installed + vboxhost, 5.0.8, 4.2.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:21fb] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:21fb] InstallationDate: Installed on 2015-10-25 (39 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 2356AB2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=794b7585-5080-4bd4-a642-688538787fea ro quiet splash vt.handoff=7 SourcePackage: xorg-server UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET63WW (2.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356AB2 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET63WW(2.05):bd11/12/2012:svnLENOVO:pn2356AB2:pvrThinkPadT430s:rvnLENOVO:rn2356AB2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356AB2 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Dec 4 08:49:37 2015 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id8510 - vendor AUO + product id8510 + vendor AUO xserver.version: 2:1.17.2-1ubuntu9.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1522727 Title: Work Mechanism and
[Desktop-packages] [Bug 571970] Re: gvfsd-http leaves a lot of sockets in CLOSE_WAIT state
** Summary changed: - buy adderall online overnight delivery in usa + gvfsd-http leaves a lot of sockets in CLOSE_WAIT state ** Description changed: - Order Now - buy Adderall online overnight delivery in the USA at onlinemedzonline. - - When you buy Adderall XR, you get the extended-release version of the - drug prescribed for the treatment of anxiety and panic disorders. Most - people who choose to buy the drug buy it without a prescription, which - may help them in the drug’s intake but will harm them in the long run. - When you take the drug, the effects of the drug last for as long as - 18-24 hours on the first day of intake or for the first few days when - you start taking it. - - Binary package hint: gvfs-backends netstat -tp reveals lots of the old connections made by gvfsd-http, and some of them are several days old. this seams like a resource leak. not very harmful for typical user, but the intense use of gvfsd could even block the user from making any new internet connections until the daemon is restarted. steps to reproduce: 1. use drag&drop to copy a picture from a web browser to the gnome desktop (this uses gvfs internally). interestingly, copying a content from clickable link did not leave a stale socket (i don't know if this is a rule. "open image in a new tab" and dragging from there was the most reliable way to reproduce the bug) 2. invoke netstat -tp in the console the socket opened by gvfsd-http wont go away workaround: kill the daemon (using killall gvfsd-http) or log out ProblemType: Bug Architecture: i386 Date: Fri Apr 30 02:22:47 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/lib/gvfs/gvfsd-http NonfreeKernelModules: nvidia Package: gvfs-backends 1.4.1-0ubuntu1 ProcEnviron: - SHELL=/bin/bash - PATH=(custom, user) - LANGUAGE=en_US.UTF-8 - LANG=en_US.UTF-8 + SHELL=/bin/bash + PATH=(custom, user) + LANGUAGE=en_US.UTF-8 + LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-20.58-generic SourcePackage: gvfs Uname: Linux 2.6.31-20-generic i686 - buy adderall online - adderall buy - adderall for sale - adderall online pharmacy - buy adderall without getting a prescription - adderall buy online - where can i buy adderall - adderall without prescription - order adderall online - adderall online cheap - buying adderall - buy adderal online - online adderall - adderall purchase - can you order adderall online - where to buy adderall online - how to buy real adderall online - adderall pills for sale - adderall without a prescription - buy adderall on internet - how to get adderall online - online pharmacy adderall - adderall online no prescription - buy amphetamine salts online - adderall online without prescription - aderall online - buy adderal - buying adderall online forum - adderal online - adderall on line - adderall for sale online - buy adderall 10mg online - adderrall online - where to buy real adderall online - how to get an adderall prescription online - adderall sale -- 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/571970 Title: gvfsd-http leaves a lot of sockets in CLOSE_WAIT state Status in gvfs package in Ubuntu: Expired Bug description: Binary package hint: gvfs-backends netstat -tp reveals lots of the old connections made by gvfsd-http, and some of them are several days old. this seams like a resource leak. not very harmful for typical user, but the intense use of gvfsd could even block the user from making any new internet connections until the daemon is restarted. steps to reproduce: 1. use drag&drop to copy a picture from a web browser to the gnome desktop (this uses gvfs internally). interestingly, copying a content from clickable link did not leave a stale socket (i don't know if this is a rule. "open image in a new tab" and dragging from there was the most reliable way to reproduce the bug) 2. invoke netstat -tp in the console the socket opened by gvfsd-http wont go away workaround: kill the daemon (using killall gvfsd-http) or log out ProblemType: Bug Architecture: i386 Date: Fri Apr 30 02:22:47 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/lib/gvfs/gvfsd-http NonfreeKernelModules: nvidia Package: gvfs-backends 1.4.1-0ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANGUAGE=en_US.UTF-8 LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-20.58-generic SourcePackage: gvfs Uname: Linux 2.6.31-20-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/571970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Hi Daniel, I've seen you marked my bug as this duplicate, but for me this doesn't happen on Ubuntu 18.10, only after the 19.04 upgrade -- 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] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: 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/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://
[Desktop-packages] [Bug 1822315] [NEW] PCI/internal sound card not detected
Public bug reported: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1822315 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822313] [NEW] PCI/internal sound card not detected
Public bug reported: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1822313 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822314] [NEW] PCI/internal sound card not detected
Public bug reported: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1822314 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1778566 Title: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU) Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When Wayland is activated in GDM, nothing happens when selecting an account with the keyboard or typing in the password. I have to type, then wait, then move the mouse around for the characters to appears. Because I wouldn't believe this report, I made a video of the problem: https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf- f2a74f952ca5 Moving from Wayland to X makes the issue disappear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 18:39:19 2018 InstallationDate: Installed on 2018-06-17 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1778566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1778566 Title: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU) Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When Wayland is activated in GDM, nothing happens when selecting an account with the keyboard or typing in the password. I have to type, then wait, then move the mouse around for the characters to appears. Because I wouldn't believe this report, I made a video of the problem: https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf- f2a74f952ca5 Moving from Wayland to X makes the issue disappear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 18:39:19 2018 InstallationDate: Installed on 2018-06-17 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1778566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822349] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1821404 *** https://bugs.launchpad.net/bugs/1821404 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1821404, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1822349/+attachment/5250678/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1822349/+attachment/5250680/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1822349/+attachment/5250683/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1822349/+attachment/5250684/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1822349/+attachment/5250685/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1822349/+attachment/5250686/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1822349/+attachment/5250687/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1821404 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822349 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: Gedit sometimes takes some time before opening and sometimes forcefully shuts down.Sometimes it works perfectly,but then also it asks that gedit has stopped working and to restart it. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 21:38:00 2019 ExecutablePath: /usr/bin/gedit ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_IN SegvAnalysis: Segfault happened at: 0x7f8a52b0067a : mov(%rax),%esi PC (0x7f8a52b0067a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: Upgraded to disco on 2019-03-17 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1822349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1503310] Re: window content doesn't refresh, only if window is moved
I just did an apt upgrade yesterday (using 18.04) and have now acquired
this same problem. I can force a repaint by minimizing and then
unminimizing the window.
--
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/1503310
Title:
window content doesn't refresh, only if window is moved
Status in compiz package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
Confirmed
Bug description:
I suppose this is a bug with the nvidia driver, but I'm not sure.
After the second-to-last routine software update (which I think
updated the nvidia driver), changing window content is only refreshed
if the window is moved.
Ubuntu 12.04.5 LTS, kernel 3.2.0-91-generic,
NVidia driver installed: 340.93-0ubuntu0.0.0.1,
Thinkpad laptop with nvidia graphics card (see below),
Window manager: Gnome Classic
How to reproduce the bug: Log in under Gnome Classic. Open Gnome
terminal. Execute some command (ls). Open new tab in terminal. Execute
some other command (ps), just to have different tab contents. Switch
back and forth between the tabs using the mouse. After some switches,
neither the tab rider is activated nor the tab content is refreshed
any longer. Only if you move the window, the tab rider gets activated
and the tab content is refreshed. The same problem occurs in other
applications (e.g. in thunderbird when selecting an email --- email
list entry is not marked and email content is not shown, only if you
move the window), so it is not application-specific.
The bug disappears when using the window manager "Gnome Classic (no
effects)" instead (which is "non-compositing" in contrast to "Gnome
Classic"). The bug is also present in other window magagers
("Ubuntu").
Side remark: I tried but failed to switch back to an earlier version
of the nvidia driver (from 340 to 331) using synaptic: When
deinstalling 340 and installing 331 instead, synaptic complains that
it depends on 340. So I can only guess that the bug is caused by the
nvidia driver.
Any help would be highly appreciated as the bug is really annoying.
% nvidia-smi
Tue Oct 6 16:13:30 2015
+--+
| NVIDIA-SMI 340.93 Driver Version: 340.93 |
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC
|
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M.
|
|===+==+==|
| 0 NVS 5400M Off | :01:00.0 N/A | N/A
|
| N/A 44CP8N/A / N/A |194MiB / 1023MiB | N/A Default
|
+---+--+--+
+-+
| Compute processes: GPU Memory
|
| GPU PID Process name Usage
|
|=|
|0Not Supported
|
+-+
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nvidia-340 340.93-0ubuntu0.0.0.1
ProcVersionSignature: Ubuntu 3.2.0-91.129-generic 3.2.71
Uname: Linux 3.2.0-91-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.11
Architecture: amd64
Date: Tue Oct 6 16:10:32 2015
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/tcsh
SourcePackage: nvidia-graphics-drivers-340
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1503310/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799688] Re: New thumbnails for PDF files not shown
*** This bug is a duplicate of bug 1798091 *** https://bugs.launchpad.net/bugs/1798091 This solution doesn't work for me -- 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/1799688 Title: New thumbnails for PDF files not shown Status in nautilus package in Ubuntu: Confirmed Bug description: Since upgrade to 18.10 any new PDF file shows the red acrobat icon instead of a thumbnail. Nautilus shows the time icon as though it's computing the thumbnail but then displays the default icon instead. - PDF thumbnails computed before the update still show - thumbnails for videos as images work as expected. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-33.37~lp1792100Commit3dfa1c904fcf138-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 14:15:42 2018 InstallationDate: Installed on 2018-01-05 (291 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to cosmic on 2018-10-22 (1 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1799688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco
Just to confirm, I also did this upgrade path (18.04 -> 18.10 -> 19.04) on my desktop and I get the same issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1821904 Title: Gnome Shell always started muted on Disco Status in pulseaudio package in Ubuntu: Incomplete Bug description: On Disco, Gnome Shell always starts muted. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe4766 F pulseaudio /dev/snd/pcmC0D0p: joe4766 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-09-15 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco wayland-session Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)
I have evince (3.30.1-1ubuntu1.2) cosmic but bug is not fixed for me -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1798091 Title: thumbnailer cannot create tempfiles (with apparmor denials) Status in evince package in Ubuntu: Fix Released Status in evince source package in Cosmic: Fix Released Status in evince source package in Disco: Fix Released Status in evince package in Debian: Fix Released Bug description: * Impact Nautilus fails to generate previews for pdf files * Test case Download/copy a pdf, open the directory in nautilus, a preview image should be displayed * Regression potential Check that there are no other apparmor denials and the thumbnailer works - While trying to create thumbnails in a directory from within nautilus, I got: [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 14:59:00 2018 InstallationDate: Installed on 2014-06-19 (1580 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1798091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822075] Re: tooltips and combo boxes in webbrowsers are all garbage in xserver-xorg-video-radeon 1:19.0.0-1
This bug was fixed in the package xserver-xorg-video-ati - 1:19.0.1-0ubuntu1 --- xserver-xorg-video-ati (1:19.0.1-0ubuntu1) disco; urgency=medium * Sync with debian git. xserver-xorg-video-ati (1:19.0.1-1) UNRELEASED; urgency=medium * New bugfix release. (Closes: #924540) (LP: #1822075) -- Timo Aaltonen Thu, 28 Mar 2019 13:15:14 +0200 ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Triaged => Fix Released -- 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/1822075 Title: tooltips and combo boxes in webbrowsers are all garbage in xserver- xorg-video-radeon 1:19.0.0-1 Status in gtk+3.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Bug description: Disco up to date With Chrome and Firefox tooltips and combo boxes are all garbage and make the browser unusable. Cf screenshots. Graphics card: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] I tried gtk2 and gtk3 demos and the combo boxes are broken in the same way. I also tried FF as a snap and as a deb and the problem is the same. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 11:51:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1717 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-03-24 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822350] Re: evince crashed with SIGABRT in g_assertion_message()
https://gitlab.gnome.org/GNOME/evince/issues/1120 ** Description changed: Click in 'File options->Dual' my PDF. + + JournalErrors.txt: + mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to 'EvWindow' + mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: ** + mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: GLib:ERROR:../../../glib/ghash.c:468:g_hash_table_lookup_node: assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count, 0)) + mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to 'EvWindow' ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Information type changed from Private to Public ** Description changed: Click in 'File options->Dual' my PDF. - - JournalErrors.txt: - mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to 'EvWindow' - mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: ** - mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: GLib:ERROR:../../../glib/ghash.c:468:g_hash_table_lookup_node: assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count, 0)) - mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to 'EvWindow' ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Description changed: + https://gitlab.gnome.org/GNOME/evince/issues/1120 + + --- + Click in 'File options->Dual' my PDF. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1120 https://gitlab.gnome.org/GNOME/evince/issues/1120 ** Also affects: evince via https://gitlab.gnome.org/GNOME
[Desktop-packages] [Bug 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS, 18.10 and 19.04
Still a problem for Ubuntu MATE 19.04 beta2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1810745 Title: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS, 18.10 and 19.04 Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS with all updates 2. Install HPLIP into it with `sudo apt install hplip-gui` 3. Log out. Expected results: * HPLIP shows hp-systray icon and its fully functional Actual results: * HPLIP shows hp-systrat icon but it is non-functional (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mate-panel 1.20.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jan 7 12:15:48 2019 InstallationDate: Installed on 2019-01-07 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1810745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
Still a problem for Ubuntu MATE 19.04 beta2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in mate-themes package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822315] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1822313 *** https://bugs.launchpad.net/bugs/1822313 ** This bug has been marked a duplicate of bug 1822313 PCI/internal sound card not detected -- 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/1822315 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822314] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1822313 *** https://bugs.launchpad.net/bugs/1822313 ** This bug has been marked a duplicate of bug 1822313 PCI/internal sound card not detected -- 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/1822314 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 726439] Re: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed
Still exists in 19.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/726439 Title: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed Status in Yelp: Expired Status in yelp package in Ubuntu: Confirmed Bug description: Binary package hint: yelp TEST CASE: 1. Launch Yelp 2. Select the menu 'Go / All Documents" 2. Enter some text (e.g nautilus) in the address bar 3. Hit Enter Result: The following error is displayed: """ Unknown Error The URI ‘xref:search=nautilus’ could not be parsed. """ Expected Results: List of documents matching the search list is returned ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: yelp 2.91.90-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 Architecture: i386 Date: Mon Feb 28 11:01:37 2011 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: yelp To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/726439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822351] [NEW] Nautilus does not open after updating to 19.04
Public bug reported: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 Status in nautilus package in Ubuntu: New Bug description: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04
Update: Enabling and disabling the search and notification permissions on Settings->Applications->Nautilus solved the problem. I will leave the bug report open as I think there is still a bug involved (maybe related to tracker?). -- 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/1822351 Title: Nautilus does not open after updating to 19.04 Status in nautilus package in Ubuntu: New Bug description: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820899] Re: Neonode AirBar 13.3 inresponsive
I have just received my Airbar today and had the same problem, install the newer kernel from Bionic and it will work out of the box. I installed 4.18.0-16-generic and it works now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1820899 Title: Neonode AirBar 13.3 inresponsive Status in libinput: New Status in libinput package in Ubuntu: New Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: I am having problems with this device in recent versions of kernel (4.x), It is showing up on `dmesg`, but doesn't work under any Linux desktop (so far). It has worked before, and works flawlessly on the MS OS (no Hardware issues). Could someone help me to identify the correct list/bug-tracker to issue this report ? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: KDE neon 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:1946] InstallationDate: Installed on 2018-10-14 (156 days ago) InstallationMedia: neon user "Bionic" - Build amd64 LIVE Binary 20181011-05:55 Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 8087:07dc Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: libinput (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=c42cdf35-bf18-4bdb-93ff-e43f92d36a4e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L73 Ver. 01.11 dmi.board.name: 1946 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 89.14 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL73Ver.01.11:bd04/29/2014:svnHewlett-Packard:pn:pvrA3009CD1:rvnHewlett-Packard:rn1946:rvrKBCVersion89.14:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: A3009CD1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: KDE neon 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:1946] InstallationDate: Installed on 2018-10-14 (156 days ago) InstallationMedia: neon user "Bionic" - Build amd64 LIVE Binary 20181011-05:55 Package: libinput (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=c42cdf35-bf18-4bdb-93ff-e43f92d36a4e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L73 Ver. 01.11 dmi.board.name: 1946 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 89.14 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL73Ver.01.11:bd04/29/2014:svnHewlett-Packard:pn:pvrA3009CD1:rvnHewlett-Packard:rn1946:rvrKBCVersion89.14:cvnHewlett-Packard:ct10:cvr: dmi.pro
[Desktop-packages] [Bug 1820899] Re: Neonode AirBar 13.3 inresponsive
If you can confirm it is working, you can close this bug and your issue at libinput. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1820899 Title: Neonode AirBar 13.3 inresponsive Status in libinput: New Status in libinput package in Ubuntu: New Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: I am having problems with this device in recent versions of kernel (4.x), It is showing up on `dmesg`, but doesn't work under any Linux desktop (so far). It has worked before, and works flawlessly on the MS OS (no Hardware issues). Could someone help me to identify the correct list/bug-tracker to issue this report ? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: KDE neon 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:1946] InstallationDate: Installed on 2018-10-14 (156 days ago) InstallationMedia: neon user "Bionic" - Build amd64 LIVE Binary 20181011-05:55 Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 8087:07dc Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: libinput (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=c42cdf35-bf18-4bdb-93ff-e43f92d36a4e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L73 Ver. 01.11 dmi.board.name: 1946 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 89.14 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL73Ver.01.11:bd04/29/2014:svnHewlett-Packard:pn:pvrA3009CD1:rvnHewlett-Packard:rn1946:rvrKBCVersion89.14:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: A3009CD1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: KDE neon 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:1946] InstallationDate: Installed on 2018-10-14 (156 days ago) InstallationMedia: neon user "Bionic" - Build amd64 LIVE Binary 20181011-05:55 Package: libinput (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=c42cdf35-bf18-4bdb-93ff-e43f92d36a4e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L73 Ver. 01.11 dmi.board.name: 1946 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 89.14 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL73Ver.01.11:bd04/29/2014:svnHewlett-Packard:pn:pvrA3009CD1:rvnHewlett-Packard:rn1946:rvrKBCVersion89.14:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: A3009CD1 dmi.sys.vendor: Hewlett-Packard
[Desktop-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's
This bug was fixed in the package libdrm - 2.4.97-1ubuntu1 --- libdrm (2.4.97-1ubuntu1) disco; urgency=medium * sync-i915-pciids.diff: Sync pci-ids with the kernel. (LP: #1821863) -- Timo Aaltonen Fri, 29 Mar 2019 11:21:10 +0200 ** Changed in: libdrm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822350] Re: evince crashed with SIGABRT in g_assertion_message()
** Description changed: https://gitlab.gnome.org/GNOME/evince/issues/1120 --- - Click in 'File options->Dual' my PDF. + Click in 'File options->Dual' in my PDF. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1822350 Title: evince crashed with SIGABRT in g_assertion_message() Status in Evince: Unknown Status in evince package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evince/issues/1120 --- Click in 'File options->Dual' in my PDF. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1822350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 I never had this issue until the 19.04 update, I always used the NVIDIA proprietary driver. In Ubuntu 18.10 is working fine, so I suppose is some sort of regression... I'm curious to try this on another distribution. -- 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/1576859 Title: [nvidia] Graphics corruption when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Resuming from suspend results in graphical glitches. These glitches, at least on the cover screen(shows date/time) go away when the Hard Drive spins back up. Additional corruption can occur in overview on currently active applications(Such as Chromium). Description: Ubuntu 16.04 LTS Release: 16.04 gnome-shell: Installed: 3.18.4-0ubuntu3 Candidate: 3.18.4-0ubuntu3 Version table: *** 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 29 15:56:14 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-23 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822335] Re: test general
** Information type changed from Private Security to Public -- 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/1822335 Title: test general Status in xorg package in Ubuntu: New Bug description: test general. thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 29 15:34:45 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: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-03-09 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 2349IP5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=29ebe1d0-5356-4a16-ac13-b48aa7be1b2e ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349IP5 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET91WW(2.51):bd01/09/2013:svnLENOVO:pn2349IP5:pvrThinkPadT430:rvnLENOVO:rn2349IP5:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349IP5 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 22 09:18:08 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822356] [NEW] [Ubuntu 19.04] New open windows don't gain focus automatically
Public bug reported: After updating to Ubuntu 19.04 I noticed a papercut: new open windows don't have the focus. For example, if I opened the terminal from the dock in 18.10, I could start writing immediately after it open. In 19.04, I have to click on the terminal window before writing because the focus is elsewhere. It doesn't seem to happen always, but often enough to be annoying and certainly a regression from 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 15:04:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) ** Affects: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822356 Title: [Ubuntu 19.04] New open windows don't gain focus automatically Status in gnome-shell package in Ubuntu: New Bug description: After updating to Ubuntu 19.04 I noticed a papercut: new open windows don't have the focus. For example, if I opened the terminal from the dock in 18.10, I could start writing immediately after it open. In 19.04, I have to click on the terminal window before writing because the focus is elsewhere. It doesn't seem to happen always, but often enough to be annoying and certainly a regression from 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 15:04:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822350] Re: evince crashed with SIGABRT in g_assertion_message()
** Changed in: evince Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1822350 Title: evince crashed with SIGABRT in g_assertion_message() Status in Evince: New Status in evince package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evince/issues/1120 --- Click in 'File options->Dual' in my PDF. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1822350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822360] [NEW] Scan does not work with Lexmark OfficeEdge Pro 5500
Public bug reported: ~$ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 Printer portion works fine. Simple scane and XSANE do not detect scanner. Scanner worked in release 14.04 ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1822360 Title: Scan does not work with Lexmark OfficeEdge Pro 5500 Status in sane-backends package in Ubuntu: New Bug description: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 Printer portion works fine. Simple scane and XSANE do not detect scanner. Scanner worked in release 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1822360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822356] Re: [Ubuntu 19.04] New open windows don't gain focus automatically
*** This bug is a duplicate of bug 1817924 *** https://bugs.launchpad.net/bugs/1817924 ** This bug has been marked a duplicate of bug 1817924 apps launched from gnome shell do not get input focus -- 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/1822356 Title: [Ubuntu 19.04] New open windows don't gain focus automatically Status in gnome-shell package in Ubuntu: New Bug description: After updating to Ubuntu 19.04 I noticed a papercut: new open windows don't have the focus. For example, if I opened the terminal from the dock in 18.10, I could start writing immediately after it open. In 19.04, I have to click on the terminal window before writing because the focus is elsewhere. It doesn't seem to happen always, but often enough to be annoying and certainly a regression from 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 15:04:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822361] [NEW] nouveau driver seems doesn't work on nvidia GTX 1050 Ti noteook card
Public bug reported: Hello! Good afternoon! I believe this should be the second time I try to report this malfunction case that I believe may be related to the xserver-xorg- video-nouveau driver, running on nvidia GTX1050 video card laptops (as is my case notebook). Sorry if that's not the case! Anyway, I decided to report this bug and add some images I got when, after several failed attempts to login with my gnome user, with the frozen interface and the committed execution flow, I was lucky to get a successful Ctrl + Alt + F4 or Ctrl + Alt + F5 and got access to a text- mode session, which worked in the "leaps" but which allowed me at least after several minutes of patience to view this log, which I believe has some clue that may be happening. Sorry again, now for the bad quality of the photos, I had to take several of the same screen because of lighting problems and focus. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 15:26:40 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2019-01-30 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190119) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=11a759f5-c884-4c9a-87f0-22554753d054 ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ubuntu wayland-session ** Attachment added: "log screen photo" https://bugs.launchpad.net/bugs/1822361/+attachment/5250726/+files/screenshot1.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1822361 Title: nouveau driver seems doesn't work on nvidia GTX 1050 Ti noteook card Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Hello! Good afternoon! I believe this should be the second time I try to report this malfunction case that I believe may be related to the xserver-xorg- video-nouveau driver, running on nvidia GTX1050 video card laptops (as is my case notebook). Sorry if that's not the case! Anyway, I decided to report this bug and add some images I got when, after several failed attempts to login with my gnome user, with the frozen interface and the committed execution flow, I was lucky to get a successful Ctrl + Alt + F4 or Ctrl + Alt + F5 and got access to a text-mode session, which worked in the "leaps" but which allowed me at least after several minutes of patience to view this log, which I believe has some clue that may be happening. Sorry again, now for the bad quality of the photos, I had to take several of the same screen because of lighting problems and focus. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permissã
[Desktop-packages] [Bug 1822361] Re: nouveau driver seems doesn't work on nvidia GTX 1050 Ti noteook card
PS: I must clarify that at the moment I have already updated the video driver of my notebook for nvidia (I used "ubuntu-drivers" for it). But the problem in question always happens, from the first installation of ubuntu where, originally, the nouveau drive is installed. In this case I resolved to give a purge in the previous version of the nvidia driver that I had installed, to then redo the installation of the new version 418 ... after the purge I was forced to reboot the computer before reinstalling the nvidia driver. .. and had to go through the whole problem of trying to use the nouveau driver in this notebook. That's where I got the photos from the log screens. ** Attachment added: "screenshot2.jpg" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1822361/+attachment/5250743/+files/screenshot2.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1822361 Title: nouveau driver seems doesn't work on nvidia GTX 1050 Ti noteook card Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Hello! Good afternoon! I believe this should be the second time I try to report this malfunction case that I believe may be related to the xserver-xorg- video-nouveau driver, running on nvidia GTX1050 video card laptops (as is my case notebook). Sorry if that's not the case! Anyway, I decided to report this bug and add some images I got when, after several failed attempts to login with my gnome user, with the frozen interface and the committed execution flow, I was lucky to get a successful Ctrl + Alt + F4 or Ctrl + Alt + F5 and got access to a text-mode session, which worked in the "leaps" but which allowed me at least after several minutes of patience to view this log, which I believe has some clue that may be happening. Sorry again, now for the bad quality of the photos, I had to take several of the same screen because of lighting problems and focus. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 15:26:40 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2019-01-30 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190119) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=11a759f5-c884-4c9a-87f0-22554753d054 ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1822361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 294830] Re: latest pcscd causes crash of firefox
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcsc-lite (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: latest pcscd causes crash of firefox Status in pcsc-lite package in Ubuntu: Confirmed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Description changed: - * Impact - On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that Nautilus displays "Empty Folder" when clicking "Windows Network" + [Impact] + The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. + Accessing such machines directly, via smb:/// type urls, continues to work. - * Test case - Try to browse a smb share from a bionic client + The fix is two-fold: + - introduce a new samba API call that can be used to set the protocol version to use + - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing - * Regression potential - Check that smb browsing/mounts still work as they should + gvfs was updated to make use of this api call, if detected at build + time. To complete this SRU, gvfs needs a no-change rebuild *after* samba + was accepted into proposed. - --- + [Test case] + * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: + $ sudo apt update + $ sudo apt install ubuntu-desktop samba smbclient + + * set a password for the ubuntu user, so you can login at the graphical console + $ sudo passwd ubuntu + + * reboot + $ sudo reboot + + * login at the graphical console as the ubuntu user. Go through the + first-user-setup motions as you want. + + * try to browse the windows network via "other locations -> windows + network". You will get an empty folder. + + * update the samba and gvfs packages + * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM). + + [Regression potential] + The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. + Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. + + + [Other Info] + This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. + + To complete this SRU, gvfs will need a no-change rebuild after samba was + accepted into proposed. + Nautilus should show smbtree nad host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor) smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the processing engine) smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5708) smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo) smb-network: send_reply(0x55b19a2e7820), failed=0 () smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708) smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate) smb-network: send_reply(0x55b19a2c30c0), failed=0 () Proposed solution: Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394 which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe NT1 which most users are doing to correct this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Invalid Status in samba package in Ubuntu: In Progress Status in gvfs source package in Bionic: Triaged Status in gvfs source package in Cosmic: Triaged Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold:
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/365297 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Invalid Status in samba package in Ubuntu: In Progress Status in gvfs source package in Bionic: Triaged Status in gvfs source package in Cosmic: Triaged Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM). [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Nautilus should show smbtree nad host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor) smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the processing engine) smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5708) smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo) smb-network: send_reply(0x55b19a2e7820), failed=0 () smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708) smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate) smb-network: send_reply(0x55b19a2c30c0), failed=0 () Proposed solution: Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394 which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe NT1 which most users are doing to correct this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/365298 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Invalid Status in samba package in Ubuntu: In Progress Status in gvfs source package in Bionic: Triaged Status in gvfs source package in Cosmic: Triaged Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM). [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Nautilus should show smbtree nad host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor) smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the processing engine) smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5708) smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo) smb-network: send_reply(0x55b19a2e7820), failed=0 () smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708) smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate) smb-network: send_reply(0x55b19a2c30c0), failed=0 () Proposed solution: Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394 which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe NT1 which most users are doing to correct this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 294830] Re: latest pcscd causes crash of firefox
Had same problem, constant firefox crashes. Crashed thread had always same pattern: libOcsCryptoki.so -> libpcsclite.so.1.0.0 -> libc-2.29.so -> crash Managed to get rid of firefox crashes by replacing: pcscd 1.8.24-1 libpcsclite1 1.8.24-1 versions with debian: pcscd 1.8.25-1 https://packages.debian.org/sid/pcscd libpcsclite1 1.8.25-1 https://packages.debian.org/sid/libpcsclite1 I suggest updating ubuntu package versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: latest pcscd causes crash of firefox Status in pcsc-lite package in Ubuntu: Confirmed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
** Changed in: gnome-control-center Status: New => Fix Released -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: Fix Released Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822373] [NEW] [Disco] crash when resuming from sleep
Public bug reported: Randomly and often GNOME-Shell crashes when resuming from sleep. Upstream bug report : https://gitlab.gnome.org/GNOME/mutter/issues/509 The fix already exists : https://gitlab.gnome.org/jadahl/mutter/commit/5174b9e105a78730f2f09be920bf56e3ef0c3776 ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: disco ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #509 https://gitlab.gnome.org/GNOME/mutter/issues/509 ** Also affects: fmutter via https://gitlab.gnome.org/GNOME/mutter/issues/509 Importance: Unknown Status: Unknown ** Project changed: fmutter => mutter -- 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/1822373 Title: [Disco] crash when resuming from sleep Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: Randomly and often GNOME-Shell crashes when resuming from sleep. Upstream bug report : https://gitlab.gnome.org/GNOME/mutter/issues/509 The fix already exists : https://gitlab.gnome.org/jadahl/mutter/commit/5174b9e105a78730f2f09be920bf56e3ef0c3776 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1822373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Is there a way to test this patch with the 418 driver? I have an RTX 2070, which is not supported by the 390 driver, but I'd really like my battery life back. When I try to follow the instructions from the report, but replacing 390 with 418, it doesn't work (predictably). $ sudo apt install nvidia-driver-418/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-418/bionic- proposed libnvidia-compute-418/bionic-proposed libnvidia-decode-418 /bionic-proposed libnvidia-encode-418/bionic-proposed libnvidia-ifr1-418 /bionic-proposed libnvidia-fbc1-418/bionic-proposed Reading package lists... Done Building dependency tree Reading state information... Done E: Release 'bionic-proposed' for 'nvidia-driver-418' was not found E: Release 'bionic-proposed' for 'nvidia-prime' was not found E: Release 'bionic-proposed' for 'nvidia-settings' was not found E: Release 'bionic-proposed' for 'libnvidia-gl-418' was not found E: Release 'bionic-proposed' for 'libnvidia-compute-418' was not found E: Release 'bionic-proposed' for 'libnvidia-decode-418' was not found E: Release 'bionic-proposed' for 'libnvidia-encode-418' was not found E: Release 'bionic-proposed' for 'libnvidia-ifr1-418' was not found E: Release 'bionic-proposed' for 'libnvidia-fbc1-418' was not found It may be worth noting that nvidia-prime and nvidia-settings are also not found, even though their names don't include the driver version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bion
[Desktop-packages] [Bug 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1
Just tried 3.19.3 - same issue as before HP Linux Imaging and Printing System (ver. 3.19.3) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.19.3) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Plugin is not accessible. Trying to download it from fallback location: [https://developers.hp.com/sites/default/files/hplip-3.19.3-plugin.run] Receiving digital keys: /usr/bin/gpg --homedir /home/fen/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9 Creating directory plugin_tmp Verifying archive integrity... All good. Uncompressing HPLIP 3.19.3 Plugin Self Extracting Archive.. HP Linux Imaging and Printing System (ver. 3.19.3) Plugin Installer ver. 3.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Plug-in version: 3.19.3 Installed HPLIP version: 3.19.3 Number of files to install: 64 Plugin installation failed error: Python gobject/dbus may be not installed error: Plug-in install failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1812582 Title: Unable to install hplip 3.18.12 on linux mint 19.1 Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: RESTART OR RE-PLUG IS REQUIRED -- If you are installing a USB connected printer, and the printer was plugged in when you started this installer, you will need to either restart your PC or unplug and re-plug in your printer (USB cable only). If you choose to restart, run this command after restarting: hp-setup (Note: If you are using a parallel connection, you will have to restart your PC. If you are using network/wireless, you can ignore and continue). Restart or re-plug in your printer (r=restart, p=re-plug in*, i=ignore/continue, q=quit) : i PRINTER SETUP - Please make sure your printer is connected and powered on at this time. Do you want to setup printer in GUI mode? (u=GUI mode*, i=Interactive mode) : u HP Linux Imaging and Printing System (ver. 3.18.12) Printer/Fax Setup Utility ver. 9.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Searching... (bus=net, timeout=5, ttl=4, search=(None) desc=0, method=slp) Segmentation fault error: The device you are trying to setup requires a binary plug-in. Some functionalities may not work as expected without plug-ins. Please run 'hp-plugin' as normal user to install plug-ins. Visit http://hplipopensource.com for more infomation. Segmentation fault error: The device you are trying to setup requires a binary plug-in. Some functionalities may not work as expected without plug-ins. Please run 'hp-plugin' as normal user to install plug-ins. Visit http://hplipopensource.com for more infomation. Done. RE-STARTING HP_SYSTRAY -- HP Linux Imaging and Printing System (ver. 3.18.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) :~/Downloads$ hp-plugin HP Linux Imaging and Printing System (ver. 3.18.12) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.18.12) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free so
[Desktop-packages] [Bug 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1
Note that's with Mint 19.1 which 3.19.3 is supposed to supoprt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1812582 Title: Unable to install hplip 3.18.12 on linux mint 19.1 Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: RESTART OR RE-PLUG IS REQUIRED -- If you are installing a USB connected printer, and the printer was plugged in when you started this installer, you will need to either restart your PC or unplug and re-plug in your printer (USB cable only). If you choose to restart, run this command after restarting: hp-setup (Note: If you are using a parallel connection, you will have to restart your PC. If you are using network/wireless, you can ignore and continue). Restart or re-plug in your printer (r=restart, p=re-plug in*, i=ignore/continue, q=quit) : i PRINTER SETUP - Please make sure your printer is connected and powered on at this time. Do you want to setup printer in GUI mode? (u=GUI mode*, i=Interactive mode) : u HP Linux Imaging and Printing System (ver. 3.18.12) Printer/Fax Setup Utility ver. 9.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Searching... (bus=net, timeout=5, ttl=4, search=(None) desc=0, method=slp) Segmentation fault error: The device you are trying to setup requires a binary plug-in. Some functionalities may not work as expected without plug-ins. Please run 'hp-plugin' as normal user to install plug-ins. Visit http://hplipopensource.com for more infomation. Segmentation fault error: The device you are trying to setup requires a binary plug-in. Some functionalities may not work as expected without plug-ins. Please run 'hp-plugin' as normal user to install plug-ins. Visit http://hplipopensource.com for more infomation. Done. RE-STARTING HP_SYSTRAY -- HP Linux Imaging and Printing System (ver. 3.18.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) :~/Downloads$ hp-plugin HP Linux Imaging and Printing System (ver. 3.18.12) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.18.12) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Receiving digital keys: /usr/bin/gpg --homedir //.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9 Creating directory plugin_tmp Verifying archive integrity... All good. Uncompressing HPLIP 3.18.12 Plugin Self Extracting Archive. HP Linux Imaging and Printing System (ver. 3.18.12) Plugin Installer ver. 3.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Plug-in version: 3.18.12 Installed HPLIP version: 3.18.12 Number of files to install: 55 Plugin installation failed error: Python gobject/dbus may be not installed error: Plug-in install failed. Done. From kernel log hplip/plugin.py" name="/etc/xdg/Trolltech.conf" pid=4238 comm="python" requested_mask="k" denied_mask="k" fsuid=1000 ouid=0 [ 9015.754212] audit: type=1400 audit(1548011993.816:100): apparmor="DENIED" operation="file_lock" profile="/usr/share/hplip/plugin.py" name="/run/sudo/ts/" pid=4240 comm="sudo" requested_mask="k" denied_mask="k" fsuid=0 ouid=0 [ 9015.862631] audit: type=1400 audit(1548011993.924:101): apparmor="DENIED" operation="file_lock" profile="/usr/share/hplip/plugin.py" name="/run/utmp" pid=4240 comm="sudo" requested_mask="k" denied_mask="k" fsuid=0 ouid=0 [
[Desktop-packages] [Bug 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1
HP check log So as before I had to install the plugin manually and that's when the error occurred ** Attachment added: "hpcheck.log" https://bugs.launchpad.net/hplip/+bug/1812582/+attachment/5250804/+files/hpcheck.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1812582 Title: Unable to install hplip 3.18.12 on linux mint 19.1 Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: RESTART OR RE-PLUG IS REQUIRED -- If you are installing a USB connected printer, and the printer was plugged in when you started this installer, you will need to either restart your PC or unplug and re-plug in your printer (USB cable only). If you choose to restart, run this command after restarting: hp-setup (Note: If you are using a parallel connection, you will have to restart your PC. If you are using network/wireless, you can ignore and continue). Restart or re-plug in your printer (r=restart, p=re-plug in*, i=ignore/continue, q=quit) : i PRINTER SETUP - Please make sure your printer is connected and powered on at this time. Do you want to setup printer in GUI mode? (u=GUI mode*, i=Interactive mode) : u HP Linux Imaging and Printing System (ver. 3.18.12) Printer/Fax Setup Utility ver. 9.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Searching... (bus=net, timeout=5, ttl=4, search=(None) desc=0, method=slp) Segmentation fault error: The device you are trying to setup requires a binary plug-in. Some functionalities may not work as expected without plug-ins. Please run 'hp-plugin' as normal user to install plug-ins. Visit http://hplipopensource.com for more infomation. Segmentation fault error: The device you are trying to setup requires a binary plug-in. Some functionalities may not work as expected without plug-ins. Please run 'hp-plugin' as normal user to install plug-ins. Visit http://hplipopensource.com for more infomation. Done. RE-STARTING HP_SYSTRAY -- HP Linux Imaging and Printing System (ver. 3.18.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) :~/Downloads$ hp-plugin HP Linux Imaging and Printing System (ver. 3.18.12) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.18.12) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Receiving digital keys: /usr/bin/gpg --homedir //.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9 Creating directory plugin_tmp Verifying archive integrity... All good. Uncompressing HPLIP 3.18.12 Plugin Self Extracting Archive. HP Linux Imaging and Printing System (ver. 3.18.12) Plugin Installer ver. 3.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Plug-in version: 3.18.12 Installed HPLIP version: 3.18.12 Number of files to install: 55 Plugin installation failed error: Python gobject/dbus may be not installed error: Plug-in install failed. Done. From kernel log hplip/plugin.py" name="/etc/xdg/Trolltech.conf" pid=4238 comm="python" requested_mask="k" denied_mask="k" fsuid=1000 ouid=0 [ 9015.754212] audit: type=1400 audit(1548011993.816:100): apparmor="DENIED" operation="file_lock" profile="/usr/share/hplip/plugin.py" name="/run/sudo/ts/" pid=4240 comm="sudo" requested_mask="k" denied_mask="k" fsuid=0 ouid=0 [ 9015.862631] audit: type=1400 audit(1548011993.924:101): apparmor=
[Desktop-packages] [Bug 1822383] [NEW] [19.04 beta] Can't add language
Public bug reported: Cannot add language in the list. The windows only allows to select language from the list of installed languages. Workaround: launch language-selector and add language. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 14:27:36 2019 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (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-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1822383 Title: [19.04 beta] Can't add language Status in gnome-settings-daemon package in Ubuntu: New Bug description: Cannot add language in the list. The windows only allows to select language from the list of installed languages. Workaround: launch language-selector and add language. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 14:27:36 2019 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1822383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode
hello, I hope this one gets fixed in 19.04. Also, I forgot to mention that the live installers aren't affected only the installed versions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1804568 Title: click position is flipped to cursor position when in tent mode Status in x11-xserver-utils package in Ubuntu: New Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1804568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 294830] Re: latest pcscd causes crash of firefox
... [New Thread 0x7fffe18ff700 (LWP 5650)] *** buffer overflow detected ***: /usr/lib/firefox/firefox terminated Thread 411 "SSL Cert #32" received signal SIGABRT, Aborted. [Switching to Thread 0x7fffd35be700 (LWP 5576)] 0x779d2fb7 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) backtrace #0 0x779d2fb7 in raise () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x779b4535 in abort () at /lib/x86_64-linux-gnu/libc.so.6 #2 0x77a1b7b6 in () at /lib/x86_64-linux-gnu/libc.so.6 #3 0x77abe76f in () at /lib/x86_64-linux-gnu/libc.so.6 #4 0x77abe791 in () at /lib/x86_64-linux-gnu/libc.so.6 #5 0x77abd0c0 in () at /lib/x86_64-linux-gnu/libc.so.6 #6 0x77abe677 in () at /lib/x86_64-linux-gnu/libc.so.6 #7 0x7fffe2e3cb06 in () at /usr/lib/x86_64-linux-gnu/libpcsclite.so.1 #8 0x7fffe2e3cc56 in () at /usr/lib/x86_64-linux-gnu/libpcsclite.so.1 #9 0x7fffe2e3a405 in SCardEstablishContext () at /usr/lib/x86_64-linux-gnu/libpcsclite.so.1 #10 0x7fffdea43729 in CPCSCDeviceManager::getDevices() () at /usr/local/AWP/lib/libOcsCryptoki.so #11 0x7fffdea24bde in CVirtualSlotManager::getSlots(bool, int&, unsigned long*) () at /usr/local/AWP/lib/libOcsCryptoki.so #12 0x7fffdea154b2 in CCryptoki::getSlotList(unsigned char, unsigned long*, unsigned long*) () at /usr/local/AWP/lib/libOcsCryptoki.so #13 0x7fffdea23570 in C_GetSlotList () at /usr/local/AWP/lib/libOcsCryptoki.so #14 0x7fffdeefcf05 in C_GetSlotList () at /usr/local/AWP/lib/libOcsPKCS11Wrapper.so #15 0x7756913c in SECMOD_UpdateSlotList () at /usr/lib/firefox/libnss3.so #16 0x7154ab5b in () at /usr/lib/firefox/libxul.so #17 0x7fffee39c9c0 in () at /usr/lib/firefox/libxul.so #18 0x7fffee39e3f9 in () at /usr/lib/firefox/libxul.so #19 0x7152cd7d in () at /usr/lib/firefox/libxul.so #20 0x7152ed9c in () at /usr/lib/firefox/libxul.so #21 0x7fffee43a07f in () at /usr/lib/firefox/libxul.so #22 0x7fffee438a7e in () at /usr/lib/firefox/libxul.so #23 0x7fffee43acc8 in () at /usr/lib/firefox/libxul.so #24 0x7fffee89daaa in () at /usr/lib/firefox/libxul.so #25 0x7fffee872205 in () at /usr/lib/firefox/libxul.so #26 0x7fffee43af71 in () at /usr/lib/firefox/libxul.so #27 0x775eb984 in () at /usr/lib/firefox/libnspr4.so #28 0x77d84182 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #29 0x77aacfaf in clone () at /lib/x86_64-linux-gnu/libc.so.6 (gdb) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: latest pcscd causes crash of firefox Status in pcsc-lite package in Ubuntu: Confirmed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1689582] Re: Mouse pointer shows trail
Bug seems not to be reproduced in Ubuntu 18.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1689582 Title: Mouse pointer shows trail Status in xorg package in Ubuntu: Won't Fix Bug description: This bug occurs in my case in Ubuntu Gnome 16.10 and 17.04 with Xorg. No artifacts in 16.04.2. Using Intel i915 driver and Intel J3710 processor (ASRock J3710-ITX). Dual monitor setting. Phenomenon occurs after executing programs with high memory usage. I was not able to reproduce it with Gnome Wayland. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue May 9 17:31:19 2017 DistUpgraded: 2017-04-21 23:26:05,151 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Uitvoeren van dochterproces ‘./xorg_fix_proprietary.py’ is mislukt (No such file or directory) (8)) DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1] InstallationDate: Installed on 2017-04-21 (17 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=43d43e4c-38c7-4c32-bcfe-d89ab33ccf3f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-04-21 (17 days ago) dmi.bios.date: 03/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: J3710-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd03/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnJ3710-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1689582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822373] Re: [Disco] crash when resuming from sleep
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1822373 Title: [Disco] crash when resuming from sleep Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: Randomly and often GNOME-Shell crashes when resuming from sleep. Upstream bug report : https://gitlab.gnome.org/GNOME/mutter/issues/509 The fix already exists : https://gitlab.gnome.org/jadahl/mutter/commit/5174b9e105a78730f2f09be920bf56e3ef0c3776 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1822373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822392] [NEW] gsd-media-keys fails to adjust the screen brightness after unlocking
Public bug reported: Whne my machine sat for some time (laptop, screen off) it is not possible to change the screen brighness of the display for some time after unlocking. After 3-5 minutes it will eventually just work again. journalctl logs the following är 30 01:17:02 dbus-daemon[975]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.212' (uid=1000 pid=14229 comm="/usr/bin/gnome-shell " label="uncon Mär 30 01:17:02 systemd[1]: Starting Fingerprint Authentication Daemon... Mär 30 01:17:02 dbus-daemon[975]: [system] Successfully activated service 'net.reactivated.Fprint' Mär 30 01:17:02 systemd[1]: Started Fingerprint Authentication Daemon. Mär 30 01:17:06 gdm-password][605]: gkr-pam: unlocked login keyring Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.137' (uid=1000 pid=808 comm="/usr/ Mär 30 01:17:45 systemd[14145]: Starting GNOME Terminal Server... Mär 30 01:17:45 gnome-terminal-server[813]: Display does not support owner-change; copy/paste will be broken! Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Successfully activated service 'org.gnome.Terminal' Mär 30 01:17:45 systemd[14145]: Started GNOME Terminal Server. Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/interface/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/sound/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage: Timeout was reached Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage: Timeout was reached Mär 30 01:17:55 pkexec[845]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[845]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93] Mär 30 01:17:55 pkexec[851]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[851]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 139] Mär 30 01:17:55 pkexec[857]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:17:55 pkexec[857]: doommaster: Executing command [USER=root] [TTY=unknown] [CWD=/home/doommaster] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 185] Mär 30 01:17:55 pkexec[863]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mär 30 01:1
[Desktop-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode
hi, I've just installed and fully upgraded fcb7652dbabbbebe207f6d1c92eda29a http://cdimage.ubuntu.com/daily-live/current/disco-desktop-amd64.iso and I can confirm that this bug is still present on this version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1804568 Title: click position is flipped to cursor position when in tent mode Status in x11-xserver-utils package in Ubuntu: New Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1804568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822394] [NEW] laptop keyboard & touchpad not working at gdm screen after boot
Public bug reported: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session ** Description changed: - On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and - keyboard are unresponsive at the gdm login screen. Keyboard works to - unlock encrypted harddrive before that though. If I plug in a USB - keyboard or activate my bluetooth mouse, I can use those to log in, and - then after logging in the laptop touchpad and keyboard work again. + On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results + in the laptop touchpad and keyboard working on the gdm screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) ** Description changed: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results - in the laptop touchpad and keyboard working on the gdm screen. + in the laptop touchpad and keyboard working on the gdm screen. Did not see + this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had + not rebooted in a while, so not sure if bios or package upgrades triggered + this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) -- 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/1822394 Title: laptop keyboard & touchpad not working at gdm screen after boot Status in gdm3 package in Ubuntu: New Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10
[Desktop-packages] [Bug 1822402] [NEW] gnome calendar automatically moves event back 1 day
Public bug reported: Step to reproduce: 1. Create an all day event 2. Set it to repeat monthly --> Surprise, it goes back one day Additional information: Time belt: GMT+7 ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1822402 Title: gnome calendar automatically moves event back 1 day Status in gnome-calendar package in Ubuntu: New Bug description: Step to reproduce: 1. Create an all day event 2. Set it to repeat monthly --> Surprise, it goes back one day Additional information: Time belt: GMT+7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1822402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
So, there is a need to rebuild xrdp against HWE 18.04. Maybe Ubuntu should provide a new binary package, let's say "xrdp- hwe-18.04" For now, I've recompiled the same xrdp from Ubuntu 18.04, on Ubuntu 18.04.2 and uploaded to my "XRP PPA", here: https://launchpad.net/~martinx/+archive/ubuntu/xrdp-hwe-18.04 To enjoy xrdp on Ubuntu 18.04 with HWE, just do: sudo add-apt-repository ppa:martinx/xrdp-hwe-18.04 sudo apt install xrdp xorgxrdp ;-) -- 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in xrdp package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
And here is the xrdp-0.9.9 and xorgxrdp-0.2.9 for Bionic HWE! https://launchpad.net/~martinx/+archive/ubuntu/xrdp-next Awesome Friday night! LOL -- 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in xrdp package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813443] Re: 3min boot delay due to 'discreteGpuAvailable' in code
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1813443 Title: 3min boot delay due to 'discreteGpuAvailable' in code Status in gnome-shell package in Ubuntu: Expired Bug description: From up to date Ubuntu 18.04.1 LTS syslog: Jan 26 21:35:45 RyzenSon deja-dup-monito[2221]: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported Note time signature for next item is 3+ mins later Jan 26 21:38:59 RyzenSon gnome-shell[1313]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Jan 26 21:38:59 RyzenSon gnome-shell[1313]: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Note time signature for next item is 3+ mins later Jan 26 21:39:58 RyzenSon dbus-daemon[1185]: [session uid=1000 pid=1185] Activating service name='org.gnome.Nautilus' requested by ':1.21' (uid=1000 pid=1313 comm="/usr/bin/gnome-shell " label="unconfined") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813431] Re: Problem with gnome panel system menu
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1813431 Title: Problem with gnome panel system menu Status in gnome-shell package in Ubuntu: Expired Bug description: When I clicked on the start menu in the top right corner, that little window jumped out, and. when I wanted to lock my account, nothing happened, but when I clicked on that panel again, it was like... vibrating... It was moving up and down about 10px (If I remember well). When I left it be and came back later (I have automatic lock after 5 min) There was that menu on the left (I don't know the name :D) After I logged in, I noticed, that when I move my mouse on it, it becomes wider and icons go slightly further apart(When I'm on desktop). When I have Firefox window opened, same happens, but when I aim on Firefox icon, the icons go to normal distance, but bar is still wider. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 23:29:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:805d] InstallationDate: Installed on 2019-01-11 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:760a Microdia Bus 001 Device 002: ID 0458:0188 KYE Systems Corp. (Mouse Systems) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProDesk 600 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=4d46de66-f485-47e9-905c-9d172082c94d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: HP dmi.bios.version: N02 Ver. 02.16 dmi.board.name: 805D dmi.board.vendor: HP dmi.board.version: KBC Version 05.22 dmi.chassis.asset.tag: CZC6448GH4 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN02Ver.02.16:bd08/18/2016:svnHP:pnHPProDesk600G2SFF:pvr:rvnHP:rn805D:rvrKBCVersion05.22:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP ProDesk 600 G2 SFF dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813020] Re: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] There is no voice in headphone
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1813020 Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] There is no voice in headphone Status in alsa-driver package in Ubuntu: Expired Bug description: Suddenly my headphone stopped working. It is being detected when I plugged in. But there is no voice in headphone. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 23 19:15:32 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-07-29 (177 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 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/controlC0: parag 1944 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-01-22T23:58:18.387600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813020/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1457438] Re: files not shown when known to exist
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1457438 Title: files not shown when known to exist Status in nautilus package in Ubuntu: Expired Bug description: When using dia I saved some .png images, as I had done before with the same names. Going to nautilus in order to select those images, I find that they are not listed, yet the dia save dialogue does show them. Reloading did not find them. See attached screenshot, which shows both the nautilus window after a reload and the dia dialogue. Later, opening a new nautilus window did find the files. So, why did they not show when I first looked? I have observed this problem before but did not keep records. This time I thought it worthwhile. Files are: timetrial_duties2.png regatta_duties2.png I'm using a fully up-to-date 14.04 on an AMD 64 motherboard and Dia- gnome 0.97.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1457438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
