[Desktop-packages] [Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04
I have billions of Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: Error executing command as another user: Not authorized Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: This incident has been reported. Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: Error executing command as another user: Not authorized Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: This incident has been reported. Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: Error executing command as another user: Not authorized Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: This incident has been reported. Feb 21 08:39:19 LIFEBOOK org.gnome.SettingsDaemon.Power.desktop[2627]: Error executing command as another user: Not authorized in the syslog as well. I get these when i try to change brightness using the bar in the top right. Using Fn + F7 works well. If i try to change brightness using terminal command "pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 0", I get the same result as above. But changing pkexec to sudo fixes the problem. ** Attachment added: "apt-cache.txt" https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+attachment/5240528/+files/apt-cache.txt -- 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/1584457 Title: gsd-backlight-helper spamming the logs since upate to 16.04 Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Xenial: Confirmed Bug description: Since updating to 16.04 from 14.04, I have the syslog spammed by: SEC: May 22 13:26:43 samsung-romano pkexec[21248]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 1766] SEC: May 22 13:26:43 samsung-romano pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1153) SEC: May 22 13:26:43 samsung-romano pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session SEC: May 22 13:26:43 samsung-romano pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device SEC: May 22 13:26:43 samsung-romano pkexec[21249]: romano: Executing command [USER=root] [TTY=unknown] [CWD=/home/romano] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 4322] SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: Error executing command as another user: Not authorized SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: This incident has been reported. every couple of seconds or so. There is no really need to change brightness... how can I stop it? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
Are you using any gnome-shell extensions? If so then please try uninstalling all of them, and reboot. -- 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/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816896] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1816896/+attachment/5240526/+files/ProcEnviron.txt -- 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/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816896] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1816896/+attachment/5240527/+files/modified.conffile..etc.gdm3.custom.conf.txt -- 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/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816896] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1816896/+attachment/5240525/+files/ProcCpuinfoMinimal.txt -- 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/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
apport information ** Tags added: apport-collected ** Description changed: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. - If an extra monitor was plugged in while the laptop was turned off - (scenario: come home, put laptop in docking station with extra monitor - attached, turn on) then often the UI will still fail to respond after - switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot - the laptop. + If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-08-13 (191 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Package: gnome-shell + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 + Tags: cosmic + Uname: Linux 4.18.0-15-generic x86_64 + UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1816896/+attachment/5240524/+files/Dependencies.txt -- 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/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
Hello. Does this patch is included in Software -> Additional Drivers page and will be installed along proposed driver ? I mean on my HP 8440p with Nvidia's NVS3100M (GT218M) suggested driver is 340.107 (proprietary, tested) . Last time I tried tu upgrade from Nouveau to Nvidia drivers got stuck with black screen and broken packages. -- 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/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
[Desktop-packages] [Bug 1816271] Re: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19
** Tags removed: regression-update -- 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/1816271 Title: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19 Status in pulseaudio package in Ubuntu: Invalid Bug description: 19.04,kern 4.19.0-13 just took update and now does not recognize soundcard or something plugged in to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it wakes up and recognizes it and works fine. I thought I had this prob a few days ago and restored back to the 10th, and updated all but alsa and worked fine. This morning I checked and a bunch of alsa stuff was no longer showing in updates, took everything, and worked fine. Just took updates (Software Updater), and checked speakers and no go. When this happened, it also would not allow sound to HDTV via HDMI, no matter what. Just tested and was able to get sound via hdmi, but remember, I have already "woken it up" by unplugging and plugging headphones (actually sony vaio computer speakers) ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast! I expected sound to recognize soundcard/speakers. It did not until I unplug/replug headphones. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 19:20:26 2019 InstallationDate: Installed on 2019-02-09 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gst-plugins-good1.0 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kris 1512 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-09 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Tags: disco Uname: Linux 4.19.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETB4WW (2.74 ) dmi.board.asset.tag: Not Available dmi.board.name: 23943J8 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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T530 dmi.product.name: 23943J8 dmi.product.sku: LENOVO_MT_2394 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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.
** Changed in: gdm3 (Ubuntu) Status: Expired => New ** Changed in: gnome-shell (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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 gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New 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/gdm3/+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://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.
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (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/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 gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired 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/gdm3/+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://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.
[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/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 gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired 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/gdm3/+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://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816945] Re: failsafeXServer does not parse Xorg.failsafe.log correctly
The attachment "Patch to failsafeXServer" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1816945 Title: failsafeXServer does not parse Xorg.failsafe.log correctly Status in xdiagnose package in Ubuntu: New Bug description: The timestamp for Xorg.failsafe.log has changed, and is no longer parsed correctly by failsafeXServer Here is a sample error message from syslog 2019-02-15T12:30:36.028591-08:00 awabi failsafeXServer[7805]: expr: non-integer argument 2019-02-15T12:30:36.028735-08:00 awabi failsafeXServer[7805]: /usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected Currently, Xorg.failsafe.log looks like: [ 477.714] (II) Server terminated successfully (0). Closing log file. but failsafeXServer assumes that the date is seconds since 1970-01-01 00:00:00 UTC I have attached a patch which provides a solution to the problem. I look at the timestamp of the file, using %s, which provides seconds since 1970-01-01 00:00:00 UTC ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xdiagnose 3.8.8 [modified: usr/share/xdiagnose/failsafeXServer] ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Feb 20 18:17:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-18 (1374 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: xdiagnose UpgradeStatus: Upgraded to cosmic on 2018-11-01 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1816945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740180]
Mozilla/5.0 (Windows NT 6.1; rv:67.0) Gecko/20100101 Firefox/67.0 (20190219094627) Reproducible using the latest Nightly build on Windows 7 x84 with the following error in the browser console "SecurityError: Permission denied to get property "href" on cross-origin object" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1740180 Title: Firefox stops loading Farmville 2 and hangs. Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. Farmville 2 hangs while loading. Never plays. The Adobe Flash Player is properly installed. Has also been re- installed. Ditto for FireFox. Does not matter if using Ubuntu 16.04 or 17.10. Farmville 2 via Facebook in Firefox hangs. Also will not work if run from the Zynga URL (the makers of Farmville 2. Other Facebook games work well. Try "Pearl's Perils." Happy to help with testing if you like. This has been tested on both desktops and laptops. Thanks, Ken Wagner ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Dec 26 15:59:05 2017 InstallationDate: Installed on 2017-03-06 (295 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ken2466 F pulseaudio /dev/snd/pcmC0D0p: ken2466 F...m pulseaudio /dev/snd/controlC0: ken2466 F pulseaudio /dev/snd/controlC2: ken2466 F pulseaudio BuildID: 20180614184508 Channel: beta CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-03-28 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.0.1 dev enp2s0 proto static metric 100 default via 192.168.1.1 dev wlx7cdd908b43ea proto static metric 600 169.254.0.0/16 dev wlx7cdd908b43ea scope link metric 1000 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx7cdd908b43ea proto kernel scope link src 192.168.1.2 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: LP-PPA-mozillateam-firefox-next] PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use) RunningIncompatibleAddons: False SubmittedCrashIDs: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 bp-481cf9ec-efcd-4900-93aa-4e8940180512 bp-ad49167e-7776-4ff5-8acc-5adb50180421 bp-08f026d0-e273-45fb-b355-c70ae0180402 Tags: xenial third-party-packages beta-channel Themes: extensions.sqlite corrupt or missing Uname: Linux 4.13.0-45-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/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M.
[Desktop-packages] [Bug 1816947] Re: Touchpad not working after last apt-get upgrade
Could you please: 1. Attach a copy of your /var/log/apt/history.log 2. Tell us the date of the upgrade when you think the problem started. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Summary changed: - Touchpad not working after last apt-get upgrade + [Dell XPS L321X] Touchpad not working after last apt-get upgrade -- 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/1816947 Title: [Dell XPS L321X] Touchpad not working after last apt-get upgrade Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: already filed at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046 check: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input- synaptics/+bug/1096046/comments/33 affects: xserver-xorg-input-synaptics (Ubuntu) The bug is marked expired an low priority, but it really prevents me from using ubuntu or any other distro based on it on my machine. Please reopen it! the bug has been successfully reproduced on my machine using the latest daily build --- $ lspci -v 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller Flags: bus master, fast devsel, latency 0 Capabilities: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 2000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Dell 6 Series/C200 Series Chipset Family MEI Controller Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f0605000 (64-bit, non-prefetchable) [size=16] Capabilities: Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI]) Subsystem: Dell 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f060a000 (32-bit, non-prefetchable) [size=1K] Capabilities: Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Dell 6 Series/C200 Series Chipset Family High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at f060 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) (prog-if 00 [Normal decode]) Flags: fast devsel, IRQ 16 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Capabilities: Kernel driver in use: pcieport 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 17 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Memory behind bridge: f050-f05f Capabilities: Kernel driver in use: pcieport 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 19 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: f040-f04f Capabilities: Kernel driver in use: pcieport 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI]) Subsystem: Dell 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at f0609000 (32-bit,
[Desktop-packages] [Bug 1816271] Re: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19
I don't completely follow, but if you are happy then yes we can close this. Feel free to reopen it (change the status) if you feel something is still wrong. ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/1816271 Title: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19 Status in pulseaudio package in Ubuntu: Invalid Bug description: 19.04,kern 4.19.0-13 just took update and now does not recognize soundcard or something plugged in to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it wakes up and recognizes it and works fine. I thought I had this prob a few days ago and restored back to the 10th, and updated all but alsa and worked fine. This morning I checked and a bunch of alsa stuff was no longer showing in updates, took everything, and worked fine. Just took updates (Software Updater), and checked speakers and no go. When this happened, it also would not allow sound to HDTV via HDMI, no matter what. Just tested and was able to get sound via hdmi, but remember, I have already "woken it up" by unplugging and plugging headphones (actually sony vaio computer speakers) ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast! I expected sound to recognize soundcard/speakers. It did not until I unplug/replug headphones. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 19:20:26 2019 InstallationDate: Installed on 2019-02-09 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gst-plugins-good1.0 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kris 1512 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-09 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Tags: disco Uname: Linux 4.19.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETB4WW (2.74 ) dmi.board.asset.tag: Not Available dmi.board.name: 23943J8 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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T530 dmi.product.name: 23943J8 dmi.product.sku: LENOVO_MT_2394 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1096046] Re: Touchpad not working after last apt-get upgrade
OTH, the workaround from http://askubuntu.com/a/262364/175109 seems to work, but I can't enable two-finger-scroll nor touch-to-click. in fact, after running ubuntu@ubuntu:~$ sudo modprobe -r psmouse ubuntu@ubuntu:~$ sudo modprobe psmouse proto=imps The touchpad works but id doesn't even appear in settings -> devices -> Mouse & Touchpad, just like if there was no touchpad at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1096046 Title: Touchpad not working after last apt-get upgrade Status in xserver-xorg-input-synaptics package in Ubuntu: Expired Bug description: After last apt-get upgrade, touchpad no longer works. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Fri Jan 4 13:47:13 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP Folio 13 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-35-generic root=UUID=c2fa7f5e-0ada-4f3a-a39f-b8903ca5119d ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17F8 dmi.board.vendor: Hewlett-Packard dmi.board.version: 46.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.05:bd12/21/2011:svnHewlett-Packard:pnHPFolio13NotebookPC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Folio 13 Notebook PC dmi.product.version: 068C10204A0320100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046/+subscriptions -- Mailing list: https://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 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Personally, I have not encountered that when using ubuntu or fedora and simply swapping gdm3 for lightdm but it's good that the other bug report has a fix. It looks like a hidpi bug; none of my monitors are hidpi. On Thu, 21 Feb 2019 at 12:50, Stefano <1716...@bugs.launchpad.net> wrote: > The problem with the lightdm workaround is that many had this cursor > issue: > > https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1770948 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > gdm3, hybrid nvidia with modeset=1, no external monitors detected > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1096046] Re: Touchpad not working after last apt-get upgrade
Just filed a new issue, with all the info attached, to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1816947 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1096046 Title: Touchpad not working after last apt-get upgrade Status in xserver-xorg-input-synaptics package in Ubuntu: Expired Bug description: After last apt-get upgrade, touchpad no longer works. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Fri Jan 4 13:47:13 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP Folio 13 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-35-generic root=UUID=c2fa7f5e-0ada-4f3a-a39f-b8903ca5119d ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17F8 dmi.board.vendor: Hewlett-Packard dmi.board.version: 46.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.05:bd12/21/2011:svnHewlett-Packard:pnHPFolio13NotebookPC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Folio 13 Notebook PC dmi.product.version: 068C10204A0320100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816271] Re: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19
Yes, indeed, I think that may be it(new alsa config panel). They added boxes and the way it works and it seems NOW that if I unplug headphones, and boot, then go to settings/sound: set system vol to full set output device to "speakers-builtin audio" set configuration to "analog stereo output" Then the speakers appear in the test box and all works as it should. Plug in headphones and the selection changes as it should. And back and forth. Before, those settings would not hold through a boot, NOW they do. I did see some more alsa library stuff going in yesterday and today. Don't know what fixed it but it seems to be fixed. At the moment, I might guess an error in the new alsa config layout, and not pulseaudio. I did do alsamixer and changed automute (right arrow way over) ena to disa to ena, with tests interspersed, but that seemed to make no difference. Requires that you go to settings/sound and set stuff up correctly the first time.(I think) I am guessing that that would be the case after a clean install, but I will not test that. I think this should be closed/as solved, but I would like to be able to re-open it if the problem re-appears. Many thanks for all your time. -- 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/1816271 Title: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19 Status in pulseaudio package in Ubuntu: New Bug description: 19.04,kern 4.19.0-13 just took update and now does not recognize soundcard or something plugged in to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it wakes up and recognizes it and works fine. I thought I had this prob a few days ago and restored back to the 10th, and updated all but alsa and worked fine. This morning I checked and a bunch of alsa stuff was no longer showing in updates, took everything, and worked fine. Just took updates (Software Updater), and checked speakers and no go. When this happened, it also would not allow sound to HDTV via HDMI, no matter what. Just tested and was able to get sound via hdmi, but remember, I have already "woken it up" by unplugging and plugging headphones (actually sony vaio computer speakers) ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast! I expected sound to recognize soundcard/speakers. It did not until I unplug/replug headphones. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 19:20:26 2019 InstallationDate: Installed on 2019-02-09 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gst-plugins-good1.0 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kris 1512 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-09 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Tags: disco Uname: Linux 4.19.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETB4WW (2.74 ) dmi.board.asset.tag: Not Available dmi.board.name: 23943J8 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:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T530 dmi.product.name: 23943J8 dmi.product.sku: LENOVO_MT_2394 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1816947] [NEW] Touchpad not working after last apt-get upgrade
Public bug reported: already filed at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046 check: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input- synaptics/+bug/1096046/comments/33 affects: xserver-xorg-input-synaptics (Ubuntu) The bug is marked expired an low priority, but it really prevents me from using ubuntu or any other distro based on it on my machine. Please reopen it! the bug has been successfully reproduced on my machine using the latest daily build --- $ lspci -v 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller Flags: bus master, fast devsel, latency 0 Capabilities: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 2000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Dell 6 Series/C200 Series Chipset Family MEI Controller Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f0605000 (64-bit, non-prefetchable) [size=16] Capabilities: Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI]) Subsystem: Dell 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f060a000 (32-bit, non-prefetchable) [size=1K] Capabilities: Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Dell 6 Series/C200 Series Chipset Family High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at f060 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) (prog-if 00 [Normal decode]) Flags: fast devsel, IRQ 16 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Capabilities: Kernel driver in use: pcieport 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 17 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Memory behind bridge: f050-f05f Capabilities: Kernel driver in use: pcieport 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 19 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: f040-f04f Capabilities: Kernel driver in use: pcieport 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI]) Subsystem: Dell 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at f0609000 (32-bit, non-prefetchable) [size=1K] Capabilities: Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation QS67 Express Chipset LPC Controller (rev 05) Subsystem: Dell QS67 Express Chipset Family LPC Controller Flags: bus master, medium devsel, latency 0 Capabilities: Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Mobile SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0]) Subsystem: Dell 6 Series/C200 Series Chipset Family 6 port Mobile SATA AHCI Controller Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 29 I/O ports at 2088 [size=8] I/O ports at 2094 [size=4] I/O ports at 2080 [size=8] I/O ports at 2090 [size=4] I/O ports at 2060 [size=32] Memory at f0608000 (32-bit, non-prefetchable)
[Desktop-packages] [Bug 1096046] Re: Touchpad not working after last apt-get upgrade
tried to execute: apport-collect -p xserver-xorg-input-synaptics 1096046 but I get the following error: You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed. Please create a new report using "apport-bug" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1096046 Title: Touchpad not working after last apt-get upgrade Status in xserver-xorg-input-synaptics package in Ubuntu: Expired Bug description: After last apt-get upgrade, touchpad no longer works. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Fri Jan 4 13:47:13 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP Folio 13 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-35-generic root=UUID=c2fa7f5e-0ada-4f3a-a39f-b8903ca5119d ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17F8 dmi.board.vendor: Hewlett-Packard dmi.board.version: 46.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.05:bd12/21/2011:svnHewlett-Packard:pnHPFolio13NotebookPC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Folio 13 Notebook PC dmi.product.version: 068C10204A0320100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816945] [NEW] failsafeXServer does not parse Xorg.failsafe.log correctly
Public bug reported: The timestamp for Xorg.failsafe.log has changed, and is no longer parsed correctly by failsafeXServer Here is a sample error message from syslog 2019-02-15T12:30:36.028591-08:00 awabi failsafeXServer[7805]: expr: non-integer argument 2019-02-15T12:30:36.028735-08:00 awabi failsafeXServer[7805]: /usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected Currently, Xorg.failsafe.log looks like: [ 477.714] (II) Server terminated successfully (0). Closing log file. but failsafeXServer assumes that the date is seconds since 1970-01-01 00:00:00 UTC I have attached a patch which provides a solution to the problem. I look at the timestamp of the file, using %s, which provides seconds since 1970-01-01 00:00:00 UTC ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xdiagnose 3.8.8 [modified: usr/share/xdiagnose/failsafeXServer] ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Feb 20 18:17:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-18 (1374 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: xdiagnose UpgradeStatus: Upgraded to cosmic on 2018-11-01 (111 days ago) ** Affects: xdiagnose (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Patch added: "Patch to failsafeXServer" https://bugs.launchpad.net/bugs/1816945/+attachment/5240463/+files/failsafeXServer.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1816945 Title: failsafeXServer does not parse Xorg.failsafe.log correctly Status in xdiagnose package in Ubuntu: New Bug description: The timestamp for Xorg.failsafe.log has changed, and is no longer parsed correctly by failsafeXServer Here is a sample error message from syslog 2019-02-15T12:30:36.028591-08:00 awabi failsafeXServer[7805]: expr: non-integer argument 2019-02-15T12:30:36.028735-08:00 awabi failsafeXServer[7805]: /usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected Currently, Xorg.failsafe.log looks like: [ 477.714] (II) Server terminated successfully (0). Closing log file. but failsafeXServer assumes that the date is seconds since 1970-01-01 00:00:00 UTC I have attached a patch which provides a solution to the problem. I look at the timestamp of the file, using %s, which provides seconds since 1970-01-01 00:00:00 UTC ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xdiagnose 3.8.8 [modified: usr/share/xdiagnose/failsafeXServer] ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Feb 20 18:17:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-18 (1374 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: xdiagnose UpgradeStatus: Upgraded to cosmic on 2018-11-01 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1816945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1096046] Re: Touchpad not working after last apt-get upgrade
I've just downloaded daily ubutun from http://cdimage.ubuntu.com/daily- live/current/ and I can confirm that the issue is still happening on my machine: Machine: Device: portable System: Dell product: Dell System XPS L321X serial: N/A Mobo: Dell model: N/A serial: N/A UEFI [Legacy]: Dell v: A01 date: 12/27/2011 Chassis: type: 8 v: 0.1 serial: N/A I'll try to log in and post more info OTH, the workaround from http://askubuntu.com/a/262364/175109 seems to work, but I can't enable two-finger-scroll nor touch-to-click. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1096046 Title: Touchpad not working after last apt-get upgrade Status in xserver-xorg-input-synaptics package in Ubuntu: Expired Bug description: After last apt-get upgrade, touchpad no longer works. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Fri Jan 4 13:47:13 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP Folio 13 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-35-generic root=UUID=c2fa7f5e-0ada-4f3a-a39f-b8903ca5119d ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17F8 dmi.board.vendor: Hewlett-Packard dmi.board.version: 46.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.05:bd12/21/2011:svnHewlett-Packard:pnHPFolio13NotebookPC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Folio 13 Notebook PC dmi.product.version: 068C10204A0320100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
The mouse cursor moving is handled by the Xorg process, so if nothing else is responding then that suggests the problem is entirely in gnome- shell. To start, please run this command to send us more information about the machine: apport-collect 1816896 ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: cosmic resume suspend-resume -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816860] Re: Second display does not show up on dock of Lenovo Helix 2
I am keen to figure this problem out. But first please run this command to send us more information about the machine (while the dock is connected): apport-collect 1816860 ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1816860 Title: Second display does not show up on dock of Lenovo Helix 2 Status in xorg-server package in Ubuntu: Incomplete Bug description: To me a deal-breaker: I bought the Helix 2 as machine on the dock, and I also bought the one out of the three docks that doesn't need extra driver (so it says), the 4X10H04503. I stuck the tablet into it, with Windows, and the second display came up without any additional driver. With kubuntu 18.04 I can't make it appear. xrandr doesn't show it. Now I wonder, where else it might pop up? I mean, the dock works, I ran a unified Logitech receiver on it, and from the first second mouse and keyboard are available to my *buntu installation, of course the grub menu. I am quite disheartened, since I don't feel like going back to Windows after some 20 years on *nix. I am willing to help out as much as my very limited abilities allow me to. I can't believe that a dock which actually supplies power and keyboard and mouse data does not supply any information about the second monitor? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1816860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816855] Re: Errores en el inicio
Can you please provide a picture of the errors? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1816855 Title: Errores en el inicio Status in Ubuntu: Incomplete Bug description: Muestra errores al iniciar el sistema operativo antes de iniciar sesion. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 20 14:16:32 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF119M [NVS 4200M] [1028:1494] InstallationDate: Installed on 2019-01-03 (48 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=3cc56e6c-0d3d-440e-9ad2-69b353545a70 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1816855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816634] Re: GNOME Shell consistently ignores mouse clicks in a particular app window
Thanks for the quick response. It sounds like the bug(s) would still exist in the latest mutter/gnome- shell code so please report the problem to the Gnome developers here: https://gitlab.gnome.org/GNOME/mutter/issues and then tell us the new issue ID. -- 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/1816634 Title: GNOME Shell consistently ignores mouse clicks in a particular app window Status in gnome-shell package in Ubuntu: New Bug description: This is similar in some ways to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but affects only the mouse, not the keyboard, and is consistent almost all (99%+) of the time. This is happening for Ubuntu 18.04.2 LTS (bionic) in the default desktop environment (Ubuntu). It also happens for the GNOME and GNOME Classic desktop environments. The version of gnome- shell is 3.28.3-0ubuntu0.18.04.4. Our program is a blend of C# winforms (Mono) with embedded web browser windows using Geckofx45 (mozilla version 45). Editing windows in the program use HTML to display formatting and typescript/javascript code to assist with popup dialogs and other editing help. Inside these editing windows, left mouse clicks are essentially ignored. Keyboarding still works fine as far as I can tell. Clicking on the gear button inside the editing window fails to bring up the Styles dialog more than 95% of the time. When the dialog does display, it is always (100%) nonfunctional as the first click in it causes it to close immediately. Tracing the internal behavior of the code, it appears that clicking the first time inside the editing (browser) window causes a series of WM_FOCUS messages to be sent and the javascript to hook up a left mouse click handler to a gear button displayed in the lower left corner of the editing window. This is the expected behavior, and the same as on other window managers. But then, on GNOME Shell only, a series of WM_KILLFOCUS messages are sent immediately. This does not happen for other window managers. (The main window receives a WM_ACTIVATE message with the argument to make it deactivate.) Any other left mouse clicks inside that window are ignored >95% of the time, probably only when double clicking quickly enough to occur before those messages to lose focus/deactivate are handled. (Right mouse clicks are handled at a higher level and appear to function normally.) The program in question is called Bloom. The source code is available at https://github.com/BloomBooks/BloomDesktop and prebuilt debian/ubuntu packages are available at http://packages.sil.org/ubuntu/ as bloom-desktop or bloom-desktop- beta. After spending a few days looking at this problem, I've reluctantly come to the conclusion that it must be a GNOME Shell bug that I can't work around in our code. It's working fine in Microsoft Windows and all the other Linux window managers that I've tested (Unity, Cinnamon, KDE Plasma, MATE, XFCE, and LXDE). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816634/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809594] Re: unity-greeter triggering mouse cursor size inconsistency on 4K display
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-greeter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1809594 Title: unity-greeter triggering mouse cursor size inconsistency on 4K display Status in unity-greeter package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy unity-greeter unity-greeter: Installed: 18.04.0+18.04.20180314.1-0ubuntu2 $ cat /etc/X11/default-display-manager /usr/sbin/lightdm $ echo $DESKTOP_SESSION cinnamon Configuration: 4k screen (3840x2160) with 1920x1080 selected in Cinnamon Display settings. Hidpi turned off. What happens: inconsistent mouse cursor size across the screen (looks like hidpi is enabled for some areas of the screen but disabled for other areas). This bug has more details on how this affects users (reported for XFCE but I am seeing exactly the same behavior with Cinnamon): https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1770948 4k screen. Relevant xrandr output: 4096x2160 24.00 23.98 3840x2160 30.00 25.00 24.00 29.97 23.98 1920x1080 120.00 100.00 119.88 60.00* 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98 When switching to lightdm-gtk-greeter the issue goes away: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1770948/comments/11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1809594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816817] Re: unable to install grafix driver
It appears you have an Intel GPU so there is no additional graphics driver that needs to be installed -- it's already built in to Ubuntu. Is there a specific problem you are trying to solve? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1816817 Title: unable to install grafix driver Status in Ubuntu: Incomplete Bug description: need suggestion to install grafix driver in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 20 22:12:26 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:06c0] InstallationDate: Installed on 2019-02-18 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Vostro 3558 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=0f86b485-1857-417c-9a59-44574b48fb22 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 05JF1T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/09/2015:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn05JF1T:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 20 14:41:41 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1816817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
The problem with the lightdm workaround is that many had this cursor issue: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1770948 -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
Thanks. That makes this bug Fix Released (because it is fixed in some release, any release). And I think the fix would have been in the kernel. If you could try some different kernel versions, you might/should be able to find the version where it started working: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D Presently it seems that 4.15 is not working. But kernel 4.18 (in Ubuntu 18.10) does work. ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Fix Released Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
No problem. There's a working patch (apparently) in the Mesa bug: https://bugs.freedesktop.org/show_bug.cgi?id=109594 ** Changed in: totem (Ubuntu) Status: New => Invalid ** 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/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in totem package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME) --- I'm not sure, but this happened after updating to gstreamer 1.15.1, I have problems when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814801] Re: Sony bluetooth headphones don't connect with correct audio profile
*** This bug is a duplicate of bug 1181106 *** https://bugs.launchpad.net/bugs/1181106 Thanks. It sounds like you are experiencing bugs in the ballpark of bug 1181106 and bug 1789758. So I will defer to those because they are similar, but also because "Ubuntu" bug tasks should ideally be about Ubuntu systems, which those other bugs are. ** This bug has been marked a duplicate of bug 1181106 Failed to change profile to A2DP -- 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/1814801 Title: Sony bluetooth headphones don't connect with correct audio profile Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have connected my Sony bluetooth headphones (WH-H900N (h.ear)) to my Linux Mint 19 Tara system. After the initial connection when I disconnect the headphones and reconnect them later on when I view the headphones with the blueman-applet and look at the Audio Profile it shows Off. If I try to play audio I get no sound in the headphones. If I select High Fidelity Playback (A2DP Sink) most of the time audio will play through the headphones. (Occasionally, the first time I select High Fidelity Playback it doesn't stick and I have to pick it again.) $ lsb_release -rd Description: Linux Mint 19 Tara Release: 19 $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3.1 Candidate: 5.48-0ubuntu3.1 Version table: *** 5.48-0ubuntu3.1 500 500 http://pubmirrors.dal.corespace.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.48-0ubuntu3 500 500 http://pubmirrors.dal.corespace.com/ubuntu bionic/main amd64 Packages $ apt-cache policy blueman blueman: Installed: 2.0.5-1ubuntu1 Candidate: 2.0.5-1ubuntu1 Version table: *** 2.0.5-1ubuntu1 500 500 http://pubmirrors.dal.corespace.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Feb 5 11:26:52 jbodnar pulseaudio[2226]: [pulseaudio] module-bluez5-device.c: Profile a2dp_sink has no transport Feb 5 11:27:14 jbodnar pulseaudio[2226]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected Feb 5 11:27:22 jbodnar pulseaudio[2226]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: blueman-manager version 2.0.5 starting Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: card Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: change Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: card Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: change Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: card Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: remove Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: card Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: add Feb 5 11:27:31 jbodnar blueman-applet[25681]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed Feb 5 11:27:31 jbodnar kernel: [1121873.865918] input: 70:26:05:87:D1:64 as /devices/virtual/input/input44 Feb 5 11:27:44 jbodnar bluetoothd[889]: /org/bluez/hci0/dev_70_26_05_87_D1_64/fd15: fd(37) ready Feb 5 11:27:44 jbodnar rtkit-daemon[2229]: Supervising 3 threads of 1 processes of 1 users. Feb 5 11:27:44 jbodnar rtkit-daemon[2229]: Successfully made thread 1443 of process 2226 (n/a) owned by '1000' RT at priority 5. Feb 5 11:27:44 jbodnar rtkit-daemon[2229]: Supervising 4 threads of 1 processes of 1 users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] Re: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds
The next step would be to report the problem to the PulseAudio developers here: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues and then tell us the new bug ID. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: New Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815550] Re: RSS grows without limit, general slowness
In that case I would agree with the theory this is likely nvidia-related (or a new regression). The only other yardstick I have at the moment is my bionic desktop for which gnome-shell has been running for 5 days and RSS=293MB. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Tags added: nvidia -- 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/1815550 Title: RSS grows without limit, general slowness Status in gnome-shell package in Ubuntu: New Bug description: This *may* be an nvidia-specific problem, but the RSS of gnome-shell on my system grows without limit (over a couple of hours it's increased past 10G). At the same time, gnome-shell appears to become progressively less responsive. Restarting gnome-shell (via restart) drops shell RSS down to ~400MB and improves system responsiveness a bit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 4.20.0 Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 13:35:59 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1815550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
** Package changed: gnome-control-center (Ubuntu) => xorg-server (Ubuntu) ** Package changed: xorg-server (Ubuntu) => gdm3 (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Quick question, I have exactly the same problem but with one small difference. I have Asus Q325UA which is pretty much the black version of UX391UA as far as I know. lshw gives out the following information system Q325UAR busQ325UAR My concern is that since the system reports a different model, it will require yet another different line to be added to the patch. Can somebody shed some light if that model needs to be added separately or will the UX391UA fix the problem on QA325UA as well? Also, how should I go about submitting a request for the QA325UA if needed? Thanks! -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816458] Re: Full load
Sebastien Bacher, could you create a [0]package with the version of [1 ]"gnome-keyring 3.31.90"? My intention is to confirm or inform what happens with this version of the application. Thanks! [0] https://people.canonical.com/~seb128/lp1816458 [1] https://gitlab.gnome.org/GNOME/gnome-keyring/tags/3.31.90 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load Status in gnome-keyring package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of Problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Always. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Yes I was talking about the gdm3 workaround -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816896] [NEW] Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
Public bug reported: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gnome-control-center package in Ubuntu: New Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816896/+subscriptions -- Mailing list: https://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 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
There are two workarounds mentioned: swap to lightdm and manipulate gdm3 start. I think you refer to the gdm3 startup changes when you say it causes problems with suspend/resume (which I didn't try). The other workaround is changing display manager to lightdm (or sddm, the KDE display manager). swapping to lightdm has not caused any suspend/resume problems for me on the two Optimus laptops I used, so I think the lightdm workaround is ok. It was the default display manager of ubuntu for a long time and is still the default for xubuntu. On Thu, 21 Feb 2019 at 08:45, Stefano <1716...@bugs.launchpad.net> wrote: > Yes but this workaround is going to create others issue for suspend and > resume. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > gdm3, hybrid nvidia with modeset=1, no external monitors detected > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://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 1816539] Re: Searching by file type doesn't work
In the current 19.04 (disco) it works well. On feb 20 2019, at 1:29 du, Balázs Pere wrote: > When I choose a certain file type, the correct hits appears for a second, but > after that all hits come back. > > On Feb 20 2019, at 1:28 pm, Balázs Pere wrote: > > New packages in > > https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16410497 > > leaves unchanged this bug. > > > > On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote: > > > Indeed, that seems fixed in the current Ubuntu serie but buggy in > > > bionic, potentially something we want to fix in a SRU > > > > > > ** Changed in: nautilus (Ubuntu) > > > Importance: Undecided => High > > > > > > ** Changed in: nautilus (Ubuntu) > > > Status: New => Fix Released > > > > > > -- > > > You received this bug notification because you are subscribed to the bug > > > report. > > > https://bugs.launchpad.net/bugs/1816539 > > > > > > Title: > > > Searching by file type doesn't work > > > > > > Status in nautilus package in Ubuntu: > > > Fix Released > > > > > > Bug description: > > > When I click on searching in nautilus a down arrow appears on the > > > right (next to the input field). If I click on this arrow, a pop up > > > menu appears with "When" and "What" titles. Inside "What" I can choose > > > file types. Choosing a certain file type nothing happens, nautilus > > > shows the hits for every file type. This search option doesn't seem to > > > work. (For "Full Text" see Bug #1767817) > > > > > > $ lsb_release -rd > > > Description: Ubuntu 18.04.2 LTS > > > Release: 18.04 > > > > > > $ apt-cache policy nautilus > > > nautilus: > > > Installed: 1:3.26.4-0~ubuntu18.04.3 > > > Candidate: 1:3.26.4-0~ubuntu18.04.3 > > > Version table: > > > *** 1:3.26.4-0~ubuntu18.04.3 500 > > > 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages > > > 100 /var/lib/dpkg/status > > > 1:3.26.3-0ubuntu4 500 > > > 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions > > > > > > > > > -- 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/1816539 Title: Searching by file type doesn't work Status in nautilus package in Ubuntu: Fix Released Bug description: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1620336] Re: Publishing videos to Google Photos fails
This bug was fixed in the package shotwell - 0.30.2-0ubuntu1 --- shotwell (0.30.2-0ubuntu1) disco; urgency=medium * New upstream version - Fix issues with google and flickr not being able to log in (lp: #1620336) * debian/patches/git_notification_segfault.patch: - removed, that change is in the new version -- Sebastien Bacher Wed, 20 Feb 2019 17:25:41 +0100 ** Changed in: shotwell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1620336 Title: Publishing videos to Google Photos fails Status in shotwell package in Ubuntu: Fix Released Bug description: Shotwell can publish photos and videos to my Google Photos account using the Picasa plugin. Publishing photos works well. However, publishing videos results in an unusable video on Google Photos: Shotwell's upload seems to work, but selecting the video on Google Photos just shows a grey box with text "Your video will be finished shortly." This never changes (i.e., the video is obviously not processed correctly by Google Photos). Uploading the video through Google Photos' web interface works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 5 16:28:46 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-13 (267 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: shotwell UpgradeStatus: Upgraded to xenial on 2016-04-22 (136 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1620336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Yes but this workaround is going to create others issue for suspend and resume. -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://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 1816634] Re: GNOME Shell consistently ignores mouse clicks in a particular app window
Daniel, I tried Bloom on Ubuntu 18.10 and things have partially improved. Left mouse clicks inside the text boxes now move the current selection point in the text as expected. Left clicking on the gear button usually brings up the Styles dialog (a javascript dialog), but the next left click always closes the dialog without allowing the user to actually do anything. I wasn't able to install Bloom on the build for 19.04 because one of its dependencies had a dependency that couldn't be met. (chmsee / libwebkitgtk-1.0-0) (We'll probably phase out using .chm help files in the next year or two, but haven't come up with a suitable replacement that all of our projects like yet.) -- Steve McConnel On Tue, Feb 19, 2019 at 7:40 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Steve, > > This sounds like a problem that should be reported to the Gnome > developers. However before doing that, are you able to test if the > problem exists in Ubuntu 18.10 or 19.04? > > http://releases.ubuntu.com/18.10/ > http://cdimages.ubuntu.com/daily-live/current/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816634 > > Title: > GNOME Shell consistently ignores mouse clicks in a particular app > window > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > This is similar in some ways to > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but > affects only the mouse, not the keyboard, and is consistent almost all > (99%+) of the time. This is happening for Ubuntu 18.04.2 LTS (bionic) > in the default desktop environment (Ubuntu). It also happens for the > GNOME and GNOME Classic desktop environments. The version of gnome- > shell is 3.28.3-0ubuntu0.18.04.4. > > Our program is a blend of C# winforms (Mono) with embedded web browser > windows using Geckofx45 (mozilla version 45). Editing windows in the > program use HTML to display formatting and typescript/javascript code > to assist with popup dialogs and other editing help. Inside these > editing windows, left mouse clicks are essentially ignored. > Keyboarding still works fine as far as I can tell. Clicking on the > gear button inside the editing window fails to bring up the Styles > dialog more than 95% of the time. When the dialog does display, it is > always (100%) nonfunctional as the first click in it causes it to > close immediately. > > Tracing the internal behavior of the code, it appears that clicking > the first time inside the editing (browser) window causes a series of > WM_FOCUS messages to be sent and the javascript to hook up a left > mouse click handler to a gear button displayed in the lower left > corner of the editing window. This is the expected behavior, and the > same as on other window managers. But then, on GNOME Shell only, a > series of WM_KILLFOCUS messages are sent immediately. This does not > happen for other window managers. (The main window receives a > WM_ACTIVATE message with the argument to make it deactivate.) Any > other left mouse clicks inside that window are ignored >95% of the > time, probably only when double clicking quickly enough to occur > before those messages to lose focus/deactivate are handled. (Right > mouse clicks are handled at a higher level and appear to function > normally.) > > The program in question is called Bloom. The source code is available > at https://github.com/BloomBooks/BloomDesktop and prebuilt > debian/ubuntu packages are available at > http://packages.sil.org/ubuntu/ as bloom-desktop or bloom-desktop- > beta. After spending a few days looking at this problem, I've > reluctantly come to the conclusion that it must be a GNOME Shell bug > that I can't work around in our code. It's working fine in Microsoft > Windows and all the other Linux window managers that I've tested > (Unity, Cinnamon, KDE Plasma, MATE, XFCE, and LXDE). > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816634/+subscriptions > -- 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/1816634 Title: GNOME Shell consistently ignores mouse clicks in a particular app window Status in gnome-shell package in Ubuntu: New Bug description: This is similar in some ways to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but affects only the mouse, not the keyboard, and is consistent almost all (99%+) of the time. This is happening for Ubuntu 18.04.2 LTS (bionic) in the default desktop environment (Ubuntu). It also happens for the GNOME and GNOME Classic desktop environments. The version of gnome- shell is 3.28.3-0ubuntu0.18.04.4. Our program is a blend of C# winforms (Mono) with embedded web browser windows
[Desktop-packages] [Bug 1556724] Re: External monitor not working on Helix Thinkpad
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1556724 Title: External monitor not working on Helix Thinkpad Status in xorg package in Ubuntu: Confirmed Bug description: Under Ubuntu 15.10, I was able to attach an external monitor using the mini DPI port of the external keyboard. Under 16.04, xrandr reports seeing the second monitor, but switching to it results in no display. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Sun Mar 13 19:44:11 2016 DistUpgraded: 2016-03-13 18:03:20,688 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:222b] InstallationDate: Installed on 2015-12-20 (84 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20CH0022US ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=e48199f5-ebb9-4812-a803-71b19bb4647f ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-03-14 (0 days ago) dmi.bios.date: 08/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N17ET80W (1.80 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CH0022US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ET80W(1.80):bd08/21/2015:svnLENOVO:pn20CH0022US:pvrThinkPadHelix2nd:rvnLENOVO:rn20CH0022US:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.name: 20CH0022US dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 13 19:38:34 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1121 vendor LGD xserver.version: 2:1.18.1-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816860] [NEW] Second display does not show up on dock of Lenovo Helix 2
Public bug reported: To me a deal-breaker: I bought the Helix 2 as machine on the dock, and I also bought the one out of the three docks that doesn't need extra driver (so it says), the 4X10H04503. I stuck the tablet into it, with Windows, and the second display came up without any additional driver. With kubuntu 18.04 I can't make it appear. xrandr doesn't show it. Now I wonder, where else it might pop up? I mean, the dock works, I ran a unified Logitech receiver on it, and from the first second mouse and keyboard are available to my *buntu installation, of course the grub menu. I am quite disheartened, since I don't feel like going back to Windows after some 20 years on *nix. I am willing to help out as much as my very limited abilities allow me to. I can't believe that a dock which actually supplies power and keyboard and mouse data does not supply any information about the second monitor? ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1816860 Title: Second display does not show up on dock of Lenovo Helix 2 Status in xorg package in Ubuntu: New Bug description: To me a deal-breaker: I bought the Helix 2 as machine on the dock, and I also bought the one out of the three docks that doesn't need extra driver (so it says), the 4X10H04503. I stuck the tablet into it, with Windows, and the second display came up without any additional driver. With kubuntu 18.04 I can't make it appear. xrandr doesn't show it. Now I wonder, where else it might pop up? I mean, the dock works, I ran a unified Logitech receiver on it, and from the first second mouse and keyboard are available to my *buntu installation, of course the grub menu. I am quite disheartened, since I don't feel like going back to Windows after some 20 years on *nix. I am willing to help out as much as my very limited abilities allow me to. I can't believe that a dock which actually supplies power and keyboard and mouse data does not supply any information about the second monitor? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1816860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816855] [NEW] Errores en el inicio
Public bug reported: Muestra errores al iniciar el sistema operativo antes de iniciar sesion. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 20 14:16:32 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF119M [NVS 4200M] [1028:1494] InstallationDate: Installed on 2019-01-03 (48 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=3cc56e6c-0d3d-440e-9ad2-69b353545a70 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1816855 Title: Errores en el inicio Status in xorg package in Ubuntu: New Bug description: Muestra errores al iniciar el sistema operativo antes de iniciar sesion. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 20 14:16:32 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF119M [NVS 4200M] [1028:1494] InstallationDate: Installed on 2019-01-03 (48 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=3cc56e6c-0d3d-440e-9ad2-69b353545a70 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1
[Desktop-packages] [Bug 1766495] Re: "your libfreerdp does not support h264"
How and where can I change the color depth? I don't see the option in the settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1766495 Title: "your libfreerdp does not support h264" Status in remmina package in Ubuntu: Confirmed Bug description: When I try to connect via RDP, Remmina gives this error: "You requested an h264 GFX mode for server , but your libfreerdp does not support h264. Please check color depth settings." However, (1) I don't see any color depth settings in Remmina GUI, and (2) ubuntu-restricted-extras is installed. I have libx264-152 version 2:0.152.2854+gite9a5903-2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 24 09:29:44 2018 InstallationDate: Installed on 2018-03-23 (31 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1766495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 393012] Re: [SRU] smb: Error while copying file, "Invalid argument"
This happens now on 18.04. I can use the shares from a Linux machine for several hours after reboot. But eventually it will stop working getting above error message. -- 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/393012 Title: [SRU] smb: Error while copying file, "Invalid argument" Status in autofs: Confirmed Status in gvfs: Unknown Status in samba: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Maverick: Invalid Status in samba source package in Maverick: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: nautilus While copying a folder from ubuntu to a Windows XP PC, I get an error message, "Error while copying "Tarantula-1.jpg". "There was an error copying the file into smb://asus1/documents/Tarantula." Show more details: Invalid argument The source folder is called "Tarantula", which contains: /host/Documents and Settings/All Users/Documents/Tarantula> ls -sail total 15545 1124200 drwxrwxrwx 1 root root 0 2009-06-27 11:41 . 38564 drwxrwxrwx 1 root root4096 2009-06-27 16:43 .. 1124261 -rwxrwxrwx 1 root root 59 2009-06-27 11:40 .picasa.ini -rwxrwxrwx 1 root root 2622811 2009-06-27 11:41 Tarantula-1.jpg -rwxrwxrwx 1 root root 2565675 2009-06-27 11:41 Tarantula-2.jpg -rwxrwxrwx 1 root root 2449986 2009-06-27 11:41 Tarantula-3.jpg -rwxrwxrwx 1 root root 2442001 2009-06-27 11:41 Tarantula-4.jpg -rwxrwxrwx 1 root root 2596930 2009-06-27 11:41 Tarantula-5.jpg -rwxrwxrwx 1 root root 3218977 2009-06-27 11:40 Tarantula.jpg I am able to read and delete files on the remote Win XP PC shared folder asus1/documents. The folder does not exist on this remote PC. At the start of the copy, Nautilus creates the folder "Tarantula", then terminates with the error: "Error while copying "Tarantula-1.jpg". The Tarantula folder on the remote PC (as reported from Nautilus 2.26.2 File Browser): Location: smb://asus1/documents/Tarantula Tarantula-1.jpg , size = 64.0 KB, type = JPEG Image, group = unknown, Octal Permissions = unknown, Owner = unknown, Permissions = unknown .picasa.ini = 59 bytes, type = unknown, group = unknown, Octal Permissions = unknown, Owner = unknown, Permissions = unknown It appears that the .ini file was copied completely, as I can open and read the file in a text editor. The JPEG image was partially copied when smb terminated. The problem can be repeated. This may be a problem with smb. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/nautilus NonfreeKernelModules: nvidia Package: nautilus 1:2.26.2-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus Uname: Linux 2.6.28-13-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/autofs/+bug/393012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] Re: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds
I have the same issue. And progress on this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: New Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716139] Re: Remove "Ubuntu" identifier from User Agent strings
Also, the chromium snap UA has extra info identifying it as a snap: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/72.0.3626.96 Chrome/72.0.3626.96 Safari/537.36" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1716139 Title: Remove "Ubuntu" identifier from User Agent strings Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: The Chromium and Firefox builds add an extra Ubuntu identifier in their user-agent strings. The inclusion of the OS name is unnecessary and could contribute to user fingerprinting. Other distros such as Fedora do not add their name to the distro browser builds' UA as far as I can tell, and google-chrome UAs do not reveal OS distro version info. chromium-browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/60.0.3112.113 Chrome/60.0.3112.113 Safari/537.36 Change to: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chromium/60.0.3112.113 Chrome/60.0.3112.113 Safari/537.36 Firefox: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 Change to: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 In Firefox the build ID can identify the package build anyway so it isn't necessary to have the distro in the UA string. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1716139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
Works in 18.10 -- 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797882]
Created attachment 143415 libdrm_ignore_deadlock -- 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/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Status in Mesa: Confirmed Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: 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 i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: LANGUAGE=en_US:en 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/mesa/+bug/1797882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797882]
Created attachment 143414 fix intel_blit.c fix error_patch2 -- 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/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Status in Mesa: Confirmed Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: 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 i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: LANGUAGE=en_US:en 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/mesa/+bug/1797882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797882]
Some more investigation, understanding and adding 2 other possible fixes for the problem. The problem occurs at Ubuntu 18.10 only at gdm3 with wayland using dual monitor. It is not occuring with wayland at single monitor. It totally doesnot occur if gdm3 is not using wayland. At ubuntu 18.04 the same problem exists with wayland, but is not occurring so often. At ubuntu 18.10 with wayland and dual monitor the user session immediately aborts, if 16 or more favorites are allocated at the dock. For some reason wayland seems to use one extra fence register at dual monitor. It is noticed at dual monitor, that gdm3 with wayland uses 2 calls to clutter_stage_cogl_redraw_view for 2 logical screens for every call to clutter_stage_cogl_redraw; gdm3 without wayland does only one call to clutter_stage_cogl_redraw_view for 1 logical screen. The crash occurs at intel_batchbuffer_flush. Always the last batch at such a flush is coming from function emit_copy_blit and intelClearWithBlit at src/mesa/drivers/dri/i915/intel_blit.c. At the call to dri_bufmgr_check_aperture_space they indicate to use zero fence registers, but in fact they use one. This violates the limit of 14, causing a crash at dual monitor. So the call to dri_bufmgr_check_aperture_space must be postponed, until the needed fence register is added in the middle of the batch-generation and then the batch-actions must be undone, a flush is called and batch is regenerated again. For this function intel_batchbuffer_emit_reset is added. This also is done for function intel_miptree_set_alpha_to_one, although I never saw a call of this function. See fix error3_patch2.txt. Another (dirty) solution is to decrement the availablity and just continue. This gives somewhere a failure, but I could not see a failing layout. See fix error3_patch3.txt. -- 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/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Status in Mesa: Confirmed Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: 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 i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps'
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
Hello, I was affected, I just now tried to re-install nvidia-390 (I purged everything about nvidia) "sudo apt-get install nvidia-390", and after that and reboot everything works fine with 18.04 hwe kernel 390.87 nvidia driver installed (the link in the posts above is about 390.77 version), I don't know if my box get it from main repository or from nvidia-ppa, maybe second one for me bug is closed -- 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/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04
[Desktop-packages] [Bug 1814801] Re: Sony bluetooth headphones don't connect with correct audio profile
I put Ubuntu 18.04-2 on a USB driver and booted up. I got slightly different behavior: 1. When I first paired the headphones with my laptop the audio profile was High Fidelity Playback (A2DP Sink) and everything sounded good. 2. When I turned off the headphones, waited for the Bluetooth devices window to say the headphones had been disconnected and then powered the headphones back on and waited for them to auto-connect the audio profile was Headset Head Unit (HSP/HFP) and all sound was in mono. 3. If I disconnected the headphones using the Bluetooth devices window and then reconnected the headphones using the Bluetooth devices window the audio profile was High Fidelity Playback (A2DP Sink) and the sound was in stereo. I removed blueman from my Mint system and still experience the original issue. Here's what I have installed on my Mint system: $ apt list --installed | grep blue WARNING: apt does not have a stable CLI interface. Use with caution in scripts. blueberry/tara,tara,now 1.2.3 all [installed] bluetooth/bionic-updates,bionic-updates,now 5.48-0ubuntu3.1 all [installed] bluez/bionic-updates,now 5.48-0ubuntu3.1 amd64 [installed] bluez-cups/bionic-updates,now 5.48-0ubuntu3.1 amd64 [installed] bluez-obexd/bionic-updates,now 5.48-0ubuntu3.1 amd64 [installed] bluez-tools/bionic,now 0.2.0~20140808-5build1 amd64 [installed] gir1.2-gnomebluetooth-1.0/bionic-updates,bionic-security,now 3.28.0-2ubuntu0.1 amd64 [installed] gnome-bluetooth/bionic-updates,bionic-security,now 3.28.0-2ubuntu0.1 amd64 [installed] libbluetooth3/bionic-updates,now 5.48-0ubuntu3.1 amd64 [installed] libgnome-bluetooth13/bionic-updates,bionic-security,now 3.28.0-2ubuntu0.1 amd64 [installed] pulseaudio-module-bluetooth/bionic-updates,now 1:11.1-1ubuntu7.1 amd64 [installed] -- 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/1814801 Title: Sony bluetooth headphones don't connect with correct audio profile Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have connected my Sony bluetooth headphones (WH-H900N (h.ear)) to my Linux Mint 19 Tara system. After the initial connection when I disconnect the headphones and reconnect them later on when I view the headphones with the blueman-applet and look at the Audio Profile it shows Off. If I try to play audio I get no sound in the headphones. If I select High Fidelity Playback (A2DP Sink) most of the time audio will play through the headphones. (Occasionally, the first time I select High Fidelity Playback it doesn't stick and I have to pick it again.) $ lsb_release -rd Description: Linux Mint 19 Tara Release: 19 $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3.1 Candidate: 5.48-0ubuntu3.1 Version table: *** 5.48-0ubuntu3.1 500 500 http://pubmirrors.dal.corespace.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.48-0ubuntu3 500 500 http://pubmirrors.dal.corespace.com/ubuntu bionic/main amd64 Packages $ apt-cache policy blueman blueman: Installed: 2.0.5-1ubuntu1 Candidate: 2.0.5-1ubuntu1 Version table: *** 2.0.5-1ubuntu1 500 500 http://pubmirrors.dal.corespace.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Feb 5 11:26:52 jbodnar pulseaudio[2226]: [pulseaudio] module-bluez5-device.c: Profile a2dp_sink has no transport Feb 5 11:27:14 jbodnar pulseaudio[2226]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected Feb 5 11:27:22 jbodnar pulseaudio[2226]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: blueman-manager version 2.0.5 starting Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: card Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: change Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: card Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: change Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: card Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: remove Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: card Feb 5 11:27:25 jbodnar org.blueman.Applet[2086]: add Feb 5 11:27:31 jbodnar blueman-applet[25681]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed Feb 5 11:27:31 jbodnar kernel: [1121873.865918] input: 70:26:05:87:D1:64 as /devices/virtual/input/input44 Feb 5 11:27:44 jbodnar bluetoothd[889]: /org/bluez/hci0/dev_70_26_05_87_D1_64/fd15: fd(37) ready Feb 5 11:27:44 jbodnar rtkit-daemon[2229]: Supervising 3 threads of 1 processes of 1 users. Feb 5 11:27:44 jbodnar rtkit-daemon[2229]: Successfully made thread 1443 of process 2226 (n/a) owned by '1000' RT at priority 5. Feb 5 11:27:44 jbodnar rtkit-daemon[2229]: Supervising 4 threads of 1 processes of 1
[Desktop-packages] [Bug 1816817] [NEW] unable to install grafix driver
Public bug reported: need suggestion to install grafix driver in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 20 22:12:26 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:06c0] InstallationDate: Installed on 2019-02-18 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Vostro 3558 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=0f86b485-1857-417c-9a59-44574b48fb22 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 05JF1T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/09/2015:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn05JF1T:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 20 14:41:41 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1816817 Title: unable to install grafix driver Status in xorg package in Ubuntu: New Bug description: need suggestion to install grafix driver in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 20 22:12:26 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:06c0] InstallationDate: Installed on 2019-02-18 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Vostro 3558 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=0f86b485-1857-417c-9a59-44574b48fb22 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 05JF1T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/09/2015:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn05JF1T:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Desktop-packages] [Bug 1816458] Re: Full load
Never stop the process 'gnome-keyring-daemon', I must close it with 'kill -9 '. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load Status in gnome-keyring package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of Problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Always. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
** Also affects: gnome-terminal (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: gnome-terminal (Ubuntu Xenial) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1762391 Title: pam_group.so is not evaluated by gnome-terminal Status in systemd: New Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Won't Fix Bug description: We are using Ubuntu in a university network with lots of ldap users. To automatically map ldap users/groups to local groups we are using pam_group.so. This has worked for years. With the upgrade from Xenial to Bionic /etc/security/group.conf is not evaluated anymore by gnome-terminal as it runs as systemd --user. Xterm, ssh, su, and tty* however do work as expected. Only the default gnome-terminal behaves different. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this might not be a bug, but a feature. Nevertheless this behavior is very unexpected when upgrading from Xenial to Bionic and therefore should at least added to the changelog. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 13:17:52 2018 InstallationDate: Installed on 2018-03-29 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816808] [NEW] [disco] OSK does not appear under wayland when a text-entry is focused
Public bug reported: 1. Login in a wayland session 2. Open an application with a text entry (e.g. gedit) 3. Focus gedit using the touch screen Expected result: The OSK appears Actual results: The OSK does not appear. --- This is caused by the fact that we still set GTK_IM_MODULE in Wayland. IIRC during the cosmic cycle we introduced a change to not set GTK_IM_MODULE under Wayland but we dropped it because there were users experiencing crashes when using libreoffice: upstream should have fixed those crashes to my knowledge. Also why are we setting GTK_IM_MODULE in X11 too? gnome-settings-daemon should be smart enough to load/unload that at run-time when required /not-required. ** Affects: im-config (Ubuntu) Importance: Medium Status: New ** Changed in: im-config (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1816808 Title: [disco] OSK does not appear under wayland when a text-entry is focused Status in im-config package in Ubuntu: New Bug description: 1. Login in a wayland session 2. Open an application with a text entry (e.g. gedit) 3. Focus gedit using the touch screen Expected result: The OSK appears Actual results: The OSK does not appear. --- This is caused by the fact that we still set GTK_IM_MODULE in Wayland. IIRC during the cosmic cycle we introduced a change to not set GTK_IM_MODULE under Wayland but we dropped it because there were users experiencing crashes when using libreoffice: upstream should have fixed those crashes to my knowledge. Also why are we setting GTK_IM_MODULE in X11 too? gnome-settings- daemon should be smart enough to load/unload that at run-time when required/not-required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1816808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
** No longer affects: libdrm (Ubuntu) ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** Bug watch added: freedesktop.org Bugzilla #109594 https://bugs.freedesktop.org/show_bug.cgi?id=109594 ** Also affects: totem via https://bugs.freedesktop.org/show_bug.cgi?id=109594 Importance: Unknown Status: Unknown ** Project changed: totem => mesa ** Description changed: - https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa) - - --- - https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME) --- I'm not sure, but this happened after updating to gstreamer 1.15.1, I have problems when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. Status in Mesa: Unknown Status in mesa package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME) --- I'm not sure, but this happened after updating to gstreamer 1.15.1, I have problems when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816800] [NEW] package libcups2:i386 2.2.8-5ubuntu1.2 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: instale el ubuntu 18.10 pero el instalador de software de ubuntu no instala nada ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libcups2:i386 2.2.8-5ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Wed Feb 20 11:03:43 2019 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2019-02-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. X505BA PackageArchitecture: i386 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=e25785df-8eb7-49f4-9c1c-eaa81657f382 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=e25785df-8eb7-49f4-9c1c-eaa81657f382 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: cups Title: package libcups2:i386 2.2.8-5ubuntu1.2 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.308:bd12/26/2017:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package cosmic i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1816800 Title: package libcups2:i386 2.2.8-5ubuntu1.2 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in cups package in Ubuntu: New Bug description: instale el ubuntu 18.10 pero el instalador de software de ubuntu no instala nada ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libcups2:i386 2.2.8-5ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Wed Feb 20 11:03:43 2019 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2019-02-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. X505BA PackageArchitecture: i386 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=e25785df-8eb7-49f4-9c1c-eaa81657f382 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=e25785df-8eb7-49f4-9c1c-eaa81657f382 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: cups Title: package libcups2:i386 2.2.8-5ubuntu1.2 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.308:bd12/26/2017:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1816800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770929] Re: backup fails with UnicodeDecodeError
Same here unbuntu 18.04 lts french
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in
inner_retry
util.uexc(e)), code=code, extra=extra)
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 36:
ordinal not in range(128)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
backup fails with UnicodeDecodeError
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
backup worked under Ubuntu 17.10
It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
my drive is encrypted
this is the error message in the error frame
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 09:55:00 2018
InstallationDate: Installed on 2018-05-01 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816780] Re: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
** Tags removed: need-duplicate-check -- 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/1816780 Title: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mesa package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Feb 20 22:03:16 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:162b] InstallationDate: Installed on 2019-02-14 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP EliteBook 2560p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b4f30c78-5458-4470-9efe-b17753fcc893 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: mesa Title: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SSU Ver. F.22 dmi.board.name: 162B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 04.21 dmi.chassis.asset.tag: CNU2101KVC dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SSUVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001C02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.21:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2560p dmi.product.version: A0001C02 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.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/mesa/+bug/1816780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816780] [NEW] package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp
Public bug reported: i don't know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Feb 20 22:03:16 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:162b] InstallationDate: Installed on 2019-02-14 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP EliteBook 2560p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b4f30c78-5458-4470-9efe-b17753fcc893 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: mesa Title: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SSU Ver. F.22 dmi.board.name: 162B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 04.21 dmi.chassis.asset.tag: CNU2101KVC dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SSUVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001C02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.21:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2560p dmi.product.version: A0001C02 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.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 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ubuntu -- 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/1816780 Title: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mesa package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Feb 20 22:03:16 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:162b] InstallationDate: Installed on 2019-02-14 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP EliteBook 2560p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b4f30c78-5458-4470-9efe-b17753fcc893 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: mesa Title: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SSU Ver. F.22 dmi.board.name: 162B dmi.board.vendor:
[Desktop-packages] [Bug 1667208] Re: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1667208
Title:
Ubuntu's selenium hardcodes a path that is valid for Debian, but not
for Ubuntu
Status in chromium-browser package in Ubuntu:
In Progress
Status in python-selenium package in Ubuntu:
Invalid
Bug description:
Hi.
The package python{,3}-selenium uses a hardcoded path of
'/usr/lib/chromium/chromedriver' when instantiating a Chrome
webdriver.
That path is correct for Debian (in particular, it was directly
inherited from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=805733#5), but since Ubuntu uses chromium-
browser instead of Debian's chromium naming. The package chromium-
chromedriver in Ubuntu installs the webdriver at '/usr/lib/chromium-
browser/chromedriver'.
There needs to be a synchronization between the selenium Python module
and the webdriver package.
Thanks,
Rogério Brito.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: python3-selenium 2.53.2+dfsg1-1
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 23 01:38:24 2017
Dependencies:
InstallationDate: Installed on 2016-12-11 (73 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64
(20161012.1)
PackageArchitecture: all
SourcePackage: python-selenium
UpgradeStatus: Upgraded to zesty on 2017-01-31 (23 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667208/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770929] Re: backup fails with UnicodeDecodeError
Same here unbuntu 18.04 lts french
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in
inner_retry
util.uexc(e)), code=code, extra=extra)
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 36:
ordinal not in range(128)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
backup fails with UnicodeDecodeError
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
backup worked under Ubuntu 17.10
It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
my drive is encrypted
this is the error message in the error frame
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 09:55:00 2018
InstallationDate: Installed on 2018-05-01 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772683]
Do you have a working PPA I could install future updates from where the product would be supported? FYI- the link previously provided is not / no longer valid. I do see this: https://launchpad.net/df-libreoffice which then directs at the bottom to where I have installed from: "LibreOffice packaging for Ubuntu can be found at: https://launchpad.net/~libreoffice; -- 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/1772683 Title: [snap] Cannot sign a document, gpg keys are not listed Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Triaged Bug description: (initially reported on the forum: https://forum.snapcraft.io/t /libreoffice-snap-missing-features-and-known-bugs/3920/10) Libreoffice 6.0.4.2 (64, candidate channel). Steps to reproduce: 1) snap run libreoffice.writer 2) write something, then save the document (anywhere) on disk 3) Open the File menu, then Digital Signatures > Digital Signatures… 4) in the dialog, click "Sign Document…" Expected result: your GPG keys are listed Current result: no keys are listed To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: jython (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - openjdk-lts 11 needs newer build dependencies - various packages have runtime failures when run with openjdk-11 A few packages *must* be updated/patched before openjdk-11 itself is uploaded: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667208] Re: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
** Branch linked: lp:~chromium-team/chromium-browser/cosmic-stable
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1667208
Title:
Ubuntu's selenium hardcodes a path that is valid for Debian, but not
for Ubuntu
Status in chromium-browser package in Ubuntu:
Confirmed
Status in python-selenium package in Ubuntu:
Invalid
Bug description:
Hi.
The package python{,3}-selenium uses a hardcoded path of
'/usr/lib/chromium/chromedriver' when instantiating a Chrome
webdriver.
That path is correct for Debian (in particular, it was directly
inherited from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=805733#5), but since Ubuntu uses chromium-
browser instead of Debian's chromium naming. The package chromium-
chromedriver in Ubuntu installs the webdriver at '/usr/lib/chromium-
browser/chromedriver'.
There needs to be a synchronization between the selenium Python module
and the webdriver package.
Thanks,
Rogério Brito.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: python3-selenium 2.53.2+dfsg1-1
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 23 01:38:24 2017
Dependencies:
InstallationDate: Installed on 2016-12-11 (73 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64
(20161012.1)
PackageArchitecture: all
SourcePackage: python-selenium
UpgradeStatus: Upgraded to zesty on 2017-01-31 (23 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667208/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816761] Re: add on dropdowns too small on 150% with wayland
** Description changed: - The dropdowns for addons are too small and do not fit the content + After changing from laptop screen to 4k monitor, the dropdowns for + addons are too small and do not fit the content, and text is blury. It + appears as though firefox doesn't fully register the dpi change. - screenshots to follow + https://i.imgur.com/znlAQ66.png + https://i.imgur.com/y5Z5MPv.png ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 65.0+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: graingert 2382 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: graingert 2382 F pulseaudio BuildID: 20190128173924 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Feb 20 13:48:21 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-02-15 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: - default via 10.9.0.1 dev wlp59s0 proto dhcp metric 600 - 10.9.0.0/16 dev wlp59s0 proto kernel scope link src 10.9.98.239 metric 600 - 10.11.0.0/16 via 10.9.0.129 dev wlp59s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp59s0 scope link metric 1000 + default via 10.9.0.1 dev wlp59s0 proto dhcp metric 600 + 10.9.0.0/16 dev wlp59s0 proto kernel scope link src 10.9.98.239 metric 600 + 10.11.0.0/16 via 10.9.0.129 dev wlp59s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp59s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=65.0/20190128173924 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N20ET40W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN20ET40W(1.25):bd01/15/2019:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X280 dmi.product.name: 20KFCTO1WW dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280 dmi.product.version: ThinkPad X280 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1816761 Title: add on dropdowns too small on 150% with wayland Status in firefox package in Ubuntu: New Bug description: After changing from laptop screen to 4k monitor, the dropdowns for addons are too small and do not fit the content, and text is blury. It appears as though firefox doesn't fully register the dpi change. https://i.imgur.com/znlAQ66.png https://i.imgur.com/y5Z5MPv.png ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 65.0+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graingert 2382 F pulseaudio BuildID: 20190128173924 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Feb 20 13:48:21 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-02-15 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 10.9.0.1 dev wlp59s0 proto dhcp metric 600 10.9.0.0/16 dev wlp59s0 proto kernel scope link src 10.9.98.239 metric 600 10.11.0.0/16 via 10.9.0.129 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=65.0/20190128173924
[Desktop-packages] [Bug 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
** Tags added: bugpattern-written -- 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/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816761] [NEW] add on dropdowns too small on 150% with wayland
Public bug reported: The dropdowns for addons are too small and do not fit the content screenshots to follow ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 65.0+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graingert 2382 F pulseaudio BuildID: 20190128173924 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Feb 20 13:48:21 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-02-15 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 10.9.0.1 dev wlp59s0 proto dhcp metric 600 10.9.0.0/16 dev wlp59s0 proto kernel scope link src 10.9.98.239 metric 600 10.11.0.0/16 via 10.9.0.129 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=65.0/20190128173924 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N20ET40W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN20ET40W(1.25):bd01/15/2019:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X280 dmi.product.name: 20KFCTO1WW dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280 dmi.product.version: ThinkPad X280 dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1816761 Title: add on dropdowns too small on 150% with wayland Status in firefox package in Ubuntu: New Bug description: The dropdowns for addons are too small and do not fit the content screenshots to follow ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 65.0+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graingert 2382 F pulseaudio BuildID: 20190128173924 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Feb 20 13:48:21 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-02-15 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 10.9.0.1 dev wlp59s0 proto dhcp metric 600 10.9.0.0/16 dev wlp59s0 proto kernel scope link src 10.9.98.239 metric 600 10.11.0.0/16 via 10.9.0.129 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=65.0/20190128173924 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N20ET40W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN20ET40W(1.25):bd01/15/2019:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X280 dmi.product.name: 20KFCTO1WW dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280 dmi.product.version: ThinkPad X280 dmi.sys.vendor: LENOVO To manage notifications about this bug go
[Desktop-packages] [Bug 1640181] Re: nvidia driver fails to build [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type]
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 ** This bug is no longer a duplicate of bug 1642241 nvidia-*: nvidia-* kernel module failed to build with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type] ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1640181 Title: nvidia driver fails to build [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type] Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: /var/lib/dkms/nvidia-370/370.28/build/nvidia/os-mlock.c:120:55: error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type [-Werror=incompatible-pointer-types] page_count, write, force, user_pages, NULL); ^~ - Can't go past the greeter loop with a nvidia driver. Compilation fails at dkms level. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.8.0-27-generic 4.8.0-27.29 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1777 F pulseaudio /dev/snd/controlC0: oem1777 F pulseaudio CurrentDesktop: GNOME Date: Tue Nov 8 15:01:20 2016 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth1 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816458] Re: Full load
Upstream might have an idea but there is nothing special in those backtraces, is seems to just be waiting for event, were they taken at the time of the issue when happening? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load Status in gnome-keyring package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of Problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Always. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642283] Re: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 ** This bug is no longer a duplicate of bug 1642241 nvidia-*: nvidia-* kernel module failed to build with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type] ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1642283 Title: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: With new 4.9 kernel from proposed. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: nvidia-367 367.57-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 4.9.0-1-generic Date: Wed Nov 16 15:44:47 2016 DuplicateSignature: dkms:nvidia-367:367.57-0ubuntu3:/var/lib/dkms/nvidia-367/367.57/build/nvidia/os-mlock.c:120:55: error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2016-03-18 (242 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160317) PackageVersion: 367.57-0ubuntu3 RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: nvidia-graphics-drivers-367 Title: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build UpgradeStatus: Upgraded to zesty on 2016-11-07 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1642283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1643425] Re: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 ** This bug is no longer a duplicate of bug 1642241 nvidia-*: nvidia-* kernel module failed to build with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type] ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1643425 Title: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build Status in nvidia-graphics-drivers-367 package in Ubuntu: New Bug description: Message appears right after fresh boot upon login ProblemType: Package DistroRelease: Ubuntu 17.04 Package: nvidia-367 367.57-0ubuntu3 ProcVersionSignature: Ubuntu 4.9.0-1.2-generic 4.9.0-rc5 Uname: Linux 4.9.0-1-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 4.9.0-1-generic Date: Sun Nov 20 22:22:27 2016 DuplicateSignature: dkms:nvidia-367:367.57-0ubuntu3:/var/lib/dkms/nvidia-367/367.57/build/nvidia/os-mlock.c:120:55: error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2016-10-27 (24 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161027) PackageVersion: 367.57-0ubuntu3 RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: nvidia-graphics-drivers-367 Title: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1643425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642241] Re: nvidia-*: nvidia-* kernel module failed to build with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type]
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1573508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- 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/1642241 Title: nvidia-*: nvidia-* kernel module failed to build with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type] Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: nvidia 340.98 is failed with kernel 4.9.x ProblemType: Package DistroRelease: Ubuntu 17.04 Package: nvidia-340 340.98-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.98 Mon Sep 19 17:31:03 PDT 2016 GCC version: gcc version 6.2.0 20161109 (Ubuntu 6.2.0-13ubuntu1) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 4.9.0-1-generic Date: Wed Nov 16 12:06:39 2016 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed bbswitch, 0.8, 4.9.0-1-generic, x86_64: installed nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed nvidia-340, 340.98, 4.8.0-27-generic, x86_64: installed DuplicateSignature: dkms:nvidia-340:340.98-0ubuntu1:/var/lib/dkms/nvidia-340/340.98/build/os-mlock.c:49:55: error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation GT218 [GeForce G210] [10de:0a60] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Pegatron GT218 [GeForce G210] [1b0a:9045] InstallationDate: Installed on 2016-11-13 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161112) MachineType: Hewlett-Packard HP Elite 7100 Microtower PC PackageVersion: 340.98-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=c7607fd8-02eb-40f0-b3fb-25acb82c79e2 ro quiet splash RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.98-0ubuntu1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.19 dmi.board.name: 2A9Ch dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: CZC0375QV2 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.19:bd03/23/2011:svnHewlett-Packard:pnHPElite7100MicrotowerPC:pvrxxx0204GR0:rvnMSI:rn2A9Ch:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP Elite 7100 Microtower PC dmi.product.version: xxx0204GR0 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.04.20161114.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.73-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1665019] Re: nvidia kernel module failed to build [error: too few arguments to function ‘get_user_pages_remote’]
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1573508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- 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/1665019 Title: nvidia kernel module failed to build [error: too few arguments to function ‘get_user_pages_remote’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: beta 17.04 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: nvidia-340 340.101-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.10.0-8-generic Date: Wed Feb 15 10:17:39 2017 DuplicateSignature: dkms:nvidia-340:340.101-0ubuntu1:/var/lib/dkms/nvidia-340/340.101/build/nv-linux.h:2122:20: error: too few arguments to function ‘get_user_pages_remote’ InstallationDate: Installed on 2017-01-26 (20 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageVersion: 340.101-0ubuntu1 RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~rc1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.101-0ubuntu1: nvidia-340 kernel module failed to build UpgradeStatus: Upgraded to zesty on 2017-01-27 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1665019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
Michael Sweet was not able to reproduce this bug with the Canon printer he got at Apple. See https://github.com/apple/cups/issues/5512 Please post in this bug report to directly interact with Michael. Before doing so, get a setup of Disco (upcoming Ubuntu 19.04) and check whether your problem still exists. Disco contains all the fixes mentioned in the upstream bug reports. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in cups package in Ubuntu: Triaged Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1815307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816458] Re: Full load
't a a bt' worked. Do you need any other information? ** Attachment added: "gdb-gnome-keyring-daemon-v4.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240218/+files/gdb-gnome-keyring-daemon-v4.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load Status in gnome-keyring package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of Problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Always. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "cupsd.conf" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+attachment/5240210/+files/cupsd.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "lpstat-before" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+attachment/5240212/+files/lpstat-before -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "error_log" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+attachment/5240217/+files/error_log ** Changed in: cups-filters (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "cups-browsed.conf" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+attachment/5240211/+files/cups-browsed.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
the "-after" files are (and logs) are taken after suspening and waking up the laptop, with the printer off. the output of lpstat -v is empty after the printer has gone ** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "printers.conf-after" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+attachment/5240214/+files/printers.conf-after -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "cups-browsed_log" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+attachment/5240216/+files/cups-browsed_log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "access_log" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+attachment/5240215/+files/access_log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "printers.conf-before" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+attachment/5240213/+files/printers.conf-before -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off
I'm seeing this again in Cosmic with the following versions: ii cups 2.2.8-5ubuntu1.2 amd64Common UNIX Printing System(tm) - PPD/driver support, web interface ii cups-browsed 1.21.3-1 amd64OpenPrinting CUPS Filters - cups-browsed ii cups-bsd 2.2.8-5ubuntu1.2 amd64Common UNIX Printing System(tm) - BSD commands ii cups-client 2.2.8-5ubuntu1.2 amd64Common UNIX Printing System(tm) - client programs (SysV) ii cups-common 2.2.8-5ubuntu1.2 all Common UNIX Printing System(tm) - common files ii cups-core-drivers 2.2.8-5ubuntu1.2 amd64Common UNIX Printing System(tm) - driverless printing ii cups-daemon 2.2.8-5ubuntu1.2 amd64Common UNIX Printing System(tm) - daemon ii cups-filters 1.21.3-1 amd64OpenPrinting CUPS Filters - Main Package ii cups-filters-core-drivers 1.21.3-1 amd64OpenPrinting CUPS Filters - Driverless printing ii cups-ipp-utils2.2.8-5ubuntu1.2 amd64Common UNIX Printing System(tm) - IPP developer/admin utilities ii cups-pk-helper0.2.6-1ubuntu3 amd64PolicyKit helper to configure cups with fine-grained privileges ii cups-ppdc 2.2.8-5ubuntu1.2 amd64Common UNIX Printing System(tm) - PPD manipulation utilities ii cups-server-common2.2.8-5ubuntu1.2 all Common UNIX Printing System(tm) - server common files Attaching logs as described in #4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups-filters package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- Mailing list: https://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 1816539] Re: Searching by file type doesn't work
When I choose a certain file type, the correct hits appears for a second, but after that all hits come back. On Feb 20 2019, at 1:28 pm, Balázs Pere wrote: > New packages in > https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16410497 > leaves unchanged this bug. > > On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote: > > Indeed, that seems fixed in the current Ubuntu serie but buggy in > > bionic, potentially something we want to fix in a SRU > > > > ** Changed in: nautilus (Ubuntu) > > Importance: Undecided => High > > > > ** Changed in: nautilus (Ubuntu) > > Status: New => Fix Released > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1816539 > > > > Title: > > Searching by file type doesn't work > > > > Status in nautilus package in Ubuntu: > > Fix Released > > > > Bug description: > > When I click on searching in nautilus a down arrow appears on the > > right (next to the input field). If I click on this arrow, a pop up > > menu appears with "When" and "What" titles. Inside "What" I can choose > > file types. Choosing a certain file type nothing happens, nautilus > > shows the hits for every file type. This search option doesn't seem to > > work. (For "Full Text" see Bug #1767817) > > > > $ lsb_release -rd > > Description: Ubuntu 18.04.2 LTS > > Release: 18.04 > > > > $ apt-cache policy nautilus > > nautilus: > > Installed: 1:3.26.4-0~ubuntu18.04.3 > > Candidate: 1:3.26.4-0~ubuntu18.04.3 > > Version table: > > *** 1:3.26.4-0~ubuntu18.04.3 500 > > 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages > > 100 /var/lib/dpkg/status > > 1:3.26.3-0ubuntu4 500 > > 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions > > > > -- 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/1816539 Title: Searching by file type doesn't work Status in nautilus package in Ubuntu: Fix Released Bug description: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions -- Mailing list: https://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 1767817] Re: Full text search does not work
It seems to work well. Sometimes it hang up, shows "searching" in the right bottom corner of nautilus window. If I delete back some characters in the input field, it starts to work again. On Feb 20 2019, at 9:11 am, Sebastien Bacher wrote: > Yes, it's fixed in the Disco serie, I've uploaded a test package to > https://launchpad.net/~ubuntu- > desktop/+archive/ubuntu/ppa/+build/16410497 > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1764995). > https://bugs.launchpad.net/bugs/1767817 > > Title: > Full text search does not work > > Status in nautilus package in Ubuntu: > In Progress > > Bug description: > Background: I have installed Tracker. It has finished indexing. I can > also use Tracker's command line interface to search by content. > > 1. > Description: Ubuntu 18.04 LTS > Release: 18.04 > > 2. > nautilus: > Installed: 1:3.26.3-0ubuntu4 > Candidate: 1:3.26.3-0ubuntu4 > Version table: > *** 1:3.26.3-0ubuntu4 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > 100 /var/lib/dpkg/status > > 3. I expect to be able to search files by content from Nautilus, > because this feature worked in 17.10. > > 4. I get no results from full text search unless the search matches > file names. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions > -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: In Progress Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://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 1816539] Re: Searching by file type doesn't work
New packages in https://launchpad.net/~ubuntu- desktop/+archive/ubuntu/ppa/+build/16410497 leaves unchanged this bug. On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote: > Indeed, that seems fixed in the current Ubuntu serie but buggy in > bionic, potentially something we want to fix in a SRU > > ** Changed in: nautilus (Ubuntu) > Importance: Undecided => High > > ** Changed in: nautilus (Ubuntu) > Status: New => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816539 > > Title: > Searching by file type doesn't work > > Status in nautilus package in Ubuntu: > Fix Released > > Bug description: > When I click on searching in nautilus a down arrow appears on the > right (next to the input field). If I click on this arrow, a pop up > menu appears with "When" and "What" titles. Inside "What" I can choose > file types. Choosing a certain file type nothing happens, nautilus > shows the hits for every file type. This search option doesn't seem to > work. (For "Full Text" see Bug #1767817) > > $ lsb_release -rd > Description: Ubuntu 18.04.2 LTS > Release: 18.04 > > $ apt-cache policy nautilus > nautilus: > Installed: 1:3.26.4-0~ubuntu18.04.3 > Candidate: 1:3.26.4-0~ubuntu18.04.3 > Version table: > *** 1:3.26.4-0~ubuntu18.04.3 500 > 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages > 100 /var/lib/dpkg/status > 1:3.26.3-0ubuntu4 500 > 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions > -- 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/1816539 Title: Searching by file type doesn't work Status in nautilus package in Ubuntu: Fix Released Bug description: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816458] Re: Full load
't a a bt' worked. Do you need any other information? Please, just let him know. ** Attachment added: "gdb-gnome-keyring-daemon-v3.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240207/+files/gdb-gnome-keyring-daemon-v3.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load Status in gnome-keyring package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of Problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Always. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816458] Re: Full load
*daemon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load Status in gnome-keyring package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of Problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Always. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816458] Re: Full load
** Attachment added: "gdb-gnome-keyring-deamon-v2.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240206/+files/gdb-gnome-keyring-deamon-v2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load Status in gnome-keyring package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of Problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Always. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 41179]
The madest thing for me is that now other browsers integrate with platform keyring. Why not Firefox ? - Since other browsers have it, political arguments are weak - Since Quantum overhaul, technical one are weak too. Mozilla had an opportunity to deal with is issue that is a *major* usability and security issue. Let's say FF displays the profile in a corner like Google Chrome. Let's say this could be associated with a FF Sync account. On profile switch, it could ask for password or not, depending on a user profile locking pref. We already know the OS user is able to unlock all FF identifier stores, because this is how keyring work. But with a live (vs on startup) profile management, FF could offer the opportunity to manage switching. Just my 2 cents, but 12 years on, it is time to look at what other successful browser are doing... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/41179 Title: Integrate with Gnome Keyring Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: For a really good Gnome integration, it would be great to have the ability to save passwords in the Gnome keyring. A similar thing has been proposed for Epiphany: see https://launchpad.net/malone/bugs/3467. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/41179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
