[Desktop-packages] [Bug 2056356] [NEW] Screen blank with only curson - Ubuntu 20.04.6 + Intel + X1 Carbon Gen11
Public bug reported: It seems an intel video driver update is needed to get Ubuntu 20.04.6 working on the Lenovo X1 Carbon Gen 11. On boot, only a blank screen appears with a blinking cursor. Here are some details: # lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 # apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917+git20200226-1 Candidate: 2:2.99.917+git20200226-1 uname -a Linux hostname 5.15.0-97-generic #107~20.04.1-Ubuntu SMP Fri Feb 9 14:20:11 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux lshw -C video *-display UNCLAIMED description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 04 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list configuration: latency=0 resources: iomemory:600-5ff iomemory:400-3ff memory:603d00-603dff memory:40-400fff ioport:2000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 # Xorg -configure X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 Build Operating System: linux Ubuntu Current Operating System: Linux hostname 5.15.0-97-generic #107~20.04.1-Ubuntu SMP Fri Feb 9 14:20:11 UTC 2024 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-5.15.0-97-generic root=/dev/mapper/ub2004-root_vol ro i915.enable_psr=0 pci=noaer quiet splash vt.handoff=7 Build Date: 29 January 2024 12:44:21PM xorg-server 2:1.20.13-1ubuntu1~20.04.15 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 17:03:45 2024 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.15.0-97-generic intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. Of particular note is this portion of the prior command: modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.15.0-97-generic intel: waited 2020 ms for i915.ko driver to load Additionally, here are some errors and warnings from a log file: /var/lib/gdm3/.local/share/xorg# grep "EE\|WW" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [63.123] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [63.123] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [63.123] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [63.123] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [63.123] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [63.131] (WW) Falling back to old probe method for modesetting [63.131] (EE) open /dev/fb0: Permission denied [63.131] (WW) Falling back to old probe method for fbdev [63.132] (EE) open /dev/fb0: Permission denied [63.132] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [63.132] (EE) Screen 0 deleted because of no matching config section. [63.132] (EE) Screen 1 deleted because of no matching config section. [63.132] (EE) [63.132] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices [63.132] (EE) [63.132] (EE) [63.132] (EE) Please also check the log file at "/var/lib/gdm3/.local/share/xorg/Xorg.0.log" for additional information. [63.132] (EE) [63.136] (EE) Server terminated with error (1). Closing log file. # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 12 On-line CPU(s) list:0-11 Thread(s) per core: 1 Core(s) per socket: 10 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 186 Model name: 13th Gen Intel(R) Core(TM) i7-1355U Stepping: 3 CPU MHz:
[Desktop-packages] [Bug 2049424] Re: Grayscreen
How frustrating I have spent hours researching this issue including
numerous reboots and logins.
After opening this bug I logged in to get my processes started expecting
the frozen gray screen and the display came up without an issue.
If there is anything that can be gained by further examination of this
issue please let me know how I can help. If not, please close this bug.
Thank you
--
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/2049424
Title:
Grayscreen
Status in xorg package in Ubuntu:
New
Bug description:
Dell Precision 3660
I upgraded BIOS to 2.11.1 which also upgraded some other things.
When I login into Xubuntu I get a frozen gray screen
jim@jim:~/Scripts$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
jim@jim:~/Scripts$ uname -r
6.5.0-14-generic
I can boot into the install flashdrive under Try Xubuntu and the
display works fine.
Flash Drive:
xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
xubuntu@xubuntu:~$ uname -r
6.5.0-9-generic
Please provide a workaround as this is my primary workstation.
Let me know if you need any additional information.
Thank you
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
Date: Mon Jan 15 10:37:25 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA
controller])
Subsystem: Dell AlderLake-S GT1 [1028:0a9f]
InstallationDate: Installed on 2023-10-14 (93 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/03/2024
dmi.bios.release: 2.11
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.11.1
dmi.board.name: 0KM9JV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.7
dmi.modalias:
dmi:bvnDellInc.:bvr2.11.1:bd01/03/2024:br2.11:efr1.7:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0KM9JV:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
dmi.product.family: Precision
dmi.product.name: Precision 3660
dmi.product.sku: 0A9F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2049424/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049424] [NEW] Grayscreen
Public bug reported:
Dell Precision 3660
I upgraded BIOS to 2.11.1 which also upgraded some other things.
When I login into Xubuntu I get a frozen gray screen
jim@jim:~/Scripts$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev
0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
jim@jim:~/Scripts$ uname -r
6.5.0-14-generic
I can boot into the install flashdrive under Try Xubuntu and the display
works fine.
Flash Drive:
xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev
0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
xubuntu@xubuntu:~$ uname -r
6.5.0-9-generic
Please provide a workaround as this is my primary workstation.
Let me know if you need any additional information.
Thank you
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
Date: Mon Jan 15 10:37:25 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA
controller])
Subsystem: Dell AlderLake-S GT1 [1028:0a9f]
InstallationDate: Installed on 2023-10-14 (93 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/03/2024
dmi.bios.release: 2.11
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.11.1
dmi.board.name: 0KM9JV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.7
dmi.modalias:
dmi:bvnDellInc.:bvr2.11.1:bd01/03/2024:br2.11:efr1.7:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0KM9JV:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
dmi.product.family: Precision
dmi.product.name: Precision 3660
dmi.product.sku: 0A9F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2049424
Title:
Grayscreen
Status in xorg package in Ubuntu:
New
Bug description:
Dell Precision 3660
I upgraded BIOS to 2.11.1 which also upgraded some other things.
When I login into Xubuntu I get a frozen gray screen
jim@jim:~/Scripts$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
jim@jim:~/Scripts$ uname -r
6.5.0-14-generic
I can boot into the install flashdrive under Try Xubuntu and the
display works fine.
Flash Drive:
xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
xubuntu@xubuntu:~$ uname -r
6.5.0-9-generic
Please provide a workaround as this is my primary workstation.
Let me know if you need any additional information.
Thank you
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied:
[Desktop-packages] [Bug 2023909] [NEW] gnome-s+ CPU useage spike to 100%+ on mouse move
Public bug reported: when i move my mouse, the gnome-s+ CPU usage spike > 100%, RES > 1G. iam using Ubunto 22.4 LS and i'm using X11. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 18:36:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-21 (205 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2023909 Title: gnome-s+ CPU useage spike to 100%+ on mouse move Status in gnome-shell package in Ubuntu: New Bug description: when i move my mouse, the gnome-s+ CPU usage spike > 100%, RES > 1G. iam using Ubunto 22.4 LS and i'm using X11. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 18:36:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-21 (205 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 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/2023909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I'd forgotten about this until now. It's been working for me lately. I don't know what changed apart from updating to 22.10 last year. $ apt-cache policy nautilus gvfs nautilus: Installed: 1:43.0-1ubuntu2.1 Candidate: 1:43.0-1ubuntu2.1 Version table: *** 1:43.0-1ubuntu2.1 500 500 http://au.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu kinetic-security/main amd64 Packages 100 /var/lib/dpkg/status 1:43.0-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages gvfs: Installed: 1.50.2-2 Candidate: 1.50.2-2 Version table: *** 1.50.2-2 500 500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Confirmed Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
Adding my name to this as I use an old W10 laptop for accessing USGOV sites until the issue is fixed. -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1994435] Re: Proprietary NVIDIA drivers stopped working as of 10/24/22 update
As of the 12/6/22 update to Ubuntu 22.04.1 LTS, the NVIDIA driver metapackage from nvidia-driver-525 works. I have not tested the other NVIDIA drivers. -- 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/1994435 Title: Proprietary NVIDIA drivers stopped working as of 10/24/22 update Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Ubuntu Release: 22.04.1.LTS Problem: On 10/24/22, I installed the latest Ubuntu 22.04.1 LTS updates. I don't know what was updated, but many of the packages had "oem" or "oracle" in their names, which I don't remember seeing before. Before updating, I had a NVIDIA driver from the "Software & Updates/Additional Drivers" list installed and I was using X11. I don't remember the driver version number, but it was the highest. After updating, Settings/About/Graphics changed from a GeForce RTX 2080 Ti to "llvmpipe (LLVM 13.0.1, 256 bits)". Windowing system was still X11. My three-monitor setup reverted to one monitor, and the display was of low resolution. I tried proprietary NVIDIA drivers 515, 510, and 470, but none restored the system to three monitors and high resolution. However, the Nouveau driver did restore the system. Settings/About/Graphics changed to NV162. Work-Around: I am now using the driver installed via "sudo sh NVIDIA- Linux-x86_64-515.76.run", from NVIDIA's website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1994435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1994435] Re: Proprietary NVIDIA drivers stopped working as of 10/24/22 update
When I selected proprietary driver 515 and rebooted, I found these NVIDIA-related errors in /var/log/kern.log: Oct 25 15:29:27 office kernel: [ 20.554599] [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to allocate NvKmsKapiDevice Oct 25 15:29:27 office kernel: [ 20.554852] [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to register device I have attached the kern.log file. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1994435/+attachment/5626730/+files/kern.log -- 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/1994435 Title: Proprietary NVIDIA drivers stopped working as of 10/24/22 update Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Ubuntu Release: 22.04.1.LTS Problem: On 10/24/22, I installed the latest Ubuntu 22.04.1 LTS updates. I don't know what was updated, but many of the packages had "oem" or "oracle" in their names, which I don't remember seeing before. Before updating, I had a NVIDIA driver from the "Software & Updates/Additional Drivers" list installed and I was using X11. I don't remember the driver version number, but it was the highest. After updating, Settings/About/Graphics changed from a GeForce RTX 2080 Ti to "llvmpipe (LLVM 13.0.1, 256 bits)". Windowing system was still X11. My three-monitor setup reverted to one monitor, and the display was of low resolution. I tried proprietary NVIDIA drivers 515, 510, and 470, but none restored the system to three monitors and high resolution. However, the Nouveau driver did restore the system. Settings/About/Graphics changed to NV162. Work-Around: I am now using the driver installed via "sudo sh NVIDIA- Linux-x86_64-515.76.run", from NVIDIA's website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1994435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1994435] [NEW] Proprietary NVIDIA drivers stopped working as of 10/24/22 update
Public bug reported: Ubuntu Release: 22.04.1.LTS Problem: On 10/24/22, I installed the latest Ubuntu 22.04.1 LTS updates. I don't know what was updated, but many of the packages had "oem" or "oracle" in their names, which I don't remember seeing before. Before updating, I had a NVIDIA driver from the "Software & Updates/Additional Drivers" list installed and I was using X11. I don't remember the driver version number, but it was the highest. After updating, Settings/About/Graphics changed from a GeForce RTX 2080 Ti to "llvmpipe (LLVM 13.0.1, 256 bits)". Windowing system was still X11. My three-monitor setup reverted to one monitor, and the display was of low resolution. I tried proprietary NVIDIA drivers 515, 510, and 470, but none restored the system to three monitors and high resolution. However, the Nouveau driver did restore the system. Settings/About/Graphics changed to NV162. Work-Around: I am now using the driver installed via "sudo sh NVIDIA- Linux-x86_64-515.76.run", from NVIDIA's website. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- 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/1994435 Title: Proprietary NVIDIA drivers stopped working as of 10/24/22 update Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Ubuntu Release: 22.04.1.LTS Problem: On 10/24/22, I installed the latest Ubuntu 22.04.1 LTS updates. I don't know what was updated, but many of the packages had "oem" or "oracle" in their names, which I don't remember seeing before. Before updating, I had a NVIDIA driver from the "Software & Updates/Additional Drivers" list installed and I was using X11. I don't remember the driver version number, but it was the highest. After updating, Settings/About/Graphics changed from a GeForce RTX 2080 Ti to "llvmpipe (LLVM 13.0.1, 256 bits)". Windowing system was still X11. My three-monitor setup reverted to one monitor, and the display was of low resolution. I tried proprietary NVIDIA drivers 515, 510, and 470, but none restored the system to three monitors and high resolution. However, the Nouveau driver did restore the system. Settings/About/Graphics changed to NV162. Work-Around: I am now using the driver installed via "sudo sh NVIDIA- Linux-x86_64-515.76.run", from NVIDIA's website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1994435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966084] Re: Nautilus file/folder highlight color won't follow accent color change until restart the file manager
** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966084 Title: Nautilus file/folder highlight color won't follow accent color change until restart the file manager Status in gnome-control-center package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: Thanks for the new accent color option under 'Appearance' settings page. However, the text background of highlighted file or folder in file manager does not follow the accent color change, until restart Nautilus (via nautilus -q). How to Reproduce: 1. Open 'Files' and select a file or folder. 2. Open 'Settings' and select another color under 'Appearance' settings page. 3. The background of filename or folder name still use the previous color. 1) Ubuntu version: Ubuntu 22.04 development branch. 2) Software version: gnome-control-center 1:41.4-1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966084] [NEW] Nautilus file/folder highlight color won't follow accent color change until restart the file manager
Public bug reported: Thanks for the new accent color option under 'Appearance' settings page. However, the text background of highlighted file or folder in file manager does not follow the accent color change, until restart Nautilus (via nautilus -q). How to Reproduce: 1. Open 'Files' and select a file or folder. 2. Open 'Settings' and select another color under 'Appearance' settings page. 3. The background of filename or folder name still use the previous color. 1) Ubuntu version: Ubuntu 22.04 development branch. 2) Software version: gnome-control-center 1:41.4-1ubuntu8 ** 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/1966084 Title: Nautilus file/folder highlight color won't follow accent color change until restart the file manager Status in gnome-control-center package in Ubuntu: New Bug description: Thanks for the new accent color option under 'Appearance' settings page. However, the text background of highlighted file or folder in file manager does not follow the accent color change, until restart Nautilus (via nautilus -q). How to Reproduce: 1. Open 'Files' and select a file or folder. 2. Open 'Settings' and select another color under 'Appearance' settings page. 3. The background of filename or folder name still use the previous color. 1) Ubuntu version: Ubuntu 22.04 development branch. 2) Software version: gnome-control-center 1:41.4-1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965622] Re: Gnome Shell color sticks to Light mode after selected non-default accent color
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1965622 Title: Gnome Shell color sticks to Light mode after selected non-default accent color Status in gnome-control-center package in Ubuntu: Fix Released Bug description: 1.) Ubuntu version: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2.) Gnome Control Center version: 1:41.4-1ubuntu6 3.) Expected behavior: Switch Light and Dark in 'Appearance' page change full system colors: app window color and Gnome Shell color (colors of system menu, app icon context menu, etc). 4.) What happened instead: But, after changed accent color from orange to another, system menu, app icon context menu, etc (except desktop & nautilus' context menu) always have Light color. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 10:20:50 2022 InstallationDate: Installed on 2022-03-06 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965622] [NEW] Gnome Shell color sticks to Light mode after selected non-default accent color
Public bug reported: 1.) Ubuntu version: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2.) Gnome Control Center version: 1:41.4-1ubuntu6 3.) Expected behavior: Switch Light and Dark in 'Appearance' page change full system colors: app window color and Gnome Shell color (colors of system menu, app icon context menu, etc). 4.) What happened instead: But, after changed accent color from orange to another, system menu, app icon context menu, etc (except desktop & nautilus' context menu) always have Light color. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 10:20:50 2022 InstallationDate: Installed on 2022-03-06 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1965622 Title: Gnome Shell color sticks to Light mode after selected non-default accent color Status in gnome-control-center package in Ubuntu: New Bug description: 1.) Ubuntu version: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2.) Gnome Control Center version: 1:41.4-1ubuntu6 3.) Expected behavior: Switch Light and Dark in 'Appearance' page change full system colors: app window color and Gnome Shell color (colors of system menu, app icon context menu, etc). 4.) What happened instead: But, after changed accent color from orange to another, system menu, app icon context menu, etc (except desktop & nautilus' context menu) always have Light color. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 10:20:50 2022 InstallationDate: Installed on 2022-03-06 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961530] [NEW] CUPS driver does not send anything to printer during test print
Public bug reported: Downloaded and installed Turboprint driver for Canon iP90 but balked at the high ($55 USD) price. The 30 day free trial ended and I found that the iP90 printer would operate after installing the iP110 driver (with the iP90-Cups or the iP90-Gutenprint drivers, it would only output 25 or so blank pages with faint printing at the top of the page). Canon didn't make a Linux driver for the iP90 printer that I can find. Today, tried to uninstall Turboprint but it seems to be all over my printer config setup. As part of that, I uninstalled the 'working' iP110 driver setup. Deleted it from the printer window. Now when I install the CUPS generic iP110 driver, and try to print a test page, it does nothing. Doesn't even wink the printers activity light and doesn't show the print job in the print queue. So it seems that Turboprint insinuated itself into the system in a way that prevents it's total removal and is somehow blocking the CUPS drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Feb 20 10:26:57 2022 Lpstat: device for Canon-iP90: usb://Canon/iP90?serial=31A4B2 MachineType: Gigabyte Technology Co., Ltd. A520M S2H Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-iP90.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-iP90.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=c201ceca-9f5a-4845-b650-e68fc9d5230f ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to impish on 2021-10-15 (128 days ago) dmi.bios.date: 07/27/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: A520M S2H 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.:bvrF2:bd07/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnA520MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA520MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: A520 MB dmi.product.name: A520M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1961530 Title: CUPS driver does not send anything to printer during test print Status in cups package in Ubuntu: New Bug description: Downloaded and installed Turboprint driver for Canon iP90 but balked at the high ($55 USD) price. The 30 day free trial ended and I found that the iP90 printer would operate after installing the iP110 driver (with the iP90-Cups or the iP90-Gutenprint drivers, it would only output 25 or so blank pages with faint printing at the top of the page). Canon didn't make a Linux driver for the iP90 printer that I can find. Today, tried to uninstall Turboprint but it seems to be all over my printer config setup. As part of that, I uninstalled the 'working' iP110 driver setup. Deleted it from the printer window. Now when I install the CUPS generic iP110 driver, and try to print a test page, it does nothing. Doesn't even wink the printers activity light and doesn't show the print job in the print queue. So it seems that Turboprint insinuated itself into the system in a way that prevents it's total removal and is somehow blocking the CUPS drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Feb 20 10:26:57 2022 Lpstat: device for Canon-iP90: usb://Canon/iP90?serial=31A4B2 MachineType: Gigabyte Technology Co., Ltd. A520M S2H Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-iP90.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-iP90.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Desktop-packages] [Bug 1953379] [NEW] terminal terminates on large select all
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 Repo: 1. Open a new terminal and turn on menu bar 2. Turn off scrollback limit in Preferences 3. Run a command that produces a lot of output. For example, enable 'locate' command, and use it to produce thousands of lines with something like 'locate a' 4. Go to Edit, Select All Result: terminal process will end and terminal disappears; seems to crash on out of memory Expected: Select All works, or, a popup with an error such as "Select All requires 19 GiB, but memory is insufficient." Note: I have VMWare installed; not sure if VMWare clipboard crashes, or if it is the terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 6 12:29:45 2021 InstallationDate: Installed on 2020-11-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1953379 Title: terminal terminates on large select all Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 Repo: 1. Open a new terminal and turn on menu bar 2. Turn off scrollback limit in Preferences 3. Run a command that produces a lot of output. For example, enable 'locate' command, and use it to produce thousands of lines with something like 'locate a' 4. Go to Edit, Select All Result: terminal process will end and terminal disappears; seems to crash on out of memory Expected: Select All works, or, a popup with an error such as "Select All requires 19 GiB, but memory is insufficient." Note: I have VMWare installed; not sure if VMWare clipboard crashes, or if it is the terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 6 12:29:45 2021 InstallationDate: Installed on 2020-11-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1953379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I can reproduce this with sudo mount -t cifs -o noauto,rw,uid=1000,gid=1000,guest,nounix,noserverino,file_mode=0660,dir_mode=0755,iocharset=utf8,vers=2.1 //192.168.1.1/backup/ /media/grumpy/brick followed by running nautilus The network drive is a USB hard disk attached to my router. It's formatted to NTFS. -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Incomplete Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951075] [NEW] Nautilus doesn't load and gives GVFS-WARNING
Public bug reported: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer-to- peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: New Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921527] [NEW] Call to cupsGetDestMediaDefault always returns Letter
Public bug reported: The following always returns size of Letter regardless of what the default is set to at localhost:631. This is the case for multiple printers and printer manufacturers. cups_size_t size; int count = cupsGetDestMediaDefault(CUPS_HTTP_DEFAULT, m_dest, m_info, 0, ); Ubuntu 20.04 CUPS 2.3.1-9ubuntu1.1 gcc 9.3.0 For driverless printers, the PPD file shows the correct default. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- 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/1921527 Title: Call to cupsGetDestMediaDefault always returns Letter Status in cups package in Ubuntu: New Bug description: The following always returns size of Letter regardless of what the default is set to at localhost:631. This is the case for multiple printers and printer manufacturers. cups_size_t size; int count = cupsGetDestMediaDefault(CUPS_HTTP_DEFAULT, m_dest, m_info, 0, ); Ubuntu 20.04 CUPS 2.3.1-9ubuntu1.1 gcc 9.3.0 For driverless printers, the PPD file shows the correct default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1921527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917705] Re: "profile will be deleted" at startup after chromium 89 update
If the profile is managed, it seems that local data is deleted - at least it becomes unusable, so it might as well be deleted. If that is avoidable, it would be good to do so. I can understand why you would want to delete the local data associated with a managed profile in some circumstances, but "Google deprecated an API" doesn't seem like one of them. Another mitigation would be to provide a message that makes it clearer that the problem is with Chromium and not with the managed account. That would save a lot of wasted time between employees and their company tech support. (Though maybe it's too late for this to be useful - perhaps everyone who is going to hit this bug has done so already.) -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917713] Re: [snap] Logged out of Chromium after latest update to 89
I think I am also hitting this same bug. I'm running Chromium 1506 from Snap on Ubuntu 20.04. I have two Chromium profiles. One of them is managed by my employer. When I try to start that one, I get the error message: "Your account is no longer allowed as the primary account. Because this account is managed by , your bookmarks, history, passwords and other settings will be cleared from this device." This profile seems to now be unusable - when I ack the error message, Chromium immediately quits. The other is my personal account. I can use this account, but although I am logged in to my Google account, Chromium itself is no longer logged in - I have a blank icon in the top right where my user avatar should be. When I open the dropdown, it says "Not logged in". -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. The current profile is named "Person 1". Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+subscriptions -- Mailing list: https://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 1898389] Re: browser frequently crashing with trap int3
My workaround is to close chromium frequently (closing its x-window rather than normal exit from the browser) and restart it, in order to save all my open tabs. This seems to release the excess memory and CPU that is being hogged by this atrocious piece of software. On Tue, 26 Jan 2021, Fevrin wrote: > Just to note, the kernel trap int3 issue persists for me, even in the > latest Chromium release for Ubuntu 20.04.1, Version 88.0.4324.96 > (Official Build) snap (64-bit). > > Here's my kernel info: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Linux cweeks-XPS-13-9380 5.4.0-59-generic #65-Ubuntu SMP Thu Dec 10 12:01:51 > UTC 2020 x86_64 x86_64 x86_64 GNU/Linux > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > I'm seeing errors like the following: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Jan 26 13:25:14 XPS-13-9380 kernel: traps: chrome[2013993] trap int3 > ip:562b6998b3de sp:7ffe6c8b6a30 error:0 in chrome[562b64e8d000+7548000] > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.176240:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.178190:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.179527:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.180881:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Expired > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962
[Desktop-packages] [Bug 1909372] [NEW] PS2 mouse stopped working the upgrade before this one, still not working. FIX IT PLS!
Public bug reported: Last upgrade, having the PS2 mouse connected caused Ubuntu 20.04.1 to lock up the computer on a black screen. ASUS Mobo, Quad core AMD, 64-bit; 1 TB WD HDD. Mobo is a circa 2014 so still well within it's life. Withdrawing support for PS2 equipment at this EARLY stage makes us computer owners wonder why as there's no reason to do that this early. They are still making and selling brand new PS2 mice and keyboards! This bug likely applies to PS2 keyboards as well though I didn't test that. This upgrade, first one since Ubuntu stopped supporting PS2 equipmnet a couple three weeks ago (it's 12/26/20 today), it didn't lock up the computer this time so that was fixed, but PS2 mice still don't work!?? Why?? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Dec 26 13:09:17 2020 InstallationDate: Installed on 2018-05-09 (962 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LD_PRELOAD= SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-26T13:05:25.187611 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1909372 Title: PS2 mouse stopped working the upgrade before this one, still not working. FIX IT PLS! Status in evince package in Ubuntu: New Bug description: Last upgrade, having the PS2 mouse connected caused Ubuntu 20.04.1 to lock up the computer on a black screen. ASUS Mobo, Quad core AMD, 64-bit; 1 TB WD HDD. Mobo is a circa 2014 so still well within it's life. Withdrawing support for PS2 equipment at this EARLY stage makes us computer owners wonder why as there's no reason to do that this early. They are still making and selling brand new PS2 mice and keyboards! This bug likely applies to PS2 keyboards as well though I didn't test that. This upgrade, first one since Ubuntu stopped supporting PS2 equipmnet a couple three weeks ago (it's 12/26/20 today), it didn't lock up the computer this time so that was fixed, but PS2 mice still don't work!?? Why?? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Dec 26 13:09:17 2020 InstallationDate: Installed on 2018-05-09 (962 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LD_PRELOAD= SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-26T13:05:25.187611 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1909372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
I've had the "Desktop Icons" disabled for a while now, and it doesn't solve the problem but it feels like it is less frequent. It most often happens when I open a new terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 Status in gjs: Unknown Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215 --- A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625
[Desktop-packages] [Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Is there any workaround to this issue? This is a huge productivity killer for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 Status in gjs: Unknown Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215 --- A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II)
Re: [Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
I second that!! This is pathetic. On November 24, 2020 3:58:16 PM EST, BloodyIron <1828...@bugs.launchpad.net> wrote: >I AM STILL GETTING THIS ISSUE TO THIS DAY. WILL THIS EVER BE FIXED? >This >issue was reported over 1.5 YEARS ago and a fix was already made, but >HAS NOT BEEN RELEASED TO UBUNTU 20.04 WHICH IS THE LONG TERM SUPPORT >VERSION. WHEN WILL THIS BE FIXED? > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1828107 > >Title: > gvfs can't list shares from smb servers that disabled SMB1 > >Status in gvfs: > Unknown >Status in gvfs package in Ubuntu: > Triaged > >Bug description: > After bug #1778322 is fixed (just needs a gvfs rebuild with newer > samba), samba machines will start to show up again in the "windows > network" tab in nautilus. But if a server has disabled the SMB1 > protocol, nautilus will show an error when that server is clicked on, > instead of showing the shares list. > > Even with SMB1 disabled, it should still be technically possible to > get a share list, since smbclient can do it: > > andreas@nsnx:~$ nmblookup -A 192.168.122.101 > Looking up status of 192.168.122.101 > D-NO-SMB1 <00> - B > D-NO-SMB1 <03> - B > D-NO-SMB1 <20> - B > ..__MSBROWSE__. <01> - B > WORKGROUP <00> - B > WORKGROUP <1d> - B > WORKGROUP <1e> - B > > MAC Address = 00-00-00-00-00-00 > > andreas@nsnx:~$ smbclient -L 192.168.122.101 -N > WARNING: The "syslog" option is deprecated > > Sharename Type Comment > - --- > print$ Disk Printer Drivers > pub_no_smb1 Disk > IPC$IPC IPC Service (d-no-smb1 server (Samba, >Ubuntu)) > Reconnecting with SMB1 for workgroup listing. > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > Failed to connect with SMB1 -- no workgroup available > >andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U >ubuntu%ubuntu -m NT1 > WARNING: The "syslog" option is deprecated > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > >andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U >ubuntu%ubuntu -m SMB2 > WARNING: The "syslog" option is deprecated > Try "help" to get a list of possible commands. > smb: \> dir >. D0 Fri May 3 18:16:38 >2019 >.. D0 Fri May 3 18:15:24 >2019 >hello.txt N 21 Fri May 3 18:16:12 >2019 >hello-from-nsnx.txt A9 Fri May 3 18:16:38 >2019 > > 20509264 blocks of size 1024. 13121800 blocks > available > >To manage notifications about this bug go to: >https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog"
Re: [Desktop-packages] [Bug 1898389] Re: browser frequently crashing with trap int3
the new version of Chromium seems to be a disaster when I try to go to full screen in YouTube. It scatters parts of the screen amongst my various virtual desktops and creates a huge mess, forcing me to kill chromium from the command line. On Fri, 30 Oct 2020, Olivier Tilloy wrote: > Thanks for the report Gerald, and sorry for the lack of a timely response. > Is this still happening with the latest update available for Ubuntu 16.04 > (version 86.0.4240.75-0ubuntu0.16.04.1)? > > ** Changed in: chromium-browser (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.357674] traps: chromium-browse[24558] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 > sp:7ffdfc316260 error:0 > [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 > sp:7ffdfc31abd0 error:0 > [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be > sp:7ffdfc31bbb0 error:0 > [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 > sp:7ffdfc31d020 error:0 > [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 > sp:7ffdfc3165c0 error:0 > [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 > sp:7ffdfc3164c0 error:0 > [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 > sp:7ffdfc31c5b0 error:0 > [519429.841404] traps: chromium-browse[24906] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions > -- 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/1898389 Title: browser frequently crashing with trap int3 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I used to be able to have many tabs open with Chromium without problems. Lately it crashes or gives "aw snap" errors (see kernel messages below) if I start to keep more than 25 or so open. Description:Ubuntu 16.04.7 LTS Release:16.04 chromium-browser: Installed: 85.0.4183.83-0ubuntu0.16.04.2 Candidate: 85.0.4183.121-0ubuntu0.16.04.1 Version table: 85.0.4183.121-0ubuntu0.16.04.1 500
Re: [Desktop-packages] [Bug 1898389] Re: browser frequently crashing with trap int3
thanks, I will try with the updated version and keep you posted On Fri, 30 Oct 2020, Olivier Tilloy wrote: > Thanks for the report Gerald, and sorry for the lack of a timely response. > Is this still happening with the latest update available for Ubuntu 16.04 > (version 86.0.4240.75-0ubuntu0.16.04.1)? > > ** Changed in: chromium-browser (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.357674] traps: chromium-browse[24558] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 > sp:7ffdfc316260 error:0 > [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 > sp:7ffdfc31abd0 error:0 > [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be > sp:7ffdfc31bbb0 error:0 > [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 > sp:7ffdfc31d020 error:0 > [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 > sp:7ffdfc3165c0 error:0 > [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 > sp:7ffdfc3164c0 error:0 > [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 > sp:7ffdfc31c5b0 error:0 > [519429.841404] traps: chromium-browse[24906] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions > -- 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/1898389 Title: browser frequently crashing with trap int3 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I used to be able to have many tabs open with Chromium without problems. Lately it crashes or gives "aw snap" errors (see kernel messages below) if I start to keep more than 25 or so open. Description:Ubuntu 16.04.7 LTS Release:16.04 chromium-browser: Installed: 85.0.4183.83-0ubuntu0.16.04.2 Candidate: 85.0.4183.121-0ubuntu0.16.04.1 Version table: 85.0.4183.121-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
[Desktop-packages] [Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
This is happening to me a few times every day lately. I do not have any icons on the desktop. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x556612c6552a in dump_gjs_stack_on_signal_handler (signo=5) at ../src/main.c:421 #2 0x7f17472b6210 in () at /lib/x86_64-linux-gnu/libc.so.6 #3 _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 #4 0x7f17480f8159 in g_log_default_handler (log_domain=, log_level=, message=, unused_data=) at ../../../glib/gmessages.c:3123 #5 0x556612c655ee in default_log_handler (log_domain=0x7f1747836e20 "Gjs", log_level=6, message=0x55661bb3aca0 "toggling down object GInotifyFileMonitor that's already queued to toggle up\n", data=0x0) at ../src/main.c:363 #6 0x7f17480f839c in g_logv (log_domain=0x7f1747836e20 "Gjs", log_level=G_LOG_LEVEL_ERROR, format=, args=args@entry=0x7ffc2bb6e820) at ../../../glib/gmessages.c:1350 #7 0x7f17480f8583 in g_log (log_domain=log_domain@entry=0x7f1747836e20 "Gjs", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f174783c308 "toggling down object %s that's already queued to toggle %s\n") at ../../../glib/gmessages.c:1415 #8 0x7f17477e40a7 in wrapped_gobj_toggle_notify(void*, GObject*, gboolean) (gobj=0x556615cd10b0 [GInotifyFileMonitor], is_last_ref=) at ../gi/object.cpp:1274 #9 0x7f17477f7058 in ToggleQueue::handle_toggle(void (*)(_GObject*, ToggleQueue::Direction)) (this=0x7f17478a14a0 , handler=0x7f17477e3f20 ) at ../gi/toggle.cpp:125 #10 0x7f17477f70df in ToggleQueue::idle_handle_toggle(void*) (data=0x7f17478a14a0 ) at ../gi/toggle.cpp:69 #11 0x7f17480f0e8e in g_main_dispatch (context=0x5566149c1350) at ../../../glib/gmain.c:3309 #12 g_main_context_dispatch (context=context@entry=0x5566149c1350) at ../../../glib/gmain.c:3974 #13 0x7f17480f1240 in g_main_context_iterate (context=0x5566149c1350, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4047 #14 0x7f17480f1533 in g_main_loop_run (loop=0x556614e05dc0) at ../../../glib/gmain.c:4241 #15 0x7f174751aaf0 in meta_run () at /lib/x86_64-linux-gnu/libmutter-6.so.0 #16 0x556612c64d7d in main (argc=, argv=) at ../src/main.c:634 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 Status in gjs: Unknown Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva
Re: [Desktop-packages] [Bug 1895217] Re: gnome control center mouse settings don't work in other window manager
yes I know that. I'm talking about gnome-control-center not saving the settings. On Fri, 11 Sep 2020, Daniel van Vugt wrote: > Anything you want run automatically on login, try putting it in a script > called: > > ~/.xsession > > or > > ~/.xinitrc > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1895217 > > Title: > gnome control center mouse settings don't work in other window manager > > Status in gnome-control-center package in Ubuntu: > Invalid > > Bug description: > I would like to use gnome control center from Fvwm window manager. > But the mouse speed does not respond at all to what I set unless I am > running it from the default ubuntu window manager. I tried running > gnome control center using different XDG environment variables as > suggested by some posts, but this had no effect. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895217/+subscriptions > -- 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/1895217 Title: gnome control center mouse settings don't work in other window manager Status in gnome-control-center package in Ubuntu: Invalid Bug description: I would like to use gnome control center from Fvwm window manager. But the mouse speed does not respond at all to what I set unless I am running it from the default ubuntu window manager. I tried running gnome control center using different XDG environment variables as suggested by some posts, but this had no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886336] [NEW] Network Manager permissions issue
Public bug reported:
Description:Ubuntu 20.04 LTS
Release:20.04
network-manager:
Installed: 1.22.10-1ubuntu2.1
Candidate: 1.22.10-1ubuntu2.1
Version table:
*** 1.22.10-1ubuntu2.1 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
100 /var/lib/dpkg/status
1.22.10-1ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
Having recently updated from 19.19 to 20.04, I am now unable to add/edit
any connections. When I try, a dialogue box pops up saying;
"Failed to activate {SSID}
Not authorized to control networking."
I have spent some time trawling the web but no obvious solution was
found, but one post mentioned "nmcli g permissions" which I tried as
user and using sudo.
User output;
PERMISSION VALUE
org.freedesktop.NetworkManager.enable-disable-network no
org.freedesktop.NetworkManager.enable-disable-wifi no
org.freedesktop.NetworkManager.enable-disable-wwan no
org.freedesktop.NetworkManager.enable-disable-wimax no
org.freedesktop.NetworkManager.sleep-wake no
org.freedesktop.NetworkManager.network-control auth
org.freedesktop.NetworkManager.wifi.share.protecte d no
org.freedesktop.NetworkManager.wifi.share.open no
org.freedesktop.NetworkManager.settings.modify.sys tem no
org.freedesktop.NetworkManager.settings.modify.own auth
org.freedesktop.NetworkManager.settings.modify.hos tname auth
org.freedesktop.NetworkManager.settings.modify.glo bal-dns auth
org.freedesktop.NetworkManager.reload auth
org.freedesktop.NetworkManager.checkpoint-rollback auth
org.freedesktop.NetworkManager.enable-disable-statistics no
org.freedesktop.NetworkManager.enable-disable-connectivity-check no
org.freedesktop.NetworkManager.wifi.scan unknown
Sudo output;
org.freedesktop.NetworkManager.enable-disable-network yes
org.freedesktop.NetworkManager.enable-disable-wifi yes
org.freedesktop.NetworkManager.enable-disable-wwan yes
org.freedesktop.NetworkManager.enable-disable-wimax yes
org.freedesktop.NetworkManager.sleep-wake yes
org.freedesktop.NetworkManager.network-control yes
org.freedesktop.NetworkManager.wifi.share.protecte d yes
org.freedesktop.NetworkManager.wifi.share.open yes
org.freedesktop.NetworkManager.settings.modify.sys tem yes
org.freedesktop.NetworkManager.settings.modify.own yes
org.freedesktop.NetworkManager.settings.modify.hos tname yes
org.freedesktop.NetworkManager.settings.modify.glo bal-dns yes
org.freedesktop.NetworkManager.reload yes
org.freedesktop.NetworkManager.checkpoint-rollback yes
org.freedesktop.NetworkManager.enable-disable-statistics yes
org.freedesktop.NetworkManager.enable-disable-connectivity-check yes
org.freedesktop.NetworkManager.wifi.scan unknown
Now it seems to me that I should have more permissions as a user.
I have checked what the User output is when you boot into the live ISO
and it has all the same permissions as the Sudo output shown above. So
my guess would be that this is what myproblem is.
How can I fix these permission issues as a workaround while you
investigate this bug.
Thanks.
Jim!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sun Jul 5 19:07:19 2020
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-10-13 (1361 days ago)
InstallationMedia: It
IpRoute:
default via 192.168.0.2 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.176 metric 600
ProcEnviron:
LANGUAGE=en_GB
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-03-14 (113 days ago)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
[connection]
wifi.powersave = 2
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
2020-01-01T15:53:38.227396
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled disabled
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1886336
Title:
Network Manager permissions issue
Status in network-manager package in Ubuntu:
New
Bug description:
Description:Ubuntu 20.04 LTS
Release:20.04
network-manager:
Installed: 1.22.10-1ubuntu2.1
Candidate: 1.22.10-1ubuntu2.1
Version table:
*** 1.22.10-1ubuntu2
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Same issue, brand new fresh install of Ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in gnome-shell package in Ubuntu: Confirmed Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Just tried upgrading my Xubuntu 19.10 desktop to 20.04 and I'm now getting the same staircase effect. Video card is an AMD Radeon RX 5700 XT which is connected with a DisplayPort -> DVI-D cable to an ancient LG W2252TQ monitor with a resolution of, yes, 1680x1050. It is the only monitor connected. Just thought I'd share. Rolling back to 19.10 now. I'll try again with the point release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW 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:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1873895/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1852679] Re: CLI to copy to clipboard does not work
If this helps... this does not happen with 18.04.3 LTS LSB Release: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic gnome-screenshot version: gnome-screenshot 3.25.0 uname -a: Linux hostname 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1852679 Title: CLI to copy to clipboard does not work Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: I just upgraded today to 19.10. I have a keyboard shortcut setup to run gnome-screenshot --area -c to allow me to do quick screen grabs. I can confirm that if I use the screenshot dialog I can copy to the clipboard with that but using the CLI version of the same function does not work. It looks like it functions normal but when you go to paste the screenshot that you just took, nothing happens. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy gnome-screenshot gnome-screenshot: Installed: 3.33.90-1ubuntu1 Candidate: 3.33.90-1ubuntu1 Version table: *** 3.33.90-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1852679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860230] Re: Resolution incorrect after updating kernel to 5.3
Bug also affects me: VGA compatible controller: NVIDIA Corporation GF106GL [Quadro 2000] (rev a1) I was running dual monitors. After reboot second monitor is not recognized. Primary monitor displays as 'Default'. Only one resolution setting is available I have Driver nvidia-driver-390 (proprietary tested) selected -- 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/1860230 Title: Resolution incorrect after updating kernel to 5.3 Status in xorg package in Ubuntu: Confirmed Bug description: Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be something like 640 x 480. Accessed (with difficulty) display settings. Monitor is shown as unknown device. Tried reinstalling kernel, problem remains. Can still boot successfully into previous kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 18:56:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2710] InstallationDate: Installed on 2018-08-02 (533 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b6d36306-de29-4163-9a21-ced3e7dfe6dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr: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. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.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/+source/xorg/+bug/1860230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
I found this thread via Google, trying to fix the Bluetooth pairing of my Bose QC35 (version 1) running Ubuntu 16.0.4.6 on a ThinkPad X230. Whilst trying out a few things I managed to solve my problem by temporarily disabling my VPN. Might have been a random coincidence but I wanted to leave this here in case it helped others. Worth a try anyway :) -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Yakkety: Fix Released Bug description: Impact: A patch we carry for Ubuntu touch introduced a change that originally was required to make sure PulseAudio did not crash. This patch was ported to PulseAudio 8 in Xenial, but the patch author's bluetooth hardware that was to hand at the time worked so was assumed to be ok. However, the opposite is now happening, i.e PulseAudio is crashing with a subset of Bluetooth hardware. Regression potential: Very low to none. As can be read in this report, much debugging and testing has been done to find the problem, and the eventual fix. Moreover the change is the removal of a patch hunk that removed a line of code originally present in PulseAudio. Test case: NOTE that this test case applies to bluetooth hardware that is identified as not working in this bug report. 1. Install, or upgrade to Xenial or yakkety. 2. Pair your bluetooth device in the bluetooth settings in the relevant settings application for your desktop environment. 3. Once paired, you will notice that sound stops working, as pulseaudio has thrown an assertion error. 4. You do not have to remove your audio device from the paired device list, but it may be easier to do so for the next part of the testing. 5. Update to the version of PulseAudio in xenial-proposed which is 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1. 6. Re-pair your device. Audio should continue to work, and you should be able to switch to your bluetooth device and use it. Original bug report: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840726] Re: Write files to a CD or DVD does not mention how to install Brasero
Nothing happens, no notification popups. Maybe its just my external usb dvd burner, but autoplay doesn't seem to. Even if i go to: settings -> devices -> removable media -> other media -> blank dvd disc The default action is "CD/DVD Creator", but changing it to Brasero doesn't automatically start it when i insert an empty dvd. So now i'm not sure if "CD/DVD Creator" is a different program than "Brasero", and maybe a default install does include it. (i did a minimum install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1840726 Title: Write files to a CD or DVD does not mention how to install Brasero Status in gnome-user-docs package in Ubuntu: Incomplete Bug description: On https://help.ubuntu.com/stable/ubuntu-help/files-disc-write.html.en there are instructions how to write a CD/DVD, but it does not mention that you need to install Brasero to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1840726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
For reference, I also see this same issue with Firefox set as my default browser, and I am using the snap version of Slack. -- 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/1766230 Title: Strange window matching behaviour between Slack and Chrome Status in gnome-shell package in Ubuntu: Confirmed Bug description: There seems to be a window matching bug between the Slack snap and Chrome. If you open a URL from within Slack without Chrome open, then the launcher shows the extra pip next to Slack and doesn't add a Chrome icon to the launcher. If you open Chrome first, then things work as expected. Steps to reproduce 1. Install Slack snap and Chrome deb. 2. Join a Slack channel and open a hyperlink. Notice the extra pip next to Slack in the launcher. 3. Close Chrome and reopen it. 4. Open a URL from Slack again and notice the Chrome icon get added to the launcher. I'm not sure if this is an Ubuntu Dock or GNOME Shell issue. EDIT: Spoke to didrocks, he says that matching is done by Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
Seeing this behavior, as well. Others reference vscode (in the comment above), so I am curious to know if this is related to electron, or if this is a snap-specific issue. I do see reference to it as a snap-specific issue here: https://forum.snapcraft.io/t/slack-opening-file-browser-firefox-and- chrome-in-the-snaps-context/8969/3 -- 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/1766230 Title: Strange window matching behaviour between Slack and Chrome Status in gnome-shell package in Ubuntu: Confirmed Bug description: There seems to be a window matching bug between the Slack snap and Chrome. If you open a URL from within Slack without Chrome open, then the launcher shows the extra pip next to Slack and doesn't add a Chrome icon to the launcher. If you open Chrome first, then things work as expected. Steps to reproduce 1. Install Slack snap and Chrome deb. 2. Join a Slack channel and open a hyperlink. Notice the extra pip next to Slack in the launcher. 3. Close Chrome and reopen it. 4. Open a URL from Slack again and notice the Chrome icon get added to the launcher. I'm not sure if this is an Ubuntu Dock or GNOME Shell issue. EDIT: Spoke to didrocks, he says that matching is done by Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837821] Re: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Looks like the same issue I'm having on Thinkpad X1 Carbon 7th Gen running Ubuntu 19.04. Debug output here: http://alsa-project.org/db/?f=5c09dfb7b0fc0ff5ad32c0576893316f5613d3a1 As well as the Mic not being detected, and therefore not available for use in any applications, there is an issue with the master audio volume being either full-on or muted. individual mixer controls still work, but the main volume control does nothing other than mute the audio. -- 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/1837821 Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.04.2 LTS. The built in microphone is not displayed and not available to select. The webcam, touchscreen, and speakers all work fine. Plugging in a headset with a microphone does allow audio to be heard through the external microphone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carwyn 2521 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 20:57:51 2019 InstallationDate: Installed on 2019-07-22 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2019 dmi.bios.vendor: AMI dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8518 dmi.board.vendor: HP dmi.board.version: 10.47 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.29:bd04/22/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8518:rvr10.47:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.product.sku: 6JY95UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1837821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822258] [NEW] package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet
Public bug reported: unable to use my fingerprint ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libfprint-dev (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 AptOrdering: aes2501-wy:amd64: Install libfprint-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 29 08:48:45 2019 ErrorMessage: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: libfprint Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1822258 Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 Status in libfprint package in Ubuntu: New Bug description: unable to use my fingerprint ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libfprint-dev (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 AptOrdering: aes2501-wy:amd64: Install libfprint-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 29 08:48:45 2019 ErrorMessage: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: libfprint Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1822258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"
I see this error in 18.04. The error recommends I try running a command $ InstrumentationBrowser (InstrumentationBrowser:24156): GdkPixbuf-WARNING **: 15:24:47.916: Cannot open pixbuf loader module file '/usr/lib64/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. $ sudo gdk-pixbuf-query-loaders > /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache: No such file or directory $ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1282294 Title: "Cannot open pixbuf loader module file" Status in gdk-pixbuf package in Ubuntu: Triaged Status in gdk-pixbuf package in Debian: New Bug description: While doing testing on trusty, I keep finding errors like the following in my apt-get -u dist-upgrade output: Preparing to unpack .../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ... Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over (0.1.7daily13.03.01-0ubuntu1) ... (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. These errors make it difficult to look for errors that I might have introduced in my own packages and if they persist in our final product will make users wonder what is broken and why it is broken. sarnold@sec-trusty-amd64:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders libgdk-pixbuf2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0: Installed: 2.30.5-0ubuntu1 Candidate: 2.30.5-0ubuntu1 Version table: *** 2.30.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0 libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0 sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin libgtk-3-bin: Installed: 3.10.7-0ubuntu2 Candidate: 3.10.7-0ubuntu2 Version table: *** 3.10.7-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-bin 3.10.7-0ubuntu2 ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Wed Feb 19 14:38:47 2014 InstallationDate: Installed on 2014-01-09 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108) ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 940631]
Running 60.5.0 on Windows 10, no longer have this problem
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/940631
Title:
Thunderbird asks three times for my master password
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
When Thunderbird is launched it asks for the master password three
times in a row. Only one password prompt needs to be completed. The
remaining prompts can be dismissed with the escape key.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: thunderbird 10.0.2+build1-0ubuntu0.11.10.1
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pierre 1609 F pulseaudio
pierre 1636 F xfce4-volumed
BuildID: 20120216123548
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5044 irq 43'
Mixer name : 'SigmaTel STAC9221 A1'
Components : 'HDA:83847680,106b2200,00103401'
Controls : 21
Simple ctrls : 13
Channel: release
Date: Fri Feb 24 22:18:53 2012
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions:
Timezone Definitions for Mozilla Calendar -
ID=calendar-timezo...@mozilla.org, Version=1.2011n, minVersion=2.0,
maxVersion=10.0, Location=app-system-share, Type=extension, Active=Yes
Provider for Google Calendar - ID={a62ef8ec-5fdc-40c2-873c-223b8a6925cc},
Version=0.11, minVersion=8.0a1, maxVersion=10.0, Location=app-system-share,
Type=extension, Active=Yes
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.10 metric
2
Profiles: Profile0 (Default) - LastVersion=10.0.2/20120216123548 (Running)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB21.88Z.00A5.B07.0706270922
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4208CAA
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4208CAA
dmi.modalias:
dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA:
dmi.product.name: MacBook2,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/940631/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800398] Re: login password not showing
** Description changed: 6 year old HP laptop with A6 processor. Loaded Xubuntu 18.10 then MATE 18.10. I saved a login password but it did not show in the keyring when I looked. I did not check any other parts of Seahorse since I don't plan to use encryption. Reloaded MATE 18.04 and it works fine there. #327481 did not seem to let me re-open that issue from 2010 so reporting again. + + Found that I can overcome problem by changing the View for Show Personal + to Show Any. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1800398 Title: login password not showing Status in seahorse package in Ubuntu: Confirmed Bug description: 6 year old HP laptop with A6 processor. Loaded Xubuntu 18.10 then MATE 18.10. I saved a login password but it did not show in the keyring when I looked. I did not check any other parts of Seahorse since I don't plan to use encryption. Reloaded MATE 18.04 and it works fine there. #327481 did not seem to let me re-open that issue from 2010 so reporting again. Found that I can overcome problem by changing the View for Show Personal to Show Any. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1800398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
FWIW, we have the patch for Trusty, and I can test it, but I know that Trusty will reach EOL in less than four months. I will leave it at your discretion as to whether to go forward with the update for Trusty. Also, I thanked Brian for getting the Xenial update into Proposed, but forgot to thank Sebastian for his help, too. Thanks to both. : ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Fix Committed Status in ubuntu-geoip source package in Artful: Won't Fix Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - 1) Install patches / patched package 2) Confirm that the 'geoip url' is set to a correct 'https' value, and that this value is set as the default: `$ gsettings get com.ubuntu.geoip geoip-url` should display `https://geoip.ubuntu.com/lookup` `$ gsettings reset com.ubuntu.geoip geoip-url && gsettings get com.ubuntu.geoip geoip-url` should continue to display `https://geoip.ubuntu.com/lookup` (this will confirm that the `https` value is set as the default. 3) Confirm that the the correct location is being retrieved by the Ubuntu geoip service: apt install geoclue-examples and then geoclue-test-gui . . . should show correct location information. Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
$ apt-cache policy geoclue-ubuntu-geoip geoclue-ubuntu-geoip: Installed: 1.0.2+14.04.20131125-0ubuntu2.16.04.1 Candidate: 1.0.2+14.04.20131125-0ubuntu2.16.04.1 Test #1 - Passed - URL includes https on first check $ gsettings get com.ubuntu.geoip geoip-url 'https://geoip.ubuntu.com/lookup' Test #2 - Passed - Reset the gsettings key & the URL value still includes https $ gsettings reset com.ubuntu.geoip geoip-url && gsettings get com.ubuntu.geoip geoip-url 'https://geoip.ubuntu.com/lookup' Test #3 - Passed - geoclue-examples application shows my correct location information -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Fix Committed Status in ubuntu-geoip source package in Artful: Won't Fix Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - 1) Install patches / patched package 2) Confirm that the 'geoip url' is set to a correct 'https' value, and that this value is set as the default: `$ gsettings get com.ubuntu.geoip geoip-url` should display `https://geoip.ubuntu.com/lookup` `$ gsettings reset com.ubuntu.geoip geoip-url && gsettings get com.ubuntu.geoip geoip-url` should continue to display `https://geoip.ubuntu.com/lookup` (this will confirm that the `https` value is set as the default. 3) Confirm that the the correct location is being retrieved by the Ubuntu geoip service: apt install geoclue-examples and then geoclue-test-gui . . . should show correct location information. Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Hi All - I can test this on Xenial tomorrow (Jan 23). I'll report back after testing. Thanks to Brian for getting the package into xenial-proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Fix Committed Status in ubuntu-geoip source package in Artful: Won't Fix Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - 1) Install patches / patched package 2) Confirm that the 'geoip url' is set to a correct 'https' value, and that this value is set as the default: `$ gsettings get com.ubuntu.geoip geoip-url` should display `https://geoip.ubuntu.com/lookup` `$ gsettings reset com.ubuntu.geoip geoip-url && gsettings get com.ubuntu.geoip geoip-url` should continue to display `https://geoip.ubuntu.com/lookup` (this will confirm that the `https` value is set as the default. 3) Confirm that the the correct location is being retrieved by the Ubuntu geoip service: apt install geoclue-examples and then geoclue-test-gui . . . should show correct location information. Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809614] [NEW] Lubuntu 18.04 ICS not working
Public bug reported: Description:Ubuntu 18.04.1 LTS Release:18.04 network-manager: Installed: 1.10.6-2ubuntu1.1 Candidate: 1.10.6-2ubuntu1.1 Version table: *** 1.10.6-2ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ICS does NOT work. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1809614 Title: Lubuntu 18.04 ICS not working Status in network-manager package in Ubuntu: New Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.1 Candidate: 1.10.6-2ubuntu1.1 Version table: *** 1.10.6-2ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ICS does NOT work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800294] Re: Xorg freeze black screen hang up
I followed the instructions at https://forums.virtualbox.org/viewtopic.php?f=3=87526#p418088 where I disabled "Wayland in /etc/gdm3/custom.conf by uncommenting 'WaylandEnable = False'." This seems to work around the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1800294 Title: Xorg freeze black screen hang up Status in xorg-server package in Ubuntu: Incomplete Bug description: i've had this issue twice this morning where during boot up my screen turns black and i can't get it to come back, then i'm forced to to a hard reboot, this issue often times happens about 99% of the time at the login screen if i don't log in with in about 10 seconds, my screen goes black and i can not get it to come back and i need to do a hard reboot. also sometimes the issue happens during boot up the screen goes purple for a few seconds then black and stay's like that and the can't get it to comes back and have to do a hard reboot, but this happens about 1 or 2 times out of ten boots i would say. so i'm hoping that this issue can be resolved in some way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 12:40:06 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7620G] [103c:808d] InstallationDate: Installed on 2018-10-27 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=45d6254a-e97a-4d45-b9a9-37afad8da3df ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 808D dmi.board.vendor: Hewlett-Packard dmi.board.version: 90.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096C120800405F0620180:rvnHewlett-Packard:rn808D:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 096C120800405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800294] Re: Xorg freeze black screen hang up
I am still running into this issue under Bionic Beaver running within VirtualBox. The system is functioning, but UI is frozen. There are no files within the /var/crash directory for me to submit. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1800294 Title: Xorg freeze black screen hang up Status in xorg-server package in Ubuntu: Incomplete Bug description: i've had this issue twice this morning where during boot up my screen turns black and i can't get it to come back, then i'm forced to to a hard reboot, this issue often times happens about 99% of the time at the login screen if i don't log in with in about 10 seconds, my screen goes black and i can not get it to come back and i need to do a hard reboot. also sometimes the issue happens during boot up the screen goes purple for a few seconds then black and stay's like that and the can't get it to comes back and have to do a hard reboot, but this happens about 1 or 2 times out of ten boots i would say. so i'm hoping that this issue can be resolved in some way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 12:40:06 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7620G] [103c:808d] InstallationDate: Installed on 2018-10-27 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=45d6254a-e97a-4d45-b9a9-37afad8da3df ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 808D dmi.board.vendor: Hewlett-Packard dmi.board.version: 90.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096C120800405F0620180:rvnHewlett-Packard:rn808D:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 096C120800405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
The patch to resolve this bug was just accepted to upstream gnome-shell master: see https - gitlab.gnome dot org/GNOME/gnome- shell/merge_requests/140 (For some reason launchpad is not letting me submit a comment with a URL). Might it be possible to back-port this patch to GNOME Shell 3.28 for Bionic? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
I've added a similar comment / request on this related launchpad bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794655] Re: Firefox: Modal dialogs with password fields instantly hide.
The patch to resolve this bug was just accepted to upstream gnome-shell master: see https - gitlab.gnome dot org/GNOME/gnome- shell/merge_requests/140 (For some reason launchpad is not letting me submit a comment with a URL). Might it be possible to back-port this patch to GNOME Shell 3.28 for Bionic? -- 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/1794655 Title: Firefox: Modal dialogs with password fields instantly hide. Status in gnome-shell package in Ubuntu: Triaged Bug description: When I use Bitwarden extension by clicking on the icon, the popup immediately hides. See [1], although further digging suggest the bug was/in iBus, see [2] and [3]. Although, the source (or code path) originates from Gnome-Shell, see [4] and [5]. There is a propose fixed but it hasn't been merged. I'm reporting the issue here, so it can at least be tracked and I can get notified when it arrives in Ubuntu. Note: This issue affects all extensions that uses 'password field', see [6]. Firefox-Version: 62.0 Dist-Version: Ubuntu 18.04.1 LTS Gnome-Shell-Version: 3.28.3-0ubuntu0.18.04.2 iBus-Version: 1.5.17-3ubuntu4 1. https://github.com/bitwarden/browser/issues/694 2. https://bugzilla.mozilla.org/show_bug.cgi?id=1405634#c16 3. https://github.com/ibus/ibus/issues/2002#issuecomment-386537208 4. https://github.com/ibus/ibus/issues/2002#issuecomment-402596959 5. https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 6. https://github.com/MetaMask/metamask-extension/issues/3313#issuecomment-418677844 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801524] [NEW] package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2
Public bug reported: Got this error message while software updater was installing downloaded packages. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Sat Nov 3 14:08:16 2018 DuplicateSignature: package:gnome-user-guide:3.8.2-1:symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2 ErrorMessage: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2 InstallationDate: Installed on 2014-12-02 (1431 days ago) InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.18 SourcePackage: gnome-user-docs Title: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2 UpgradeStatus: Upgraded to trusty on 2015-12-20 (1048 days ago) ** Affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1801524 Title: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2 Status in gnome-user-docs package in Ubuntu: New Bug description: Got this error message while software updater was installing downloaded packages. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Sat Nov 3 14:08:16 2018 DuplicateSignature: package:gnome-user-guide:3.8.2-1:symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2 ErrorMessage: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2 InstallationDate: Installed on 2014-12-02 (1431 days ago) InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.18 SourcePackage: gnome-user-docs Title: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2 UpgradeStatus: Upgraded to trusty on 2015-12-20 (1048 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1801524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800398] [NEW] login password not showing
Public bug reported: 6 year old HP laptop with A6 processor. Loaded Xubuntu 18.10 then MATE 18.10. I saved a login password but it did not show in the keyring when I looked. I did not check any other parts of Seahorse since I don't plan to use encryption. Reloaded MATE 18.04 and it works fine there. #327481 did not seem to let me re-open that issue from 2010 so reporting again. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1800398 Title: login password not showing Status in seahorse package in Ubuntu: New Bug description: 6 year old HP laptop with A6 processor. Loaded Xubuntu 18.10 then MATE 18.10. I saved a login password but it did not show in the keyring when I looked. I did not check any other parts of Seahorse since I don't plan to use encryption. Reloaded MATE 18.04 and it works fine there. #327481 did not seem to let me re-open that issue from 2010 so reporting again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1800398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755023] Re: Restore ignores what I type into the folder box
I have exactly the same problem, on a clean install of Bionic/18.04 Desktop AMD64, with a locally-attached (USB) 2TB SATA hard drive which works perfectly AFAIK for all functions other than Deja Dup. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1755023 Title: Restore ignores what I type into the folder box Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Bug description: I have my computer using Deja Dup to backup everything to a particular folder on a secondary drive. When I try to use Deja Dup to restore a backup from a different folder on that drive, it does not scan that folder. 1. Open Deja Dup and click the Restore... button. 2. In the Restore From Where? window, the Backup location is set to my external hard drive, and the Folder field is set to my current backup folder. From here, I try paths "a" and "b" below: 3a. Change the text in the Folder field to be the name of the folder containing my previous computer's backup, and click Forward. 4a. I am presented with a list of backups from my current backup folder, not from the other folder I tried to select. 3b. Change the Backup location field to Local Folder, and now click the Choose Folder... button that has appeared next to the Folder field. 4b. Browse to the mount point of my secondary drive, and select the backup folder that was used for my previous computer. Click OK, and then Forward. 5b. I am presented with the message "Restore Failed" "No backups to restore" I'm on Ubuntu 17.10 with deja-dup 36.3-0ubuntu0.1 and duplicity 0.7.12-1ubuntu1 I have attached deja-dup.gsettings to this bug report. I will add debug outputs in comments below. In those logs, it should be noted that my secondary drive is named "Octonary" and is mounted at "/media/paul/Octonary". My current backup folder is "/media/paul/Octonary/Ubuntu Backup 3", and the backup folder of my previous computer is "/media/paul/Octonary/Ubuntu Backup 2". To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1755023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
** Changed in: lightdm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in lightdm package in Ubuntu: Fix Released Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes "/usr/sbin/lightdm- session: 5: exec: init: not found" - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to "init" in the .xsession-errors. First of them is "init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory" .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
s/metter/better/!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
I've encountered this bug on the past TWO kernel updates of my Xubuntu 16.04.4 (now .5) system that uses an Nvidia card. Initially I found that falling back to the previous kernel was a satisfactory workaround. This morning, I tried using the "Additional drivers" system setting to change from the Nvidia driver to the noveau driver -- and that has worked perfectly so far. This might be a possible recommended solution. I had originally switched from noveau to the proprietary driver because noveau didn't work properly, but that was several years ago and it has obviously gotten much metter! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772056] Re: Snap Store Authentication always fails
Sorry, forgot to mention, this is on a brand new install of Ubuntu 18.04. Using I3 as window manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1772056 Title: Snap Store Authentication always fails Status in gnome-software package in Ubuntu: New Bug description: Trying to install "Visual Studio Code" get a dialog to Authenticate: "To continue you need to sign in to Snap Store." I have tried an old login, reset passsword, no luck. Registered new user, same deal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1772056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772056] [NEW] Snap Store Authentication always fails
Public bug reported: Trying to install "Visual Studio Code" get a dialog to Authenticate: "To continue you need to sign in to Snap Store." I have tried an old login, reset passsword, no luck. Registered new user, same deal. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2018-05-18 08-43-09.png" https://bugs.launchpad.net/bugs/1772056/+attachment/5141286/+files/Screenshot%20from%202018-05-18%2008-43-09.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1772056 Title: Snap Store Authentication always fails Status in gnome-software package in Ubuntu: New Bug description: Trying to install "Visual Studio Code" get a dialog to Authenticate: "To continue you need to sign in to Snap Store." I have tried an old login, reset passsword, no luck. Registered new user, same deal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1772056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771661] [NEW] After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome
Public bug reported: I recently updated to Ubuntu 18.04. After updating I can only log into Gnome if I select Gnome or Ubuntu with Wayland at my login screen. Nothing I can do will allow me tuse Xorg. I tried reinstalling Xorg and reinstalling my video driver (nvidia-390) . If I select Ubuntu with Xorg at login I get a purple screen and frozen mouse. If I set etting |WaylandEnable=false| in |/etc/gdm/custom.conf| I cannot get to the login screen. The system freezes. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1771661 Title: After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome Status in gdm3 package in Ubuntu: New Bug description: I recently updated to Ubuntu 18.04. After updating I can only log into Gnome if I select Gnome or Ubuntu with Wayland at my login screen. Nothing I can do will allow me tuse Xorg. I tried reinstalling Xorg and reinstalling my video driver (nvidia-390) . If I select Ubuntu with Xorg at login I get a purple screen and frozen mouse. If I set etting |WaylandEnable=false| in |/etc/gdm/custom.conf| I cannot get to the login screen. The system freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Might anyone be able to clarify what kinds of additional test cases (if any) are needed? If so, I would appreciate it. I'm making an attempt to be helpful in fixing this bug, but am a bit new to Canonical's internal processes in terms of what they expect to test / resolve these kinds of bugs. Any additional info / resources would be helpful. Thanks, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Triaged Status in ubuntu-geoip source package in Artful: Triaged Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor
These pages suggest it is intentional: http://gregcor.com/2011/05/07/fix-dual-monitors-in-gnome-3-aka-my-workspaces-are-broken/ https://elementaryos.stackexchange.com/questions/2732/workspaces-seem-to-only-apply-to-the-primary-display-is-this-a-feature-or-a-bug It is certainly frustrating. I had expected independent workspace control on each monitor. ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor Status in gnome-shell package in Ubuntu: Invalid Bug description: After connecting an external monitor to the laptop: - the 4 workspaces that I could access using keyboard shortcuts seem to have been reduced to only 2 - the 'workspace' does not appear to be changeable on the external (secondary) monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 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: Sat Apr 28 12:42:28 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/1767564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767564] [NEW] Ubuntu 18.04 Workspaces only change on primary monitor
Public bug reported: After connecting an external monitor to the laptop: - the 4 workspaces that I could access using keyboard shortcuts seem to have been reduced to only 2 - the 'workspace' does not appear to be changeable on the external (secondary) monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 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: Sat Apr 28 12:42:28 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic workspaces -- 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/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor Status in gnome-shell package in Ubuntu: New Bug description: After connecting an external monitor to the laptop: - the 4 workspaces that I could access using keyboard shortcuts seem to have been reduced to only 2 - the 'workspace' does not appear to be changeable on the external (secondary) monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 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: Sat Apr 28 12:42:28 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/1767564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1753263] Re: GNOME Power Statistics shows nothing on Ubuntu 18.04
On a Dell XPS 13 laptop, Power Statistics does show the AC adapter and Laptop battery status, but the Processor statistics has the same error as above: Processor wakeups per second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1753263 Title: GNOME Power Statistics shows nothing on Ubuntu 18.04 Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: GNOME Power Statistics shows nothing on Ubuntu 18.04, just the "cannot enable timerstats" error. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1753263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Adding test case here: 1) Install patches / patched package 2) Confirm that the 'geoip url' is set to a correct 'https' value, and that this value is set as the default: `$ gsettings get com.ubuntu.geoip geoip-url` should display `https://geoip.ubuntu.com/lookup` `$ gsettings reset com.ubuntu.geoip geoip-url && gsettings get com.ubuntu.geoip geoip-url` should continue to display `https://geoip.ubuntu.com/lookup` (this will confirm that the `https` value is set as the default. 3) Confirm that the the correct location is being retrieved by the Ubuntu geoip service: apt install geoclue-examples and then geoclue-test-gui . . . should show correct location information. If additional test cases / test case information is needed, please let me know. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Triaged Status in ubuntu-geoip source package in Artful: Triaged Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Include associated patch to fix this for Trusty. Please update package after associated packages for Artful and Xenial. ** Patch added: "One-line fix and associated changelog - Trusty" https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachment/5081722/+files/ubuntu_geoip_url_https_trusty.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Triaged Status in ubuntu-geoip source package in Artful: Triaged Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Include patch to set https geoip url for Xenial. Package should be updated after the related Artful package, but before the associated Trusty package. ** Patch added: "One-line fix and associated changelog - Xenial" https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachment/5081721/+files/ubuntu_geoip_url_https_xenial.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Triaged Status in ubuntu-geoip source package in Artful: Triaged Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Include associated patch for Artful. This package should be updated before packages for Trusty and Xenial, although I'm attaching all three patches at more or less the same time. ** Patch added: "One-line fix and associated changelog" https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachment/5081720/+files/ubuntu_geoip_url_https_artful.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Triaged Status in ubuntu-geoip source package in Artful: Triaged Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
It appears as though the servers may have been updated to also serve this over https (previously, https didn't work at the Ubuntu geoip url), but the default value for desktops is to use the http value, and the defaults should be updated Current values: $ gsettings reset com.ubuntu.geoip geoip-url $ gsettings get com.ubuntu.geoip geoip-url 'http://geoip.ubuntu.com/lookup' Should show: $ gsettings reset com.ubuntu.geoip geoip-url $ gsettings get com.ubuntu.geoip geoip-url 'https://geoip.ubuntu.com/lookup' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Committed Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Triaged Status in ubuntu-geoip source package in Artful: Triaged Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726143] Re: Automatic installation of samba fails with "could not find package libpam-smbpass"
I'm getting this too. Just saw this post while looking to see if this has been fixed or if anyone has any work-arounds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1726143 Title: Automatic installation of samba fails with "could not find package libpam-smbpass" Status in nautilus-share package in Ubuntu: Confirmed Bug description: I actually have no idea if this is really a Nautilus issue but didn't know where else to file it. I have a fresh install of ubuntu 17.10. I start nautilus (using File). I right-click on a folder and select "Local Network Share". When I select "Share this folder" it says the sharing service is not installed, so I select "Install Service" and it offers to install samba for me. I click "install" and it proceeds, then throws up an error dialog: Could not find package 'libpam-smbpass' I can see that Samba packages are already installed at this point. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:43:28 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1726143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Using the: $ gsettings set com.ubuntu.geoip geoip-url https://freegeoip.net/xml/ Appears to work well enough after initial testing. 1) $ gsettings set com.canonical.indicator.datetime show-auto-detected-location true shows my correct location 2) apt install geoclue-examples and then geoclue-test-gui . . . seems to show correct information, as well. The freegeoip service appears to be well-maintained. Perhaps this is a service that canonical / ubuntu could move to / could support, as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Confirmed Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
To reset the value to the ubuntu default: gsettings reset com.ubuntu.geoip geoip-url -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Confirmed Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
You can update to an alternate provider via: gsettings set com.ubuntu.geoip geoip-url https://freegeoip.net/xml/ and verify the setting via: gsettings get com.ubuntu.geoip geoip-url but I have not done extensive testing to see if this breaks anything. Assistance on this would be appreciated. You can either use the freegeoip service or use its code to host an instance yourself. I do not mean to vouch for their service in any way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Confirmed Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728435] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: Error occurred while upgrading Ubuntu 16.04 to 17.10. Other errors occurred during the process. System appears to be working normally after upgrade. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Oct 29 12:57:51 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-10-19 (375 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-10-29 (0 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1728435 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: Error occurred while upgrading Ubuntu 16.04 to 17.10. Other errors occurred during the process. System appears to be working normally after upgrade. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Oct 29 12:57:51 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-10-19 (375 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-10-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1728435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key
I finally got the evemu program to work, same results as above. Now that I know what module, there are lot of other reports. Looks like a longterm fix is coming from upstream. Sorry for the dupe, but thanks for helping track it down and workaround. -- 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/1722298 Title: keyboard autorepeat not happening when I hold down any key Status in gnome-terminal package in Ubuntu: Confirmed Bug description: The failure to auto repeat happens in all terminal apps I've tried in Artful. If I open a virtual console, it looks like a phantom is typing ^@ about once per second. This prevents successfully typing a password, and is probably what is breaking autorepeat in the GUI terminals, although they don't show the ^@. Gnome terminal and guake also can't stay scrolled up in the buffer for more than a second before popping back down to the bottom. This problem happens in the Ubuntu desktop or Gnome and it doesn't matter if I pick the xorg or default Wayland options. It happens under both the open source and proprietary nvidia drivers. It also happens with a newly created user with no home directory baggage. xev reports a constant stream of the following about the same frequency as the ^@ in console: KeyPress event, serial 62, synthetic NO, window 0x381, root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501), state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False If I boot into a recovery shell, the problem does _not_ appear. My system was built with a fresh install of 17.04, installed my usual packages, then upgrade to 17.10 when the problem began. I'm certain it was not present in 17.04 for the few days before I upgraded. There were similar bugs reported a decade ago, but didn't help me. Expectation: Hold down any key in terminal window. After a moment, the letter should repeat until key is released. Actually: Key will repeat 0 or a few times, but stop repeating before I release the key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 9 10:43:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key
I wanted to open this while my PC was still in an "upgraded" state, but I just did a clean install of 17.10 with today's daily image and the problem persists as reported. I can even reproduce it booting off the the install media and clicking the Try Ubuntu option. Any advice on narrowing it down is welcome. -- 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/1722298 Title: keyboard autorepeat not happening when I hold down any key Status in gnome-terminal package in Ubuntu: New Bug description: The failure to auto repeat happens in all terminal apps I've tried in Artful. If I open a virtual console, it looks like a phantom is typing ^@ about once per second. This prevents successfully typing a password, and is probably what is breaking autorepeat in the GUI terminals, although they don't show the ^@. Gnome terminal and guake also can't stay scrolled up in the buffer for more than a second before popping back down to the bottom. This problem happens in the Ubuntu desktop or Gnome and it doesn't matter if I pick the xorg or default Wayland options. It happens under both the open source and proprietary nvidia drivers. It also happens with a newly created user with no home directory baggage. xev reports a constant stream of the following about the same frequency as the ^@ in console: KeyPress event, serial 62, synthetic NO, window 0x381, root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501), state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False If I boot into a recovery shell, the problem does _not_ appear. My system was built with a fresh install of 17.04, installed my usual packages, then upgrade to 17.10 when the problem began. I'm certain it was not present in 17.04 for the few days before I upgraded. There were similar bugs reported a decade ago, but didn't help me. Expectation: Hold down any key in terminal window. After a moment, the letter should repeat until key is released. Actually: Key will repeat 0 or a few times, but stop repeating before I release the key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 9 10:43:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722298] [NEW] keyboard autorepeat not happening when I hold down any key
Public bug reported: The failure to auto repeat happens in all terminal apps I've tried in Artful. If I open a virtual console, it looks like a phantom is typing ^@ about once per second. This prevents successfully typing a password, and is probably what is breaking autorepeat in the GUI terminals, although they don't show the ^@. Gnome terminal and guake also can't stay scrolled up in the buffer for more than a second before popping back down to the bottom. This problem happens in the Ubuntu desktop or Gnome and it doesn't matter if I pick the xorg or default Wayland options. It happens under both the open source and proprietary nvidia drivers. It also happens with a newly created user with no home directory baggage. xev reports a constant stream of the following about the same frequency as the ^@ in console: KeyPress event, serial 62, synthetic NO, window 0x381, root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501), state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False If I boot into a recovery shell, the problem does _not_ appear. My system was built with a fresh install of 17.04, installed my usual packages, then upgrade to 17.10 when the problem began. I'm certain it was not present in 17.04 for the few days before I upgraded. There were similar bugs reported a decade ago, but didn't help me. Expectation: Hold down any key in terminal window. After a moment, the letter should repeat until key is released. Actually: Key will repeat 0 or a few times, but stop repeating before I release the key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 9 10:43:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1722298 Title: keyboard autorepeat not happening when I hold down any key Status in gnome-terminal package in Ubuntu: New Bug description: The failure to auto repeat happens in all terminal apps I've tried in Artful. If I open a virtual console, it looks like a phantom is typing ^@ about once per second. This prevents successfully typing a password, and is probably what is breaking autorepeat in the GUI terminals, although they don't show the ^@. Gnome terminal and guake also can't stay scrolled up in the buffer for more than a second before popping back down to the bottom. This problem happens in the Ubuntu desktop or Gnome and it doesn't matter if I pick the xorg or default Wayland options. It happens under both the open source and proprietary nvidia drivers. It also happens with a newly created user with no home directory baggage. xev reports a constant stream of the following about the same frequency as the ^@ in console: KeyPress event, serial 62, synthetic NO, window 0x381, root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501), state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False If I boot into a recovery shell, the problem does _not_ appear. My system was built with a fresh install of 17.04, installed my usual packages, then upgrade to 17.10 when the problem began. I'm certain it was not present in 17.04 for the few days before I upgraded. There were similar bugs reported a decade ago, but didn't help me. Expectation: Hold down any key in terminal window. After a moment, the letter should repeat until key is released. Actually: Key will repeat 0 or a few times, but stop repeating before I release the key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 9 10:43:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Any update to this bug? Seems that it would be adviseable to make the change to https for any services possible. The less unencrypted traffic over the web, the better. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Incomplete Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 608162] Re: GNOME Keyring Daemon stops panel's shutdown
This same problem just popped up in the last few days after updating to Mint 18.2 -- 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/608162 Title: GNOME Keyring Daemon stops panel's shutdown Status in gnome-keyring package in Ubuntu: Invalid Bug description: Binary package hint: gnome-keyring Almost every time I click "Shut Down" from the panel's menu for it, I get an error that says: "GNOME-Keyring-Daemon is not responding." Then I can choose "Shut Down anyway" and the computer usually turns off after that, but sometimes I need to use a sudo shutdown command. Also, sometimes when I select "Shut Down" from the panel, nothing happens at all. Again, I need to use a sudo shutdown command to turn off the computer. This happens for all of the users on this computer (a Thinkpad laptop). This issue is particularly annoying for non-administrator users, because if selecting "Shut Down" from the panel doesn't work they cannot issue a sudo shutdown command - which means I need to assist them in changing to a tty terminal, logging in as me, and then giving the sudo shutdown command. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Wed Jul 21 20:17:15 2010 ExecutablePath: /usr/bin/gnome-keyring-daemon InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711337] [NEW] Firefox crashes at start on armv7L after 55.0.1 update
Public bug reported: Firefox always crashes when launched after the 55.0.1 update on an Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi), even in safe mode. I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for ARM single-board computer) on a similar board (Orange Pi Plus 2e), installed Firefox and experienced the same problem--it won't load without crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 55.0.1+build2-0ubuntu0.16.04.2 Uname: Linux 3.4.113-sun8i armv7l AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.20.1-0ubuntu2.10 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jim1138 F pulseaudio /dev/snd/controlC0: jim1138 F pulseaudio BuildID: 20170814194718 Card0.Amixer.info: Card hw:0 'audiocodec'/'audiocodec' Mixer name : '' Components : '' Controls : 12 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'sndhdmi'/'sndhdmi' Mixer name : '' Components : '' Controls : 1 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'hdmi audio format Function',0 Capabilities: enum Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO' Item0: 'pcm' Channel: Unavailable CurrentDesktop: XFCE Date: Thu Aug 17 05:37:00 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.10.1 dev eth0 default via 192.168.10.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.107 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.108 metric 600 Locales: extensions.sqlite corrupt or missing PciMultimedia: PciNetwork: Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf xenial -- 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/1711337 Title: Firefox crashes at start on armv7L after 55.0.1 update Status in firefox package in Ubuntu: New Bug description: Firefox always crashes when launched after the 55.0.1 update on an Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi), even in safe mode. I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for ARM single-board computer) on a similar board (Orange Pi Plus 2e), installed Firefox and experienced the same problem--it won't load without crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 55.0.1+build2-0ubuntu0.16.04.2 Uname: Linux 3.4.113-sun8i armv7l AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.20.1-0ubuntu2.10 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jim1138 F pulseaudio /dev/snd/controlC0: jim1138 F pulseaudio BuildID: 20170814194718 Card0.Amixer.info: Card hw:0 'audiocodec'/'audiocodec' Mixer name : '' Components : '' Controls : 12 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'sndhdmi'/'sndhdmi' Mixer name : '' Components : '' Controls : 1 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'hdmi audio format Function',0 Capabilities: enum Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO' Item0: 'pcm' Channel: Unavailable CurrentDesktop: XFCE Date: Thu Aug 17 05:37:00 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.10.1 dev eth0 default via 192.168.10.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.107 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.108 metric 600 Locales: extensions.sqlite corrupt or missing PciMultimedia: PciNetwork: Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718 RfKill: 0: phy0: Wireless LAN Soft blocked
[Desktop-packages] [Bug 1318834] Re: Applications can no longer access your @gmail.com Online Account
"Applications can no longer access your [gmail address]. Choose Online Accounts from the user menu to reinstate access to this account." This bug is still present in 17.04 with Gnome. I don't think it was an issue until I entered the information for my Google account in Online Accounts. Now, the error pops up at every login and is quite annoying. I have tried to remove it, add it again, remove it and remove authorization via Google as well as adding it and turning off all applications. Nothing works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-signon in Ubuntu. https://bugs.launchpad.net/bugs/1318834 Title: Applications can no longer access your @gmail.com Online Account Status in gnome-control-center-signon package in Ubuntu: Confirmed Bug description: IN start UBUNTU Application can no longer access your dumetz1...@gmail.com Online Account. Choose online Accounts from the user menu to reinstale access to this account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1318834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
** This bug is no longer a duplicate of bug 1639776 name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670059] Re: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot
I also have this issue. Running "alsactl restore" will allow sound to come through the headphones without rebooting, but this is suboptimal. I have attached my alsa-info output. ** Attachment added: "alsa-info.txt.vU4MuqgaEu" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059/+attachment/4883677/+files/alsa-info.txt.vU4MuqgaEu -- 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/1670059 Title: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot Status in alsa-driver package in Ubuntu: New Bug description: When (re)booting with headphones in, audio won't play. Once the headphones are unplugged, it will start to come through the speakers and will work with the headphones when they are plugged back in. Expected headphones to be detected automatically even if plugged in before boot. This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64). ALSA Info attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1066488] Re: No sound on Dell XPS after suspend (ALC275)
Hi, Daniel, Appears to be fixed entirely now. I was running Ubuntu 12.04 when I first encountered the bug, and if memory serves it was fixed at least a year or two ago. I'm currently running 16.04. Thanks for responding. -- 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/1066488 Title: No sound on Dell XPS after suspend (ALC275) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Dell XPS One 2710, Ubuntu 12.04, Kernel 3.2.0.31 or 3.2.0.32 or 3.6.2 Sound works out of the box, until machine is supended to RAM. After suspend and resume, no sound at all. A suspend to Disk and resume restores sound! aplay -l: Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC275 Analog [ALC275 Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 lsmod|grep snd: snd_hda_codec_hdmi 32506 1 snd_hda_codec_realtek79668 1 snd_hda_intel 34147 3 snd_hda_codec 135374 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 13668 1 snd_hda_codec snd_pcm97661 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_timer 29989 1 snd_pcm snd79391 13 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 15091 1 snd snd_page_alloc 18572 2 snd_hda_intel,snd_pcm It is NOT possible to unload snd modules. sudo /sbin/alsa force-unload: Unloading ALSA sound driver modules: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device snd-page-alloc (failed: modules still loaded: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-timer snd-page-alloc). All information in the net either is depreciated (using acpi_suspend) or refers to chips that have options (e.g. modprobe snd_hda_intel option=acer). There is NO documentation about options of the ALC275 chip. Anybody has a solution to this? Thanks Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1066488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1680750] Re: pm-hibernate does nothing at all
** Package changed: powerman (Ubuntu) => pm-utils (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1680750 Title: pm-hibernate does nothing at all Status in pm-utils package in Ubuntu: New Bug description: I have run from a command line: # sudo pm-hibernate and NOTHING f***ing happens. Usually it works (except for lots of issues on resume), but now I have tried it twice and it does nothing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: powerman (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 7 10:47:47 2017 InstallationDate: Installed on 2013-10-11 (1273 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: powerman UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1680750/+subscriptions -- Mailing list: https://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 1664526] Re: Evolution crashes upon launch
Thanks Josuha. I sent that information to you via apport utility per your request. Let me know if there is anything else you need. On Tue, Feb 14, 2017 at 7:05 AM, Joshua Bayfield <1664...@bugs.launchpad.net > wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please execute the following command only once, as it will > automatically gather debugging information, in a terminal: > apport-collect 1664526 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > ** Changed in: evolution (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1664526 > > Title: > Evolution crashes upon launch > > Status in evolution package in Ubuntu: > Incomplete > > Bug description: > Upon launch, I receive the following information when I launch > evolution from the terminal. This is from Xubuntu 16.10, XFCE > desktop. > > %:~$ evolution > Xlib: extension "GLX" missing on display ":0.0". > Xlib: extension "GLX" missing on display ":0.0". > libEGL warning: DRI2: failed to authenticate > > (evolution:7393): GLib-ERROR **: > /build/glib2.0-6SKPi7/glib2.0-2.50.2/./glib/gmem.c:100: > failed to allocate 4289397732 bytes > Trace/breakpoint trap (core dumped) > > > The Ubuntu crash pop-up window appeared and indicates that it "crashed > with signal in g_malloc()" > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/ > 1664526/+subscriptions > -- Regards, Jim Leslie (248) 217-6326 jimlesl...@gmail.com http://www.linkedin.com/in/jamesleslie -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1664526 Title: Evolution crashes upon launch Status in evolution package in Ubuntu: Incomplete Bug description: Upon launch, I receive the following information when I launch evolution from the terminal. This is from Xubuntu 16.10, XFCE desktop. %:~$ evolution Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". libEGL warning: DRI2: failed to authenticate (evolution:7393): GLib-ERROR **: /build/glib2.0-6SKPi7/glib2.0-2.50.2/./glib/gmem.c:100: failed to allocate 4289397732 bytes Trace/breakpoint trap (core dumped) The Ubuntu crash pop-up window appeared and indicates that it "crashed with signal in g_malloc()" --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2015-11-01 (471 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) Package: evolution 3.22.3-0ubuntu0.1 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Tags: yakkety Uname: Linux 4.8.0-37-generic i686 UpgradeStatus: Upgraded to yakkety on 2017-01-03 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1664526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664526] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1664526/+attachment/4819397/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1664526 Title: Evolution crashes upon launch Status in evolution package in Ubuntu: Incomplete Bug description: Upon launch, I receive the following information when I launch evolution from the terminal. This is from Xubuntu 16.10, XFCE desktop. %:~$ evolution Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". libEGL warning: DRI2: failed to authenticate (evolution:7393): GLib-ERROR **: /build/glib2.0-6SKPi7/glib2.0-2.50.2/./glib/gmem.c:100: failed to allocate 4289397732 bytes Trace/breakpoint trap (core dumped) The Ubuntu crash pop-up window appeared and indicates that it "crashed with signal in g_malloc()" --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2015-11-01 (471 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) Package: evolution 3.22.3-0ubuntu0.1 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Tags: yakkety Uname: Linux 4.8.0-37-generic i686 UpgradeStatus: Upgraded to yakkety on 2017-01-03 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1664526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664526] Re: Evolution crashes upon launch
apport information ** Tags added: apport-collected yakkety ** Description changed: Upon launch, I receive the following information when I launch evolution from the terminal. This is from Xubuntu 16.10, XFCE desktop. %:~$ evolution Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". libEGL warning: DRI2: failed to authenticate (evolution:7393): GLib-ERROR **: /build/glib2.0-6SKPi7/glib2.0-2.50.2/./glib/gmem.c:100: failed to allocate 4289397732 bytes Trace/breakpoint trap (core dumped) The Ubuntu crash pop-up window appeared and indicates that it "crashed with signal in g_malloc()" + --- + ApportVersion: 2.20.3-0ubuntu8.2 + Architecture: i386 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.10 + InstallationDate: Installed on 2015-11-01 (471 days ago) + InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) + Package: evolution 3.22.3-0ubuntu0.1 + PackageArchitecture: i386 + ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 + Tags: yakkety + Uname: Linux 4.8.0-37-generic i686 + UpgradeStatus: Upgraded to yakkety on 2017-01-03 (43 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1664526/+attachment/4819395/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1664526 Title: Evolution crashes upon launch Status in evolution package in Ubuntu: Incomplete Bug description: Upon launch, I receive the following information when I launch evolution from the terminal. This is from Xubuntu 16.10, XFCE desktop. %:~$ evolution Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". libEGL warning: DRI2: failed to authenticate (evolution:7393): GLib-ERROR **: /build/glib2.0-6SKPi7/glib2.0-2.50.2/./glib/gmem.c:100: failed to allocate 4289397732 bytes Trace/breakpoint trap (core dumped) The Ubuntu crash pop-up window appeared and indicates that it "crashed with signal in g_malloc()" --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2015-11-01 (471 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) Package: evolution 3.22.3-0ubuntu0.1 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Tags: yakkety Uname: Linux 4.8.0-37-generic i686 UpgradeStatus: Upgraded to yakkety on 2017-01-03 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1664526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664526] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1664526/+attachment/4819396/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1664526 Title: Evolution crashes upon launch Status in evolution package in Ubuntu: Incomplete Bug description: Upon launch, I receive the following information when I launch evolution from the terminal. This is from Xubuntu 16.10, XFCE desktop. %:~$ evolution Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". libEGL warning: DRI2: failed to authenticate (evolution:7393): GLib-ERROR **: /build/glib2.0-6SKPi7/glib2.0-2.50.2/./glib/gmem.c:100: failed to allocate 4289397732 bytes Trace/breakpoint trap (core dumped) The Ubuntu crash pop-up window appeared and indicates that it "crashed with signal in g_malloc()" --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2015-11-01 (471 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) Package: evolution 3.22.3-0ubuntu0.1 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Tags: yakkety Uname: Linux 4.8.0-37-generic i686 UpgradeStatus: Upgraded to yakkety on 2017-01-03 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1664526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664526] [NEW] Evolution crashes upon launch
Public bug reported: Upon launch, I receive the following information when I launch evolution from the terminal. This is from Xubuntu 16.10, XFCE desktop. %:~$ evolution Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". libEGL warning: DRI2: failed to authenticate (evolution:7393): GLib-ERROR **: /build/glib2.0-6SKPi7/glib2.0-2.50.2/./glib/gmem.c:100: failed to allocate 4289397732 bytes Trace/breakpoint trap (core dumped) The Ubuntu crash pop-up window appeared and indicates that it "crashed with signal in g_malloc()" ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1664526 Title: Evolution crashes upon launch Status in evolution package in Ubuntu: New Bug description: Upon launch, I receive the following information when I launch evolution from the terminal. This is from Xubuntu 16.10, XFCE desktop. %:~$ evolution Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". libEGL warning: DRI2: failed to authenticate (evolution:7393): GLib-ERROR **: /build/glib2.0-6SKPi7/glib2.0-2.50.2/./glib/gmem.c:100: failed to allocate 4289397732 bytes Trace/breakpoint trap (core dumped) The Ubuntu crash pop-up window appeared and indicates that it "crashed with signal in g_malloc()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1664526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1598993] Re: xrandr scaling corrupts external monitor output
I recently reproduced the same problem without using scaling, by connecting to a different external monitor. Now the problem exists in every video mode. Perhaps a problem of compatibility with Sky Lake integrated graphics in Thinkpad X260 -- 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/1598993 Title: xrandr scaling corrupts external monitor output Status in xorg-server package in Ubuntu: New Bug description: after doing xrandr --output HDMI2 --scale wxh, using any values except 1x1, the screen becomes increasingly distorted when typing in an editor window. The problem first appears as images of the previous cursor position being left behind, but as typing continues, lines below that being edited become increasingly garbled. The distortion can be removed temporarily by dragging the window to a different position. But of course it comes back as soon as editing resumes. The problem appears also in typing in an xterm window, as the image of the cursor gets left behind while typing the space bar. This makes the scale option completely useless for my usual purposes, and forces me to live with a screen resolution that doesn't properly fill the external monitor. The problem did not exist in xrandr 1.3.3 on my old system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1598993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
Reply back here if anything like this comes up again and we can discuss re-opening this bug. ** Changed in: media-hub (Ubuntu) Status: Incomplete => Invalid ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid ** Changed in: qtmultimedia-opensource-src (Ubuntu) Status: Confirmed => 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/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Status in qtmultimedia-opensource-src package in Ubuntu: Invalid Status in telephony-service package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1643119] [NEW] package tex-common 6.05 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: on a normal upgrade ProblemType: Package DistroRelease: Ubuntu 16.10 Package: tex-common 6.05 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 Date: Fri Nov 18 19:27:40 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-02-17 (1736 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: tex-common Title: package tex-common 6.05 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-11-19 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1643119 Title: package tex-common 6.05 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: on a normal upgrade ProblemType: Package DistroRelease: Ubuntu 16.10 Package: tex-common 6.05 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 Date: Fri Nov 18 19:27:40 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-02-17 (1736 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: tex-common Title: package tex-common 6.05 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-11-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1643119/+subscriptions -- Mailing list: https://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 1635668] [NEW] [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
Replaced the Radeon with a Geforce 710 eliminating a Cirago DisplayPort to HDMI adapter and the problem went away. On Fri, Oct 21, 2016 at 12:09 PM, Jim Tarvid <tar...@ls.net> wrote: > Public bug reported: > > This defect is not apparent on two other Ubuntu 16.04 machines. The > upgrade to 16.10 did not change the symptoms. > > lsb_release -rd > Description:Ubuntu 16.10 > Release:16.10 > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 > Uname: Linux 4.8.0-26-generic x86_64 > ApportVersion: 2.20.3-0ubuntu8 > Architecture: amd64 > CurrentDesktop: Unity > Date: Fri Oct 21 11:53:54 2016 > InstallationDate: Installed on 2016-09-22 (29 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed > Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] > - HDA ATI HDMI > Symptom_Jack: Digital Out, HDMI > Symptom_Type: Digital clip or distortion, or "overdriven" sound > Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted > UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago) > dmi.bios.date: 09/19/2012 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A08 > dmi.board.name: 0773VG > dmi.board.vendor: Dell Inc. > dmi.board.version: A01 > dmi.chassis.type: 3 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.: > pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr: > dmi.product.name: OptiPlex 7010 > dmi.product.version: 01 > dmi.sys.vendor: Dell Inc. > > ** Affects: alsa-driver (Ubuntu) > Importance: Undecided > Status: New > > > ** Tags: amd64 apport-bug yakkety > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1635668 > > Title: > [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+ > bug/1635668/+subscriptions > -- Kindness Works! Jim Tarvid 12897A Grays Pointe Road, Fairfax, Va 22033-2143 38.87782, -77.39270 703-657-0099 Condo 703-624-5289 Cell 703-594-7297 Google voice 202-753-0025 Tablet http://ls.net -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1635668 Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted Status in alsa-driver package in Ubuntu: New Bug description: This defect is not apparent on two other Ubuntu 16.04 machines. The upgrade to 16.10 did not change the symptoms. lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 21 11:53:54 2016 InstallationDate: Installed on 2016-09-22 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0773VG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
@Andrea, Anupam, Robie: That's interesting indeed and might explain why I've never been able to reproduce this myself. I would always have been actively engaged with the phone when trying to reproduce this. -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
@Andrea: media-hub manages the playback state of nearly all playback sessions on Ubuntu Touch. It utilizes pulseaudio for the sound server. Any sounds coming from the web browser or web apps do not use media-hub. Ringtone and notification sounds all go through media-hub for playback. -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132
I also cannot log on since the update to 304.132. Ubuntu 14.04 Geforce 9100 Right now I am using the nouveau driver but it is not a satisfactory solution. I have two monitors and with the nouveau driver one runs at a much lower resolution that the other. With the 304.131 driver this was not the case. Having struggled to get a system that works I am hesitant to try the workaround in comment #20 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-legacy-304xx package in Debian: Confirmed Bug description: Ubuntu 16.04 LTS NVIDIA driver: - nvidia-graphics-drivers-304 - update to version 304.132 dpkg.log: upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2 - reboot - lightdm login screen - login - a few seconds some flickering - and the lightdm login screen appears again It is not possible to login. Unity is not loading. .xsession-errors: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 34 Current serial number in output stream: 35 See also bug 1634802 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635668] [NEW] [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
Public bug reported: This defect is not apparent on two other Ubuntu 16.04 machines. The upgrade to 16.10 did not change the symptoms. lsb_release -rd Description:Ubuntu 16.10 Release:16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 21 11:53:54 2016 InstallationDate: Installed on 2016-09-22 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0773VG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1635668 Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted Status in alsa-driver package in Ubuntu: New Bug description: This defect is not apparent on two other Ubuntu 16.04 machines. The upgrade to 16.10 did not change the symptoms. lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 21 11:53:54 2016 InstallationDate: Installed on 2016-09-22 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0773VG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in isn't supported and may not works as expected
This bug is easy to fix. For example, it will be caused by a section like this: zh-cn zh-sg The correct syntax would be zh-cn zh-sg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-arphic-ukai in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in isn't supported and may not works as expected Status in culmus package in Ubuntu: Fix Released Status in fonts-arphic-ukai package in Ubuntu: Fix Released Status in fonts-arphic-uming package in Ubuntu: Fix Released Status in fonts-baekmuk package in Ubuntu: Fix Released Status in fonts-droid package in Ubuntu: Fix Released Status in fonts-nanum package in Ubuntu: Fix Released Status in fonts-nanum-coding package in Ubuntu: Fix Released Status in fonts-sil-andika package in Ubuntu: Fix Released Status in fonts-tlwg package in Ubuntu: Fix Released Status in fonts-unfonts-core package in Ubuntu: Fix Released Status in fonts-unfonts-extra package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in ttf-wqy-zenhei package in Ubuntu: Fix Released Status in culmus source package in Quantal: Fix Released Status in fonts-arphic-ukai source package in Quantal: Fix Released Status in fonts-arphic-uming source package in Quantal: Fix Released Status in fonts-baekmuk source package in Quantal: Fix Released Status in fonts-droid source package in Quantal: Fix Released Status in fonts-nanum source package in Quantal: Fix Released Status in fonts-nanum-coding source package in Quantal: Fix Released Status in fonts-sil-andika source package in Quantal: Fix Released Status in fonts-tlwg source package in Quantal: Fix Released Status in fonts-unfonts-core source package in Quantal: Fix Released Status in fonts-unfonts-extra source package in Quantal: Fix Released Status in language-selector source package in Quantal: Fix Released Status in ttf-wqy-zenhei source package in Quantal: Fix Released Status in fonts-arphic-ukai package in Debian: Fix Released Status in fonts-arphic-uming package in Debian: Fix Released Status in fonts-baekmuk package in Debian: Fix Released Status in fonts-droid package in Debian: Fix Released Status in fonts-nanum package in Debian: Fix Released Status in fonts-sil-andika package in Debian: Fix Released Status in fonts-unfonts-core package in Debian: Fix Released Status in fonts-unfonts-extra package in Debian: Fix Released Status in ttf-wqy-zenhei package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf [Test Case] 1) Install the fonts in question 2) Open a terminal 3) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal [Regression Potential] In case of a regression, the font in question can be affected. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
