[Desktop-packages] [Bug 1820323] Re: amdgpu-pro xorg crash
** Changed in: xorg-server (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1820323 Title: amdgpu-pro xorg crash Status in xorg-server package in Ubuntu: New Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
** Tags removed: verification-failed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorgproto in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time
use another method to install, it's there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time Status in libxkbcommon package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Committed Bug description: [Impact] libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the package isn't properly multi-archified in bionic [Test case] apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64 should succeed [Regression potential] not really -- Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820323] Re: amdgpu-pro xorg crash
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1820323 Title: amdgpu-pro xorg crash Status in xorg-server package in Ubuntu: Expired Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824330] Re: crashed when tried to do gedit textname
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1824330 Title: crashed when tried to do gedit textname Status in gedit package in Ubuntu: Expired Bug description: (gedit:18666): dbind-WARNING **: 18:11:43.231: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-EV6hC9BiLn: Connection refused ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smbclient (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 11 18:08:19 2019 InstallationDate: Installed on 2018-08-17 (237 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: samba UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1824330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Process follows directly from previous comment. - Updated to network-manager 1.10.14-0ubuntu2 (from bionic-proposed) - Rebooted and ran dig twice to mirror previous test, never resolved to expected result. :( - Log file from reboot until after the second dig attached. Ran dig a few more times over a couple of minutes, but never resolved successfully. ** Attachment added: "nm-1.10.14.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+attachment/5270070/+files/nm-1.10.14.log -- 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/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Incomplete Status in network-manager source package in Bionic: Incomplete Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Can only attach one file at a time, so this and the next comment are heavily linked. - Updated to systemd 237-3ubuntu10.22 (from bionic-updates) - Enabled debug logging for network manager and disabled flood protection on journald. - Rebooted and successfully ran dig (second attempt) - First run did not return expected IP. - Second run onwards resolved as expected. - Log file from reboot until after the second dig attached. ** Attachment added: "nm-1.10.6.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+attachment/5270066/+files/nm-1.10.6.log -- 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/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Incomplete Status in network-manager source package in Bionic: Incomplete Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832268] Re: Low performance when I play a game
Thanks for the bug report. It does sound strange that pressing Escape improves performance. I wonder if that's a quirk of the game itself. Does pressing Escape work only in one specific game or multiple games? ** Tags added: nvidia ** Summary changed: - Low performance when I play a game + [nvidia] Low performance when I play a game ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1832268 Title: [nvidia] Low performance when I play a game Status in mutter package in Ubuntu: Incomplete Bug description: Low performance when I play a game, i have a 18 fps frame rate, but when I press "Esc" the frame rate come back to usual performance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 17:30:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.18.0-20-generic, x86_64: installed nvidia, 390.116, 4.18.0-21-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 1050] [1462:8c97] InstallationDate: Installed on 2019-05-14 (27 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=ffe2dbb1-cd8c-415e-91c3-d382f32bb40e ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M PLUS/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/mutter/+bug/1832268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
What model machine are you seeing this bug on? -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Confirmed Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 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/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
Duplicate bug 1828393 suggests Bluetooth theoretically allows for two profiles to be enabled simultaneously. That would resolve this, but I don't know if it's true. If it is true then any fix would require modifying PulseAudio and the GUI in gnome-control-center. Maybe it's not really simultaneous. Maybe it's just smarter automatic switching. There is an upstream bug for that already: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/81 ** Bug watch added: PulseAudio #81 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/81 ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/81 Importance: Unknown Status: Unknown -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832283] [NEW] /usr/bin/gnome-software:double free or corruption (out)
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.30.6-2ubuntu4, the problem page at https://errors.ubuntu.com/problem/90c2b072fcbf913fd3cd8d6314f822fa198163c2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1832283 Title: /usr/bin/gnome-software:double free or corruption (out) Status in gnome-software package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.30.6-2ubuntu4, the problem page at https://errors.ubuntu.com/problem/90c2b072fcbf913fd3cd8d6314f822fa198163c2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1832283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Hi all, We have found a workaround, for the display not usable. I give it here for people like me who were stuck... with dell. Since I cannot comment my post #24, here a summary: Step to reproduce: Plug HDMI cable 4k ready, of course connected to 4k screen. Actual result: Purpul screen (default color of my background) on both screen... To have any things displayed I need to use CTRL + ALT + F1. Using "Screen Mode" key (i.e. F8) we were able to have display properly set. Hope this helps... BR Eric. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
I was wondering why it took so long to be able to unlock my laptop and it looks like it is this bug. Jun 10 15:34:30 speedy dbus-daemon[989]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.335' (uid=1000 pid=3119 comm="/usr/bin/gnome-shell " label="unconfined") Jun 10 15:34:30 speedy systemd[1]: Starting Fingerprint Authentication Daemon... Jun 10 15:34:55 speedy dbus-daemon[989]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms) Jun 10 15:34:55 speedy gnome-shell[3119]: Failed to connect to Fprint service: Error calling StartServiceByName for net.reactivated.Fprint: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'net.reactivated.Fprint ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Confirmed Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 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/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.
*** This bug is a duplicate of bug 1652282 *** https://bugs.launchpad.net/bugs/1652282 I did not delete libgtk-x11-2.0.so.0. I installed 19.04 a few days ago. Unit tmp.mount does not exist, proceeding anyway. /usr/sbin/gpartedbin: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1744372 Title: gparted does not start - Unit -.mount does not exist, proceeding anyway. Status in gparted package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Invalid Bug description: 1. fresh ubuntu 18.04 daily: lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. install gparted with Software: gparted: Installiert: 0.30.0-3ubuntu1 Installationskandidat: 0.30.0-3ubuntu1 Versionstabelle: *** 0.30.0-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. launch with icon - enter password - nothing. 4.launch in terminal: Unit -.mount does not exist, proceeding anyway. Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null. Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount. Removed /run/systemd/system/run-snapd-ns.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/snap-core-3748.mount. Removed /run/systemd/system/snap-vlc-113.mount. Removed /run/systemd/system/tmp.mount. How to Fix: run xhost +local: before gparted! # this only bypass the wayland restriction; meaning a security violation (not a fix !!! ) thomas@ubuntu-1804:~$ xhost +local: non-network local connections being added to access control list thomas@ubuntu-1804:~$ gparted Unit -.mount does not exist, proceeding anyway. Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null. Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. Gtk-Message: Failed to load module "canberra-gtk-module" == libparted : 3.2 == Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount. Removed /run/systemd/system/run-snapd-ns.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/snap-core-3748.mount. Removed /run/systemd/system/snap-vlc-113.mount. Removed /run/systemd/system/tmp.mount. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gparted 0.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 19:45:14 2018 InstallationDate: Installed on 2018-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1832258] Re: Need to backport fix for inability to add Canon printers
** Changed in: cups Status: Unknown => Fix Released -- 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/1832258 Title: Need to backport fix for inability to add Canon printers Status in CUPS: Fix Released Status in cups package in Ubuntu: New Bug description: The following bug was reported and fixed in cups 2.2.11. https://github.com/apple/cups/issues/5484 Without the fix, it is not possible to add or use a number of Canon printers. Currently, 19.04 ships with 2.2.10 + some backports, but those backports do not include the fix for this problem. We either need the fix backported or an update to 2.2.11. Release: Ubuntu 19.04 Version: 2.2.10-4ubuntu2 What you expected: Adding a canon printer works What happened instead: Adding a canon printer fails with a useless error and log investigation lead to upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1832258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832268] [NEW] Low performance when I play a game
Public bug reported: Low performance when I play a game, i have a 18 fps frame rate, but when I press "Esc" the frame rate come back to usual performance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 17:30:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.18.0-20-generic, x86_64: installed nvidia, 390.116, 4.18.0-21-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 1050] [1462:8c97] InstallationDate: Installed on 2019-05-14 (27 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=ffe2dbb1-cd8c-415e-91c3-d382f32bb40e ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M PLUS/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance 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/1832268 Title: Low performance when I play a game Status in xorg package in Ubuntu: New Bug description: Low performance when I play a game, i have a 18 fps frame rate, but when I press "Esc" the frame rate come back to usual performance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 17:30:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.18.0-20-generic, x86_64: installed nvidia, 390.116, 4.18.0-21-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 1050] [1462:8c97] InstallationDate:
[Desktop-packages] [Bug 1821957] Re: Turning off a monitor unlocks the computer
** Changed in: gnome-screensaver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1821957 Title: Turning off a monitor unlocks the computer Status in Ubuntu Budgie: Incomplete Status in gnome-screensaver package in Ubuntu: Incomplete Bug description: I am using budgie desktop installed on ubuntu 18. I am using a computer with two monitors. When the computer is locked and i turn off a monitor, the system is unlocked. I also realized that the keyboard does not work. Budgie-desktop 10.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1821957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832041] Re: The mouse stops working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1832041 Title: The mouse stops working Status in xorg package in Ubuntu: New Bug description: Sometime the wifi is not getting detected and the mouse is not working and and i am using touch instead of mouse, the external mouse is also not working ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 8 00:40:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-47-generic, x86_64: installed nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.18.0-17-generic, x86_64: installed nvidia, 390.116, 4.18.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83ba] Subsystem: Hewlett-Packard Company GP108M [GeForce MX150] [103c:83ba] InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 05c8:0815 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 009: ID 03f0:0941 Hewlett-Packard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 15-ch0xx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=a759c10c-be50-4caf-bd43-1516b97d1c6a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83BA dmi.board.vendor: HP dmi.board.version: 57.31 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.23:bd10/15/2018:svnHP:pnHPSpectrex360Convertible15-ch0xx:pvr:rvnHP:rn83BA:rvr57.31:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-ch0xx dmi.product.sku: 2FW61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 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/1832041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832258] [NEW] Need to backport fix for inability to add Canon printers
Public bug reported: The following bug was reported and fixed in cups 2.2.11. https://github.com/apple/cups/issues/5484 Without the fix, it is not possible to add or use a number of Canon printers. Currently, 19.04 ships with 2.2.10 + some backports, but those backports do not include the fix for this problem. We either need the fix backported or an update to 2.2.11. Release: Ubuntu 19.04 Version: 2.2.10-4ubuntu2 What you expected: Adding a canon printer works What happened instead: Adding a canon printer fails with a useless error and log investigation lead to upstream issue. ** Affects: cups Importance: Unknown Status: Unknown ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/apple/cups/issues #5484 https://github.com/apple/cups/issues/5484 ** Also affects: cups via https://github.com/apple/cups/issues/5484 Importance: Unknown Status: Unknown -- 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/1832258 Title: Need to backport fix for inability to add Canon printers Status in CUPS: Unknown Status in cups package in Ubuntu: New Bug description: The following bug was reported and fixed in cups 2.2.11. https://github.com/apple/cups/issues/5484 Without the fix, it is not possible to add or use a number of Canon printers. Currently, 19.04 ships with 2.2.10 + some backports, but those backports do not include the fix for this problem. We either need the fix backported or an update to 2.2.11. Release: Ubuntu 19.04 Version: 2.2.10-4ubuntu2 What you expected: Adding a canon printer works What happened instead: Adding a canon printer fails with a useless error and log investigation lead to upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1832258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832249] Re: Notify when battery is low at 15%, and notify again when critically low at 5%
** Changed in: gnome-settings-daemon Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832249 Title: Notify when battery is low at 15%, and notify again when critically low at 5% Status in GNOME Settings Daemon: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: According to the upstream bug, power notifications are done by gnome-settings-daemon and the decision whether a battery is considered "low" or "critical" happens in UPower. - What should happen: I should be getting two notifications currently: "Battery Low" or "Laptop battery low" usually set to 10% "Battery critically low" or "Laptop battery critically low" at 3% The laptop should then suspend to disk at 2% (or power off as that is usually not possible). - What happens instead: I get one notification when the battery is at 5% and it doesn't say that the laptop is going to suspend to disk. I believe that is sub-optimal especially when I'm not looking at the battery status, in the case of a full-screen video or game. It would be better to give a first (yellow coloured) notification at low battery 15% and a second (red coloured) notification at critically low battery 5%. My Android phone does that for example. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 19:44:08 2019 InstallationDate: Installed on 2018-11-29 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832173] Re: nautilus crashed with SIGSEGV
The core dump included in this crash report is corrupted so retracing is not possible. Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.10/amd64/report-sandbox//usr/bin/nautilus... Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.10/amd64/report-sandbox/usr/lib/debug/.build-id/ed/225155cf94bd3b6e89bcf31cd7bb9d2efc09c3.debug... "/tmp/apport_core_12qy88ar" is not a core dump: file truncated (gdb) quit ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1832173 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Invalid Bug description: just rebooted with new kernel, no nautilus open, just firefox. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 08:39:04 2019 Disassembly: No registers. ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'162' b'org.gnome.nautilus.window-state' b'initial-size' b'(1141, 776)' b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-05-07 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190507) ProcCmdline: /usr/bin/nautilus --gapplication-service Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1832173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
This was fixed in systemd 237-3ubuntu10.22 for bionic, and 239-7ubuntu10.14 for cosmic. I missed a "#" in the changelog (sorry) so the tooling didn't automatically mark this bug as fix released. ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: systemd (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Tags removed: ddstreet-next -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Won't Fix Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832249] [NEW] Notify when battery is low at 15%, and notify again when critically low at 5%
Public bug reported: According to the upstream bug, power notifications are done by gnome-settings-daemon and the decision whether a battery is considered "low" or "critical" happens in UPower. - What should happen: I should be getting two notifications currently: "Battery Low" or "Laptop battery low" usually set to 10% "Battery critically low" or "Laptop battery critically low" at 3% The laptop should then suspend to disk at 2% (or power off as that is usually not possible). - What happens instead: I get one notification when the battery is at 5% and it doesn't say that the laptop is going to suspend to disk. I believe that is sub-optimal especially when I'm not looking at the battery status, in the case of a full-screen video or game. It would be better to give a first (yellow coloured) notification at low battery 15% and a second (red coloured) notification at critically low battery 5%. My Android phone does that for example. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 19:44:08 2019 InstallationDate: Installed on 2018-11-29 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon Importance: Unknown Status: Unknown ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #409 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/409 ** Also affects: gnome-settings-daemon via https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/409 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832249 Title: Notify when battery is low at 15%, and notify again when critically low at 5% Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: New Bug description: According to the upstream bug, power notifications are done by gnome-settings-daemon and the decision whether a battery is considered "low" or "critical" happens in UPower. - What should happen: I should be getting two notifications currently: "Battery Low" or "Laptop battery low" usually set to 10% "Battery critically low" or "Laptop battery critically low" at 3% The laptop should then suspend to disk at 2% (or power off as that is usually not possible). - What happens instead: I get one notification when the battery is at 5% and it doesn't say that the laptop is going to suspend to disk. I believe that is sub-optimal especially when I'm not looking at the battery status, in the case of a full-screen video or game. It would be better to give a first (yellow coloured) notification at low battery 15% and a second (red coloured) notification at critically low battery 5%. My Android phone does that for example. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 19:44:08 2019 InstallationDate: Installed on 2018-11-29 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
Disappointing that 9 years on this is still an issue. If I have A2DP Sink selected I have no Mic option, and if I use HSP/HFP the audio quality sounds like it's being played down a 14.4K modem; you might as well not have audio as it's just going to cause your ears to bleed. -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832031] Re: No sound on external Samsung Monitor via Display Port/HDMI
** Package changed: ubuntu => pulseaudio (Ubuntu) -- 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/1832031 Title: No sound on external Samsung Monitor via Display Port/HDMI Status in pulseaudio package in Ubuntu: New Bug description: Hello, I have two external monitor connected via a Dell TB16 (thunderbolt). One is a Samsung T28C570 and the other one is a Samsung CF791. The first one is connected via HDMI. The second one is connected via Display Port. The problem is that sound on Samsung CF791 doesn't work. I know it's not a mixer problem because: 1) Sometime, If i press CTRL+ALT+F2 (to enter in console mode) and then go back on Desktop with CTRL+ALT+F1 i can heard sound from the monitor when I increase or decrease volume, even if a little bit distorted. Nevertheless, if I try to play a video (for example youtube), sound stops to work. I have to stop any audio stream, return to console mode and back again in desktop to hear again distorted sound then increase volume. 2) On Windows, I have no problem (so it seems not to be an hardware issue). I tried to connect the CF791 via HDMI, but problem persist. I have no problem with the other monitor. I have checked every alsamixer e pavucontrol settings unsuccessful. My laptop is a Dell XPS 13. Description:Ubuntu 18.04.2 LTS Release:18.04 THe HDMI2 is the not working audio device: Lista di PLAYBACK dispositivi hardware scheda 0: PCH [HDA Intel PCH], dispositivo 0: ALC3271 Analog [ALC3271 Analog] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 3: HDMI 0 [HDMI 0] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 7: HDMI 1 [HDMI 1] Sottoperiferiche: 0/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 8: HDMI 2 [HDMI 2] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 9: HDMI 3 [HDMI 3] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 10: HDMI 4 [HDMI 4] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 1: Dock [WD15 Dock], dispositivo 0: USB Audio [USB Audio] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 1: Dock [WD15 Dock], dispositivo 1: USB Audio [USB Audio #1] Sottoperiferiche: 1/1 Hardware list: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3
[Desktop-packages] [Bug 1832031] [NEW] No sound on external Samsung Monitor via Display Port/HDMI
You have been subscribed to a public bug: Hello, I have two external monitor connected via a Dell TB16 (thunderbolt). One is a Samsung T28C570 and the other one is a Samsung CF791. The first one is connected via HDMI. The second one is connected via Display Port. The problem is that sound on Samsung CF791 doesn't work. I know it's not a mixer problem because: 1) Sometime, If i press CTRL+ALT+F2 (to enter in console mode) and then go back on Desktop with CTRL+ALT+F1 i can heard sound from the monitor when I increase or decrease volume, even if a little bit distorted. Nevertheless, if I try to play a video (for example youtube), sound stops to work. I have to stop any audio stream, return to console mode and back again in desktop to hear again distorted sound then increase volume. 2) On Windows, I have no problem (so it seems not to be an hardware issue). I tried to connect the CF791 via HDMI, but problem persist. I have no problem with the other monitor. I have checked every alsamixer e pavucontrol settings unsuccessful. My laptop is a Dell XPS 13. Description:Ubuntu 18.04.2 LTS Release:18.04 THe HDMI2 is the not working audio device: Lista di PLAYBACK dispositivi hardware scheda 0: PCH [HDA Intel PCH], dispositivo 0: ALC3271 Analog [ALC3271 Analog] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 3: HDMI 0 [HDMI 0] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 7: HDMI 1 [HDMI 1] Sottoperiferiche: 0/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 8: HDMI 2 [HDMI 2] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 9: HDMI 3 [HDMI 3] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 0: PCH [HDA Intel PCH], dispositivo 10: HDMI 4 [HDMI 4] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 1: Dock [WD15 Dock], dispositivo 0: USB Audio [USB Audio] Sottoperiferiche: 1/1 Sottoperiferica #0: subdevice #0 scheda 1: Dock [WD15 Dock], dispositivo 1: USB Audio [USB Audio #1] Sottoperiferiche: 1/1 Hardware list: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 3a:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3b:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3b:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3d:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3e:01.0 PCI bridge: Intel
[Desktop-packages] [Bug 1797820] Re: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamo
Maybe this update corriga this error: xorg-server: 1.20.5 https://lists.x.org/archives/xorg-announce/2019-May/002993.html -- 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/1797820 Title: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_composite_clipped_region Status in xorg-server package in Ubuntu: Confirmed Bug description: Xwayland: https://errors.ubuntu.com/problem/f8ea9bb558676edbe2acec52b0f386ab1321fdaf Xorg: https://errors.ubuntu.com/problem/90ab0b3de538bdc1058e1af52156d870e04dd56e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1797820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797820] Re: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamo
** Tags added: eoan -- 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/1797820 Title: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_composite_clipped_region Status in xorg-server package in Ubuntu: Confirmed Bug description: Xwayland: https://errors.ubuntu.com/problem/f8ea9bb558676edbe2acec52b0f386ab1321fdaf Xorg: https://errors.ubuntu.com/problem/90ab0b3de538bdc1058e1af52156d870e04dd56e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1797820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
This bug was fixed in the package cups - 2.1.3-4ubuntu0.9 --- cups (2.1.3-4ubuntu0.9) xenial; urgency=medium * d/p/0045-Fix-an-issue-with-PreserveJobHistory-and-time-values.patch Fix an issue with `PreserveJobHistory` and time values (Issue #5538, Closes: #921741, LP: #1747765) -- Dariusz Gadomski Thu, 30 May 2019 11:33:26 +0200 ** Changed in: cups (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Released Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Thanks! I've just installed it on one of my Xenial servers for testing... I'll let you know how it goes... Cheers! -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Released Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
This bug was fixed in the package cups - 2.2.7-1ubuntu2.6 --- cups (2.2.7-1ubuntu2.6) bionic; urgency=medium * d/p/0045-Fix-an-issue-with-PreserveJobHistory-and-time-values.patch Fix an issue with `PreserveJobHistory` and time values (Issue #5538, Closes: #921741, LP: #1747765) -- Dariusz Gadomski Thu, 30 May 2019 10:02:17 +0200 -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
This bug was fixed in the package cups - 2.2.8-5ubuntu1.4 --- cups (2.2.8-5ubuntu1.4) cosmic; urgency=medium * d/p/0045-Fix-an-issue-with-PreserveJobHistory-and-time-values.patch Fix an issue with `PreserveJobHistory` and time values (Issue #5538, Closes: #921741, LP: #1747765) -- Dariusz Gadomski Thu, 30 May 2019 14:11:53 +0200 ** Changed in: cups (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: cups (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
This bug was fixed in the package cups - 2.2.10-4ubuntu2 --- cups (2.2.10-4ubuntu2) disco; urgency=medium * d/p/0045-Fix-an-issue-with-PreserveJobHistory-and-time-values.patch Fix an issue with `PreserveJobHistory` and time values (Issue #5538, Closes: #921741, LP: #1747765) -- Dariusz Gadomski Thu, 30 May 2019 09:51:37 +0200 ** Changed in: cups (Ubuntu Disco) Status: Fix Committed => Fix Released -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Released Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747765] Update Released
The verification of the Stable Release Update for cups has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830049] Re: nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.2.0-0.1
This bug was fixed in the package nvidia-graphics-drivers-340 - 340.107-0ubuntu4 --- nvidia-graphics-drivers-340 (340.107-0ubuntu4) eoan; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_5.2.patch debian/templates/dkms_nvidia.conf.in: - Add support for Linux 5.2 (LP: #1830049). -- Alberto Milone Mon, 10 Jun 2019 13:18:45 +0200 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1830049 Title: nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.2.0-0.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/n/nvidia-graphics-drivers-340/20190522_043007_06930@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/i386/n/nvidia-graphics-drivers-340/20190522_121357_06930@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1830049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Thank you for verifying all the test cases! -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832224] [NEW] battery status always shows "Estimating.........."
Public bug reported: This is lenovo G560 laptop. ** Affects: upower (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1832224 Title: battery status always shows "Estimating.." Status in upower package in Ubuntu: New Bug description: This is lenovo G560 laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1832224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832222] [NEW] using aakar font reboots printer
Public bug reported: A user accidentally selected the aakar font for one cell of a spreadsheet containing English text. Printing the spreadsheet resulted in the printer displaying: Rebooting... followed by Initializing The result was the same for both printers tried: Samsung SL-M3820ND and HP Colour LaserJet CM1017 The spreadsheet was exported to a PDF, printing the PDF caused the same printer reboot. Opening the PDF in Libre Office Draw and printing caused the same printer reboot. If the font was changed to Liberation Sans, the file could be printed. A minimal Libre Office spreadsheet with the problem is attached. ** Affects: fonts-gujr-extra (Ubuntu) Importance: Undecided Status: New ** Attachment added: "spreadsheet with font problem" https://bugs.launchpad.net/bugs/183/+attachment/5269913/+files/aakar_problem.ods -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-gujr-extra in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: using aakar font reboots printer Status in fonts-gujr-extra package in Ubuntu: New Bug description: A user accidentally selected the aakar font for one cell of a spreadsheet containing English text. Printing the spreadsheet resulted in the printer displaying: Rebooting... followed by Initializing The result was the same for both printers tried: Samsung SL-M3820ND and HP Colour LaserJet CM1017 The spreadsheet was exported to a PDF, printing the PDF caused the same printer reboot. Opening the PDF in Libre Office Draw and printing caused the same printer reboot. If the font was changed to Liberation Sans, the file could be printed. A minimal Libre Office spreadsheet with the problem is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-gujr-extra/+bug/183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830049] Re: nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.2.0-0.1
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1830049 Title: nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.2.0-0.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: In Progress Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/n/nvidia-graphics-drivers-340/20190522_043007_06930@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/i386/n/nvidia-graphics-drivers-340/20190522_121357_06930@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1830049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776030] Re: Backup fails with "an unknown error"
I see something that looks *exactly* identical to the problem sambo63 has (#6): Same uname -a, same everything except for: deja-dup --version deja-dup 37.0 I get: Backup Failed Failed with an unknown error. Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1511, in do_backup full_backup(col_stats) File "/usr/bin/duplicity", line 572, in full_backup globals.backend) File "/usr/bin/duplicity", line 454, in write_multivol (tdp, dest_filename, vol_num))) File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 146, in schedule_task return self.__run_synchronously(fn, params) File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 172, in __run_synchronously ret = fn(*params) File "/usr/bin/duplicity", line 453, in vol_num: put(tdp, dest_filename, vol_num), File "/usr/bin/duplicity", line 342, in put backend.put(tdp, dest_filename) File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in inner_retry % (n, e.__class__.__name__, util.uexc(e))) File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc return ufn(unicode(e).encode('utf-8')) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128) -- 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/1776030 Title: Backup fails with "an unknown error" Status in deja-dup package in Ubuntu: Confirmed Bug description: Trying to a backup to a network drive. Yesterday Backup decided to do the preiodic full backup. But it fails, and I get the following error information with the "unknown error" message: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1522, in do_backup check_last_manifest(col_stats) # not needed for full backup File "/usr/bin/duplicity", line 1227, in check_last_manifest last_backup_set.check_manifests() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201, in check_manifests remote_manifest = self.get_remote_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 242, in get_remote_manifest return manifest.Manifest().from_string(manifest_buffer) File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 188, in from_string vi = VolumeInfo().from_string(match.group(1)) File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 388, in from_string raise VolumeInfoError("Start or end index not set") VolumeInfoError: Start or end index not set lsb_release -rd > Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy deja-dup > deja-dup: Installed: 37.1-2fakesync1 Candidate: 37.1-2fakesync1 Version table: *** 37.1-2fakesync1 500 500 http://la-mirrors.evowise.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-2fakesync1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 21:14:08 2018 InstallationDate: Installed on 2016-02-26 (834 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: deja-dup UpgradeStatus: Upgraded to bionic on 2018-05-03 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832145] Re: X.org freeze after selecting nvidia profile on Plasma Desktop
#1 doesn't happen to be always the case, most of the times the desktop become unusuable. Anyway, with further testing I updated the bug. Looks like related to the X server settings. Opening it TWICE after selecting the NVIDIA card from intel, triggers this behavior. ** Summary changed: - X.org freeze after selecting nvidia profile + X.org freeze after selecting nvidia profile on Plasma Desktop ** Description changed: - - Using ubuntu 18.04.2 LTS. + - Using ubuntu 18.04.2 LTS, also tried 19.10 development eoan edition. - Tried driver NVIDIA 390 + 430 from the repo, same result - - KDE Plasma desktop + - Happens only on KDE Plasma desktop + - Does not happen on GNOME desktop + - Used the X server settings instead of the CLI Reproducibility: 75% Steps required: - Installing nvidia drivers on an optimus laptop - Rebooting - Select NVIDIA GPU with prime from Intel - Waiting some seconds + - Opening NVIDIA X server settings again, increases a lot the chance of the freeze to happen (looks like it gets the nvidia module loaded even before the session logout) - Bug observed: - - Before the nvidia module gets loaded (I could type lsmod | grep nvidia fine and no module is loaded after the first 3 seconds) - - When (presumably) the nvidia driver is loaded, the X.org session locks up. The mouse cursor can move things, but cannot click anything, everything else on the screen is frozen up + Bug observed: + - Before the nvidia module gets loaded (I could type lsmod | grep nvidia fine and no module is loaded after the first 3 seconds) + - When (presumably) the nvidia driver is loaded (checked from a tty), the X.org session locks up. The mouse cursor can move things, but cannot click anything, everything else on the screen is frozen up Workaround: Killing the X.org session gives an usable graphical system - Notes: If the session ends (doing a logout so SDDM) there is no lockup - at all, but once the nvidia driver is loaded, it looks like it's when - the issue appears. - - I recently moved from 19.04 to 18.04.2 LTS, and I don't remember this - issue happening at all, is that some fix that needs to be backported? + Notes: If the session ends (doing a logout so SDDM) before the nvidia + module gets loaded, there is no lockup at all, but once the nvidia + driver is loaded, it looks like it's when the issue appears. ** Description changed: - Using ubuntu 18.04.2 LTS, also tried 19.10 development eoan edition. - Tried driver NVIDIA 390 + 430 from the repo, same result - Happens only on KDE Plasma desktop - Does not happen on GNOME desktop - - Used the X server settings instead of the CLI + - Used the X server settings instead of the CLI Reproducibility: 75% Steps required: - Installing nvidia drivers on an optimus laptop - Rebooting - Select NVIDIA GPU with prime from Intel - Waiting some seconds - - Opening NVIDIA X server settings again, increases a lot the chance of the freeze to happen (looks like it gets the nvidia module loaded even before the session logout) + - Opening NVIDIA X server settings again TWICE, increases a lot the chance of the freeze to happen (looks like it gets the nvidia module loaded even before the session logout) Bug observed: - Before the nvidia module gets loaded (I could type lsmod | grep nvidia fine and no module is loaded after the first 3 seconds) - When (presumably) the nvidia driver is loaded (checked from a tty), the X.org session locks up. The mouse cursor can move things, but cannot click anything, everything else on the screen is frozen up Workaround: Killing the X.org session gives an usable graphical system Notes: If the session ends (doing a logout so SDDM) before the nvidia module gets loaded, there is no lockup at all, but once the nvidia driver is loaded, it looks like it's when the issue appears. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1832145 Title: X.org freeze after selecting nvidia profile on Plasma Desktop Status in nvidia-prime package in Ubuntu: New Bug description: - Using ubuntu 18.04.2 LTS, also tried 19.10 development eoan edition. - Tried driver NVIDIA 390 + 430 from the repo, same result - Happens only on KDE Plasma desktop - Does not happen on GNOME desktop - Used the X server settings instead of the CLI Reproducibility: 75% Steps required: - Installing nvidia drivers on an optimus laptop - Rebooting - Select NVIDIA GPU with prime from Intel - Waiting some seconds - Opening NVIDIA X server settings again TWICE, increases a lot the chance of the freeze to happen (looks like it gets the nvidia module loaded even before the session logout) Bug observed: - Before the nvidia module gets loaded (I could type lsmod | grep nvidia fine and no module is loaded after the first 3 seconds) - When (presumably)
[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when desktop files are constantly created or deleted
Hello! Have same problem: With zsh as default, every time I press "Enter" in terminal there is 4s delay in whole system. I monitored CPU and CPU utilization is 100% every time I press enter in the terminal. So, the problem was that I removed useless folders in $HOME: Desktop, Music, Templates, etc. After, I noticed that value of $XDG_DESKTOP_DIR is "$HOME/" (But it was XDG_DESKTOP_DIR="$HOME/Desktop" before deletion of that directories) WORKAROUND: I created all that stuff again and changed ~/.config/user-dirs.dirs Now it looks like that: XDG_DESKTOP_DIR="$HOME/Desktop" XDG_DOWNLOAD_DIR="$HOME/Downloads" XDG_TEMPLATES_DIR="$HOME/Templates" XDG_PUBLICSHARE_DIR="$HOME/Public" XDG_DOCUMENTS_DIR="$HOME/Documents" XDG_MUSIC_DIR="$HOME/Music" XDG_PICTURES_DIR="$HOME/Pictures" XDG_VIDEOS_DIR="$HOME/Videos" Then re-login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1815550 Title: gnome-shell high memory and CPU usage when desktop files are constantly created or deleted Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons source package in Disco: In Progress Bug description: This *may* be an nvidia-specific problem, but the RSS of gnome-shell on my system grows without limit (over a couple of hours it's increased past 10G). At the same time, gnome-shell appears to become progressively less responsive. Restarting gnome-shell (via restart) drops shell RSS down to ~400MB and improves system responsiveness a bit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 4.20.0 Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 13:35:59 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1815550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
In 19.10 the problem seems to be gone, too. But I once whilst cleaning my keyboard got a glimpse on the locked screen => There might be a more subtle bug, still. -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup
Upgraded libreoffice from 1:6.1.6-0ubuntu0.18.10.2 to 1:6.1.6-0ubuntu0.18.10.3 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and verified that the crash is now resolved. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1798074 Title: LIbreoffice crashes on startup Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Status in libreoffice-l10n source package in Bionic: In Progress Status in libreoffice source package in Cosmic: Fix Committed Status in libreoffice-l10n source package in Cosmic: Fix Committed Bug description: [Impact] * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*' packages installed. * The fix is currently in LibreOffice 6.2.0+ on disco and eoan. [Test Case] 1. apt install cpdb-backend-gcp 2. run LibreOffice [Regression Potential] * We're backporting a patch that has already been applied to 6.2.0+ with no regression, so potential for regression here is low. * A combination of autopkgtests and manual testing should provide reasonable confidence that no regressions sneaked in. [Original Description] On starting up LibreOffice, it crashes. Starting from a terminal with just "libreoffice", I see the "general open a document" libreoffice window and a popup dialog titled "LibreOffice 6.0 Document Recovery", with text "Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. The following files will be recovered:" (and no files to be recovered are listed). Clicking "OK" on this dialog hides it and the general window, and then shows them both again; clicking OK on that dialog exits. LibreOffice does not start. Running "libreoffice --norestore" gives a stack trace: $ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5] /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97] /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca] I have tried entirely removing my profile, ~/.config/libreoffice , but
[Desktop-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack
tested on a Dell hybrid gfx laptop with Intel Skylake + AMD HAINAN, and everything seems fine. Tested glxgears, glmark2 on both GPU's I noticed that the daily image doesn't use HWE X stack, so this was tested on a bionic install ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831624] Re: ibus-cangjie in libreoffice cannot type Chinese character at end of line
Hi Bo-Yin, could you please show me the same character sequence working correctly on gedit / Text Editor, and not working on LibreOffice? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1831624 Title: ibus-cangjie in libreoffice cannot type Chinese character at end of line Status in libreoffice package in Ubuntu: Incomplete Bug description: I am using LibreOffice Version: 6.0.7.3, in particular I am using LibreOffice Writer. I am using ibus-cangjie to input Chinese. I cannot input any Chinese characters when I reach the end of a line on the screen. The expected behavior is that the typed Chinese character simply spills over to the next line and I can continue to type without a problem. If I reach the end of the line with half a space (of full-sized Chinese character) available, then I could insert a punctuation mark like 。 or 、 even if I use cangjie codes to input them (and then I can continue normally). if I reach the end of the line with no space available, then I cannot insert 。 or 、 when I use cangjie codes to input them (in the ibus- cangjie standard input table, 、 = XI) In neither case I can type a Chinese character like 日, all the typed characters simply disappears from the input queue and is not typed at all. Note that as I type I can see that the candidate Chinese characters according to the cangjie codes I input, they just don't get sent to the application. when I am at the end of the line, I can type as many spaces as I want and the problem of being unable to type a Chinese character persists. Finally, the bug only triggers when I am at the end of text; if I am inserting in the middle of text, even if I am at the linebreak, I can type normally and naturally. the attached screenshot shows where I am getting my cursor stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1831624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
I have a suggestion that if the ubuntu can backup itself when upgrade ,when if it crashed , I can restore it, now I have to rollback it to a very old version... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Jun 9 23:57:05 ubuntu spice-vdagent[1306]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jun 9 23:57:05 ubuntu dbus-daemon[670]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jun 9 23:57:05 ubuntu systemd[1]: Started PackageKit Daemon. Jun 9 23:57:06 ubuntu gnome-session[1032]: gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1 Jun 9 23:57:06 ubuntu gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1 Jun 9 23:57:06 ubuntu gnome-shell[1077]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files Jun 9 23:57:06 ubuntu gnome-shell[1077]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1477]: reference to undefined property "MetaWindowXwayland" Jun 9 23:57:06 ubuntu ModemManager[779]: Couldn't check support for device '/sys/devices/pci:00/:00:11.0/:02:01.0': not supported by any plugin Jun 9 23:57:06 ubuntu dbus-daemon[670]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.62' (uid=121 pid=1311 comm="/usr/lib/gnome-settings-daemon/gsd-color " label="unconfined") Jun 9 23:57:06 ubuntu gnome-session-binary[1032]: Entering running state Jun 9 23:57:06 ubuntu xbrlapi.desktop[1391]: openConnection: connect: 没有那个文件或目录 Jun 9 23:57:06 ubuntu xbrlapi.desktop[1391]: cannot connect to braille devices daemon brltty at :0 Jun 9 23:57:06 ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles... Jun 9 23:57:06 ubuntu colord[1392]: failed to get edid data: EDID length is too small Jun 9 23:57:06 ubuntu dbus-daemon[670]: [system] Successfully activated service 'org.freedesktop.ColorManager' Jun 9 23:57:06 ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles. Jun 9 23:57:06 ubuntu gsd-color[1311]: failed to get edid: unable to get EDID for output Jun 9 23:57:06 ubuntu gsd-color[1311]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output Jun 9 23:57:16 ubuntu systemd[1]: Created slice User Slice of hfu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Hi all, I have the same problems... I just upgraded my system... It freaks me out... journalctl -b | grep -E 'spice-vdagent|gnome-session' 6月 09 23:57:05 ubuntu spice-vdagent[1306]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 6月 09 23:57:06 ubuntu gnome-session[1032]: gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1 6月 09 23:57:06 ubuntu gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1 6月 09 23:57:06 ubuntu gnome-session-binary[1032]: Entering running state -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831827] Re: Update to 1.48
This bug was fixed in the package snapd-glib - 1.48-0ubuntu2 --- snapd-glib (1.48-0ubuntu2) eoan; urgency=medium * debian/libsnapd-qt1.symbols: - Add symbols that occurs in ppc64el builds -- Robert Ancell Fri, 07 Jun 2019 16:53:04 +1200 ** Changed in: snapd-glib (Ubuntu Eoan) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1831827 Title: Update to 1.48 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Triaged Status in snapd-glib source package in Bionic: Triaged Status in snapd-glib source package in Cosmic: Triaged Status in snapd-glib source package in Disco: Triaged Status in snapd-glib source package in Eoan: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1831827/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832173] nautilus crashed with SIGSEGV
Stacktrace: No stack. StacktraceSource: StacktraceTop: ThreadStacktrace: ** Tags added: apport-failed-retrace ** Tags removed: need-amd64-retrace -- 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/1832173 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: just rebooted with new kernel, no nautilus open, just firefox. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 08:39:04 2019 Disassembly: No registers. ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'162' b'org.gnome.nautilus.window-state' b'initial-size' b'(1141, 776)' b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-05-07 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190507) ProcCmdline: /usr/bin/nautilus --gapplication-service Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1832173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832173] [NEW] nautilus crashed with SIGSEGV
Public bug reported: just rebooted with new kernel, no nautilus open, just firefox. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 08:39:04 2019 Disassembly: No registers. ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'162' b'org.gnome.nautilus.window-state' b'initial-size' b'(1141, 776)' b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-05-07 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190507) ProcCmdline: /usr/bin/nautilus --gapplication-service Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash apport-failed-retrace eoan ** Information type changed from Private to Public -- 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/1832173 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: just rebooted with new kernel, no nautilus open, just firefox. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 08:39:04 2019 Disassembly: No registers. ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'162' b'org.gnome.nautilus.window-state' b'initial-size' b'(1141, 776)' b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-05-07 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190507) ProcCmdline: /usr/bin/nautilus --gapplication-service Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1832173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831341] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: unable to stat './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-draw
No problem :) Glad it’s sorted. ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1831341 Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: unable to stat './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis- drawing.png' (which I was about to install): Input/output error Status in libreoffice package in Ubuntu: Invalid Bug description: Distribution-upgrade was proposed on my BananaPi from Ubuntu 16.04.6 LTS to 18.04.2 LTS. I agreed, but during the process, the crash occured. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 Uname: Linux 3.4.39-BPI-M3-Kernel armv7l ApportVersion: 2.20.1-0ubuntu2.18 Architecture: armhf Date: Sat Jun 1 18:32:16 2019 DuplicateSignature: package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial6 Unpacking ure (5.1.6~rc2-0ubuntu1~xenial7) over (5.1.6~rc2-0ubuntu1~xenial6) ... dpkg: error processing archive /var/cache/apt/archives/ure_5.1.6~rc2-0ubuntu1~xenial7_armhf.deb (--unpack): unable to stat './usr/share/maven-repo/org/libreoffice/jurt/5.1.6/jurt-5.1.6.jar' (which I was about to install): Input/output error ErrorMessage: unable to stat './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' (which I was about to install): Input/output error PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: libreoffice Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: unable to stat './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' (which I was about to install): Input/output error UpgradeStatus: Upgraded to xenial on 2019-06-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1831341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp