[Desktop-packages] [Bug 2051303] Re: T14s Gen4 Intel under 23.10 started locking up hard
** Description changed:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously,
without high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
- I accept updates when they arrive. Recently it's been telling me to do
- firmware updates, too.
+ Other context:
+ I accept OS updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything
much on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
- virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
- virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
+ virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
+ virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
- Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
-Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
+ Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
+ Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
InstallationDate: Installed on 2022-09-02 (510 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
dmi.bios.date: 10/30/2023
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N3PET20W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21F6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
dmi.product.family: ThinkPad T14s Gen 4
dmi.product.name: 21F6CTO1WW
dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
dmi.product.version: ThinkPad T14s Gen 4
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
** Summary changed:
- T14s Gen4 Intel under 23.10 started locking up hard
+ T14s Gen4 Intel under 23.10 started freezing / locking up hard
--
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/2051303
Title:
T14s Gen4 Intel under 23.10 started freezing / locking up hard
Status in xorg package in Ubuntu:
New
Bug description:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously,
without high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
Other context:
I accept OS updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything
much on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
[Desktop-packages] [Bug 2051303] Re: T14s Gen4 Intel under 23.10 started locking up hard
The last crash before I reported this was just before hard-rebooting
around time 2024-01-25 19:30
--
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/2051303
Title:
T14s Gen4 Intel under 23.10 started locking up hard
Status in xorg package in Ubuntu:
New
Bug description:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously,
without high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
I accept updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything
much on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
InstallationDate: Installed on 2022-09-02 (510 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
dmi.bios.date: 10/30/2023
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N3PET20W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21F6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
dmi.product.family: ThinkPad T14s Gen 4
dmi.product.name: 21F6CTO1WW
dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
dmi.product.version: ThinkPad T14s Gen 4
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2051303/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051303] [NEW] T14s Gen4 Intel under 23.10 started locking up hard
Public bug reported:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously, without
high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
I accept updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything much
on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
InstallationDate: Installed on 2022-09-02 (510 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
dmi.bios.date: 10/30/2023
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N3PET20W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21F6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
dmi.product.family: ThinkPad T14s Gen 4
dmi.product.name: 21F6CTO1WW
dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
dmi.product.version: ThinkPad T14s Gen 4
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze mantic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2051303
Title:
T14s Gen4 Intel under 23.10 started locking up hard
Status in xorg package in Ubuntu:
New
Bug description:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously,
without high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
I accept updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything
much on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse:
[Desktop-packages] [Bug 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken
I believe this issue is affecting me as well. The updater could not calculate the update, and asked me to use PPA-Purge. Main.log shows the following error: 2023-12-18 11:51:29,328 ERROR Dist-upgrade failed: 'Broken packages after upgrade: gnome-remote-desktop, gnome-shell' 2023-12-18 11:51:29,344 DEBUG abort called My apt.log is attached. ** Attachment added: "apt.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+attachment/5730448/+files/apt.log -- 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/2043395 Title: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken Status in gnome-shell package in Ubuntu: Confirmed Bug description: Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal based** install: 2023-11-10 07:03:16,578 DEBUG nvidiaUpdate() 2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new 2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache 2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache 2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with 2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35 2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36 2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after upgrade: gnome-remote-desktop, gnome-shell' 2023-11-10 07:03:20,564 DEBUG abort called To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
I am not the original poster, but I had all of the same symptoms. I
manually tried the 45.2-0ubuntu1 version of mutter mentioned above, and
the tablet works now!
Tested Krita, Inkscape, Blender (and general system navigation)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in mutter package in Ubuntu:
Fix Committed
Status in mutter source package in Mantic:
Fix Committed
Bug description:
Impact
--
Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11
sessions
Test Case
-
One of the people affected by this issue will verify whether their Wacom
tablet is working noticably better with the upgraded Mutter packages
What Could Go Wrong
---
The fix for this issue is included in upstream's mutter 45.2 release so
please see bug 2043000 as the master bug for this upgrade
Original Bug Report
---
Tablet seems to work until I open Krita (as I could read on Internet, it may
be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when
it comes to click action it doesn't work and any further action with
mouse is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
[Desktop-packages] [Bug 2044654] [NEW] No debugging symbols found in libgdk-3.so.0
Public bug reported: Attach gdb to a running yelp process! (gdb) share libgdk Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0... (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 13:11:15 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2044654 Title: No debugging symbols found in libgdk-3.so.0 Status in gtk+3.0 package in Ubuntu: New Bug description: Attach gdb to a running yelp process! (gdb) share libgdk Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0... (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 13:11:15 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2044654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
Can someone tell me how to know when this fix hits the normal updates? Or how long this normally takes? I don't want to mess with editing files if I can help it, or attempting to not mess up my system by trying to include proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error
[Desktop-packages] [Bug 1093765]
AFAIK, the original reporter's preference wasn't ever designed this way so this is an enhancement request. Also, nothing changed in: Version: 7.5.0.3 (AARCH64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Mac OS X 13.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Latest Office still behaves the same way as noted in https://bugs.documentfoundation.org/show_bug.cgi?id=58070#c2 : Microsoft Word for Microsoft 365 MSO (Version 2212 Build 16.0.15928.20278) 64-bit -- 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/1093765 Title: [upstream] switching paragraph style changes character orientation Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:4.0.2-0ubuntu1 Candidate: 1:4.0.2-0ubuntu1 Version table: *** 1:4.0.2-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/+attachment/3688368/+files/test-bug1093765.doc && lowriter --nologo test-bug1093765.doc is select all -> change combo box Apply Style from Text Body to Heading 1 and the text style changes, preserving the character order. 4) What happens instead is: (Example text=) טקסט לדוגמה changes to: טקסט לדוגמה (=Example text) Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit) changes it to: =)טקסט לדוגמהExample text( ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-core 1:3.6.2~rc2-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Wed Dec 26 11:20:42 2012 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-10-19 (67 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1093765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 892476]
As the original reporter, I accept this being root caused to a documentation issue now fixed by: https://bugs.documentfoundation.org/show_bug.cgi?id=43107#c27 I wouldn't have filed this report if it had been documented as such to begin with. -- 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/892476 Title: [Upstream] Regular expression "\n" in replace field inputs "\n" instead of paragraph break Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description:Ubuntu 11.10 Release:11.10 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.4.4-0ubuntu1~ppa1 Candidate: 1:3.4.4-0ubuntu1~ppa1 Version table: *** 1:3.4.4-0ubuntu1~ppa1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Calc is when one of the cells contains a line break -> Edit -> Find and Replace... -> in the "Search for" drop down \n -> in the "Replace with" drop down \n -> Regular expression button checked is the line break is replaced with a paragraph break as noted in http://help.libreoffice.org/Common/List_of_Regular_Expressions 4) What happens instead is the line break is replaced with the characters \n ProblemType: BugDistroRelease: Ubuntu 11.10 Package: libreoffice-calc 1:3.4.3-3ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 19 13:02:28 2011 EcryptfsInUse: YesInstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-10-16 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/892476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 892476] Re: [Upstream] Regular expression "\n" in replace field inputs "\n" instead of paragraph break
Shahar Or, as per upstream, the root cause was a documentation issue that has since been clarified: https://help.libreoffice.org/7.5/en-US/text/shared/01/0211.html?=SHARED=MAC ** Changed in: libreoffice (Ubuntu) Status: Triaged => Fix Released -- 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/892476 Title: [Upstream] Regular expression "\n" in replace field inputs "\n" instead of paragraph break Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description:Ubuntu 11.10 Release:11.10 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.4.4-0ubuntu1~ppa1 Candidate: 1:3.4.4-0ubuntu1~ppa1 Version table: *** 1:3.4.4-0ubuntu1~ppa1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Calc is when one of the cells contains a line break -> Edit -> Find and Replace... -> in the "Search for" drop down \n -> in the "Replace with" drop down \n -> Regular expression button checked is the line break is replaced with a paragraph break as noted in http://help.libreoffice.org/Common/List_of_Regular_Expressions 4) What happens instead is the line break is replaced with the characters \n ProblemType: BugDistroRelease: Ubuntu 11.10 Package: libreoffice-calc 1:3.4.3-3ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 19 13:02:28 2011 EcryptfsInUse: YesInstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-10-16 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/892476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 462564] Re: [Upstream] Deleting a column in Writer deletes whole table
Confirmed resolved in 7.5.x. ** Changed in: libreoffice (Ubuntu) Status: Triaged => Fix Released -- 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/462564 Title: [Upstream] Deleting a column in Writer deletes whole table Status in LibreOffice: Fix Released Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Fix Released Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt && lowriter -nologo test.odt is when one highlights the second column of the table -> secondary clicks -> Column -> Delete is only that column is deleted. Please see movie for more details: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv 4) What happens instead is the whole table is deleted. Reproducible in: lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status WORKAROUND: Split the table then delete the column. WORKAROUND: Use Word via WINE. Microsoft Office Word 2003 (11.5604.6505) apt-cache policy wine1.3 wine1.3: Installed: 1.3.28-0ubuntu1~ppa1~natty1 Candidate: 1.3.28-0ubuntu1~ppa1~natty1 Version table: *** 1.3.28-0ubuntu1~ppa1~natty1 0 500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status 1.3.15-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages ProblemType: Bug Architecture: amd64 Date: Wed Oct 28 09:43:20 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/462564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
I have the same issue as Samuel. I can connect to the hotspot just fine, but the connected devices don't have access to internet. Strangely enough I did find one workaround that fixes the problem for me in this answer: https://askubuntu.com/a/1444778 The -999 priority doesn't seem to matter, but if I set the hotspot to start automatically and then reboot, connected devices can access the internet. Also, if the hotspot is started automatically I can stop and re-start it and things still work. -- 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/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979891] Re: Firefox becomes unusable when adjusting window size
Done! https://bugzilla.mozilla.org/show_bug.cgi?id=1790527 ** Bug watch added: Mozilla Bugzilla #1790527 https://bugzilla.mozilla.org/show_bug.cgi?id=1790527 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1979891 Title: Firefox becomes unusable when adjusting window size Status in firefox package in Ubuntu: New Bug description: OS version: Ubuntu 22.04 LTS Firefox version: 1:1snap1-0ubuntu2 - 101.0.1 (64-bit) Sometimes when I adjust the size of a Firefox window, that window becomes messed up: the contents don't fill the window, not all the controls are visible, and clicks are offset, so if I click on one spot, the window behaves as if I clicked on a different spot (so it's impossible to use Firefox in that window anymore). I seem to remember being able to fix this by dragging and dropping the window onto a different monitor or workspace in the GNOME Activities view, but I'm currently experiencing the problem and that is not helping. I took a screenshot of what's currently going on (attached) which happened when I tried to maximize the window. This is on a laptop with an external monitor that I'm using in portrait mode, via a USB-C connection that's converted to HDMI. I had plugged in to the external monitor a few minutes before this happens, and plugging in or possibly unplugging seems to make this bug more likely. This is a relatively new problem, starting within the last few weeks. (Maybe after I switched to the snap version of Firefox? I guess that was when I upgraded from the previous LTS version of Ubuntu.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 25 15:23:13 2022 DistUpgraded: 2022-05-27 14:03:05,108 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-39-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-40-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: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-11-23 (1309 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-27 (29 days ago) dmi.bios.date: 03/22/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/22/2022:br1.19:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1979891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979891] Re: Firefox becomes unusable when adjusting window size
Still happening with version 103.0.02. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1979891 Title: Firefox becomes unusable when adjusting window size Status in firefox package in Ubuntu: New Bug description: OS version: Ubuntu 22.04 LTS Firefox version: 1:1snap1-0ubuntu2 - 101.0.1 (64-bit) Sometimes when I adjust the size of a Firefox window, that window becomes messed up: the contents don't fill the window, not all the controls are visible, and clicks are offset, so if I click on one spot, the window behaves as if I clicked on a different spot (so it's impossible to use Firefox in that window anymore). I seem to remember being able to fix this by dragging and dropping the window onto a different monitor or workspace in the GNOME Activities view, but I'm currently experiencing the problem and that is not helping. I took a screenshot of what's currently going on (attached) which happened when I tried to maximize the window. This is on a laptop with an external monitor that I'm using in portrait mode, via a USB-C connection that's converted to HDMI. I had plugged in to the external monitor a few minutes before this happens, and plugging in or possibly unplugging seems to make this bug more likely. This is a relatively new problem, starting within the last few weeks. (Maybe after I switched to the snap version of Firefox? I guess that was when I upgraded from the previous LTS version of Ubuntu.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 25 15:23:13 2022 DistUpgraded: 2022-05-27 14:03:05,108 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-39-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-40-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: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-11-23 (1309 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-27 (29 days ago) dmi.bios.date: 03/22/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/22/2022:br1.19:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1979891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
For those of us who used the workaround method by @nfalse in comment 22, how and when do we undo this workaround so as to be safe and benefit from the released fix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Fix Released Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
Whoops -- actually, my enterprise network was a university's main wifi (wpa.mcgill.ca), not eduroam. I propose to generalize the title of this bug by dropping eduroam or changing it to (e.g. eduroam) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
On a Thinkpad X230 I had this problem after upgrading to 22.04. The recipe in comment 23 by nfalse solved the problem for me. Thank you (though this is only a temporary workaround, given its use of "UnsafeLegacyRenegotiation") -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963836] [NEW] package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pi
Public bug reported: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 pipewire-pulse: Installed: 0.3.47-3~ubuntu22.04 Candidate: 0.3.48-1ubuntu1 Version table: 0.3.48-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages *** 0.3.47-3~ubuntu22.04 500 500 http://ppa.launchpad.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 22.04 Package: pipewire-pulse 0.3.47-3~ubuntu22.04 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Mar 6 20:05:39 2022 DpkgTerminalLog: Preparing to unpack .../00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb ... Unpacking pipewire-pulse (0.3.48-1ubuntu1) over (0.3.47-3~ubuntu22.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-tiBpp8/00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 DuplicateSignature: package:pipewire-pulse:0.3.47-3~ubuntu22.04 Unpacking pipewire-pulse (0.3.48-1ubuntu1) over (0.3.47-3~ubuntu22.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-tiBpp8/00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 ErrorMessage: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 InstallationDate: Installed on 2022-02-13 (20 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220116) Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu1 apt 2.3.15build1 SourcePackage: pipewire Title: package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check package-conflict third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1963836 Title: package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 Status in pipewire package in Ubuntu: New Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 pipewire-pulse: Installed: 0.3.47-3~ubuntu22.04 Candidate: 0.3.48-1ubuntu1 Version table: 0.3.48-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages *** 0.3.47-3~ubuntu22.04 500 500 http://ppa.launchpad.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 22.04 Package: pipewire-pulse 0.3.47-3~ubuntu22.04 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Mar 6 20:05:39 2022 DpkgTerminalLog: Preparing to unpack .../00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb ... Unpacking pipewire-pulse (0.3.48-1ubuntu1) over (0.3.47-3~ubuntu22.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-tiBpp8/00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 DuplicateSignature: package:pipewire-pulse:0.3.47-3~ubuntu22.04 Unpacking pipewire-pulse (0.3.48-1ubuntu1) over (0.3.47-3~ubuntu22.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-tiBpp8/00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 ErrorMessage: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 InstallationDate: Installed on 2022-02-13 (20 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220116) Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonDetails: N/A
[Desktop-packages] [Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.
This seems to be the same as https://bugs.launchpad.net/ubuntu/+source/evolution-data- server/+bug/1952107 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. Status in Evolution: Unknown Status in Ubuntu MATE: New Status in evolution package in Ubuntu: New Status in evolution-data-server package in Ubuntu: New Bug description: I'm running Ubuntu MATE 20.04; I stick with LTS for this system. I use Evolution for email and calendar. Tonight I got this message: = Failed to connect address book “guy.rouill...@gmail.com : Contacts” Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. == I went to report this on the GNOME bug tracker and found this existing issue: https://gitlab.gnome.org/GNOME/evolution/-/issues/1655 That issue was closed with this comment: == "Andre Klapper Issue found on latest Evolution in Debian 11 (3.38.3-1) That version is ancient and not maintained anymore by GNOME developers. Feel free to file a bug report in your distribution's issue tracker." The version in MATE is even older: 3.36.5-0ubuntu1 So apparently Evolution in MATE is currently not functional. We need to update to a later release. I will update to the newer LTS of MATE when it is released. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-10-05 (1212 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: evolution-data-server PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Tags: third-party-packages focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 631045] Re: [Upstream] Unable to print slide selection properly in Impress
Confirmed resolved in: apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:7.2.2-0ubuntu0.21.10.1 Candidate: 1:7.2.2-0ubuntu0.21.10.1 Version table: *** 1:7.2.2-0ubuntu0.21.10.1 500 500 http://us.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.2.1-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- 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/631045 Title: [Upstream] Unable to print slide selection properly in Impress Status in LibreOffice: Fix Released Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org Binary package hint: libreoffice 1) Natty: lsb_release -rd Description: Ubuntu Natty (development branch) Release: 11.04 Maverick: lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 2) Natty: apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.3.1-1ubuntu5 Candidate: 1:3.3.1-1ubuntu5 Version table: *** 1:3.3.1-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status Maverick: apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.3.1-1ubuntu3~maverick1 Candidate: 1:3.3.1-1ubuntu3~maverick1 Version table: *** 1:3.3.1-1ubuntu3~maverick1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when performs at the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/631045/+attachment/1547180/+files/slideshow.odp && loimpress -nologo slideshow.odp click Slide Sorter tab -> hold Ctrl and click slides 3, and 35 (1 was already highlighted) -> Ctrl+P -> click Selection radio button -> click Print button that pages 1, 3, and 35 are printed. 4) What happens instead is that only page 1 prints. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openoffice.org-impress 1:3.2.0-7ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Sun Sep 5 14:32:57 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openoffice.org To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/631045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915059] Re: [Upstream] Compare Document highlighting unchanged words as changed
Confirmed Fix Released in: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:7.2.2-0ubuntu0.21.10.1 Candidate: 1:7.2.2-0ubuntu0.21.10.1 Version table: *** 1:7.2.2-0ubuntu0.21.10.1 500 500 http://us.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.2.1-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/915059 Title: [Upstream] Compare Document highlighting unchanged words as changed Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671476/+files/versions.zip && file-roller -h versions.zip && cd versions && lowriter -nologo version1.odt Edit -> Compare Document -> version2.odt -> Insert button is under Actions regarding the first Deletion top to bottom, one tan hyphen is shown to the left of "LibreOffice Writer" and "LibreOffice Writer" is not marked tan with a tan underline. An example of how it should look may be found via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671477/+files/versions- space.zip && file-roller -h versions-space.zip && cd versions-space && lowriter -nologo version1-space.odt Edit -> Compare Document -> version2-space.odt -> Insert button 4) What happens instead is the hyphen to the left of "LibreOffice Writer" is not shown and "LibreOffice Writer" is marked tan with a tan underline. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/915059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 461128] Re: [Upstream] Draw shifts, breaks apart, and merges icons importing SVG
Confirmed fixed in: apt-cache policy libreoffice-draw libreoffice-draw: Installed: 1:7.2.2-0ubuntu0.21.10.1 Candidate: 1:7.2.2-0ubuntu0.21.10.1 Version table: *** 1:7.2.2-0ubuntu0.21.10.1 500 500 http://us.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.2.1-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- 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/461128 Title: [Upstream] Draw shifts, breaks apart, and merges icons importing SVG Status in LibreOffice: Invalid Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Fix Released Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 2) apt-cache policy libreoffice-draw libreoffice-draw: Installed: 1:3.4.2-2ubuntu3 Candidate: 1:3.4.2-2ubuntu3 Version table: *** 1:3.4.2-2ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Draw via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887683/+files/gliffy- biznet.svg && lodraw -nologo gliffy-biznet.svg is the file looks as it does in Inkscape. 4) What happens instead is all the icons are shifed around as shown by a screenshot: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887688/+files/gliffy- biznet-ooomangle.png ProblemType: Bug Architecture: amd64 Date: Mon Oct 26 15:17:08 2009 DistroRelease: Ubuntu 9.10 Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 XsessionErrors: (polkit-gnome-authentication-agent-1:3239): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (npviewer.bin:4074): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/461128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923459] Re: evince doesn't show filename or PDF title on the title bar
This is reported at https://gitlab.gnome.org/GNOME/evince/-/issues/1583 (thanks to Michaël Berteaux @Mikenux at https://gitlab.gnome.org/GNOME/evince/-/issues/996). The bug is solved in Evince 40.2, and it looks like Ubuntu 21.10 has Evince 40.4-2, which would include the fix. However, this is worth backporting, please: it's really a weird nuisance for one of the core applications on a desktop computer. ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #1583 https://gitlab.gnome.org/GNOME/evince/-/issues/1583 ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #996 https://gitlab.gnome.org/GNOME/evince/-/issues/996 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1923459 Title: evince doesn't show filename or PDF title on the title bar Status in evince package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 21.04, evince does not show any info in the title bar. Previously, it showed the filename and the PDF title. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evince 40.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 10:42:29 2021 InstallationDate: Installed on 2020-11-04 (159 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: evince UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1923459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944746] [NEW] LibreOffice from Ubuntu Store/snaps broken GNOME integration for remote smb shares
Public bug reported: 1) lsb_release -rd Description:Ubuntu 21.04 Release:21.04 2) Name Version RevTracking Publisher Notes snap list | grep libreoffice libreoffice 7.2.1.2 235latest/edge canonical* - apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 Candidate: 3.38.4-1ubuntu3~21.04.1 Version table: *** 3.38.4-1ubuntu3~21.04.1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.4-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 3) What I expected to happen is using any version of LibreOffice snaps from Ubuntu Software app (i.e. https://snapcraft.io/libreoffice ) works as it does as if I used the default install of libreoffice. Specifically, when I open the GNOME Files program via the icon on the bar on the left, I have an smb share already added via "Other Locations". When I use the default libreoffice install version as per below, when I attempt to open a file in Libreoffice Calc, the share is visible and I'm able to open files, edit, save, close, etc.: apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.1.6-0ubuntu0.21.04.1 Version table: 1:7.1.6-0ubuntu0.21.04.1 500 (phased 70%) 500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/universe amd64 Packages 1:7.1.2~rc2-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 4) However, when I completely remove all things libreoffice-* via command line, then install the snap version, the smb share is not visible. It's confirmed all packages associated with default install are removed, and only the snap is installed. I've tried completely removing each snap and trying a different version (e.g. stable, candidate, edge) but it's the same problem. I'm guessing it's something borked with the libreoffice-gnome integration between the snap and the GNOME environment but that's a wild guess. I tried the snap package as the default install Draw kept crashing opening a particular file, and was hoping to work around it by installing later snap version. WORKAROUND: Use default install of LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 21.04 ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 23 08:58:30 2021 InstallationDate: Installed on 2021-08-25 (28 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: libreoffice 7.2.1.2 (latest/edge) SnapSource: ubuntu/+source/libreoffice UpgradeStatus: Upgraded to hirsute on 2021-09-20 (3 days ago) ** Affects: libreoffice (Ubuntu) Importance: Low Status: Triaged ** Tags: amd64 apport-bug hirsute snap testcase -- 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/1944746 Title: LibreOffice from Ubuntu Store/snaps broken GNOME integration for remote smb shares Status in libreoffice package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 2) Name Version RevTracking Publisher Notes snap list | grep libreoffice libreoffice 7.2.1.2 235 latest/edge canonical* - apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 Candidate: 3.38.4-1ubuntu3~21.04.1 Version table: *** 3.38.4-1ubuntu3~21.04.1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.4-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 3) What I expected to happen is using any version of LibreOffice snaps from Ubuntu Software app (i.e. https://snapcraft.io/libreoffice ) works as it does as if I used the default install of libreoffice. Specifically, when I open the GNOME Files program via the icon on the bar on the left, I have an smb share already added via "Other Locations". When I use the default libreoffice install version as per below, when I attempt to open a file in Libreoffice Calc, the share is visible and I'm able to open files, edit, save, close, etc.: apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.1.6-0ubuntu0.21.04.1 Version table: 1:7.1.6-0ubuntu0.21.04.1 500 (phased 70%)
[Desktop-packages] [Bug 1940757] [NEW] Keyboard/configuration
Public bug reported: have-no-space-bar.--no-#six--no-esc--and-other-key--functions--when-i- instaled-Kubontu-20.four ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 21 22:47:59 2021 DistUpgraded: 2020-10-11 03:03:06,479 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff10] Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff10] InstallationDate: Installed on 2018-12-30 (965 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite A505 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=82ca8cbd-36b7-461a-b546-3b3631865996 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-11 (314 days ago) dmi.bios.date: 05/25/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.80:bd05/25/2010:svnTOSHIBA:pnSatelliteA505:pvrPSAT0U-00M001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite A505 dmi.product.sku: Montevina_Fab dmi.product.version: PSAT0U-00M001 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Jul 24 17:26:30 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1940757 Title: Keyboard/configuration Status in xorg package in Ubuntu: New Bug description: have-no-space-bar.--no-#six--no-esc--and-other-key--functions--when-i- instaled-Kubontu-20.four ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 21 22:47:59 2021 DistUpgraded: 2020-10-11 03:03:06,479 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff10] Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff10] InstallationDate: Installed on 2018-12-30 (965 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite A505 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Desktop-packages] [Bug 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 I'm having a similar issue on Ubuntu 20.04. Currently, every time that I reboot I'm unable to login. I just get a black screen after logging in. I have noticed that if I first delete the contents of .config and .local I'm able to log in. However, obviously, all of my configurations and customizations are then gone. My workaround lately has been to clear those directories, login, logout, copy a backup of those directories to the active directories and then log back in. It's a pain, but for some reason it works. Otherwise, 100% of the time after a reboot I can't access the desktop. -- 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/1870779 Title: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060) Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login right after installation, but after a few reboots a black screen is displayed after login. I'm able to switch to a tty and tried to collect information with ubuntu-bug, but I am not sure if that help. I'm happy to provide further information if needed. I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the same. 19.10 works without any problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Sat Apr 4 14:05:01 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7] InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5675 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.7 dmi.board.name: 0477DV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.7 dmi.modalias: dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7: dmi.product.family: Inspiron dmi.product.name: Inspiron 5675 dmi.product.sku: 07EE dmi.product.version: 1.3.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938978] [NEW] nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid)
Public bug reported: ProblemType: Package DKMSBuildLog: DKMS make.log for nvidia-340-340.108 for kernel 5.11.0-25-generic (x86_64) to. 05. aug. 06:23:28 +0200 2021 NVIDIA: calling KBUILD... make[1]: Entering directory '/usr/src/linux-headers-5.11.0-25-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it ."; \ echo >&2 ; \ /bin/false) make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-340/340.108/build \ single-build= \ need-builtin=1 need-modorder=1 cc -Wp,-MMD,/var/lib/dkms/nvidia-340/340.108/build/.nv.o.d -nostdinc -isyste m /usr/lib/gcc/x86_64-linux-gnu/9/include -I./arch/x86/include -I./arch/x86/inc lude/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/gener ated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/k...etc /var/crash$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 06:24:36 2021 InstallationDate: Installed on 2021-05-01 (95 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1938978 Title: nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: ProblemType: Package DKMSBuildLog: DKMS make.log for nvidia-340-340.108 for kernel 5.11.0-25-generic (x86_64) to. 05. aug. 06:23:28 +0200 2021 NVIDIA: calling KBUILD... make[1]: Entering directory '/usr/src/linux-headers-5.11.0-25-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2;\ echo >&2 " ERROR: Kernel configuration is invalid.";\ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it ."; \ echo >&2 ; \ /bin/false) make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-340/340.108/build \ single-build= \ need-builtin=1 need-modorder=1 cc -Wp,-MMD,/var/lib/dkms/nvidia-340/340.108/build/.nv.o.d -nostdinc -isyste m /usr/lib/gcc/x86_64-linux-gnu/9/include -I./arch/x86/include -I./arch/x86/inc lude/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/gener ated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/k...etc /var/crash$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 06:24:36 2021 InstallationDate: Installed on 2021-05-01 (95 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Desktop-packages] [Bug 1493921] Re: X server fails to set correct mode on resume from sleep (NVIDIA: Setting a mode on head 0 failed: An invalid mode was requested)
Steve, please open a new report. Thanks! -- 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/1493921 Title: X server fails to set correct mode on resume from sleep (NVIDIA: Setting a mode on head 0 failed: An invalid mode was requested) Status in xorg package in Ubuntu: Won't Fix Bug description: Using a really picky Dell P2415Q monitor through DP->mDP (displayport -> mini displayport) cable, nvidia binary driver version 352.30-0ubuntu1. This is not a laptop, so the Intel integrated VGA is disabled. (No other cards in sysfs.) Really nasty bug, as every time all the running applications detect that the X server went away and exit, logind terminates the session culling everyone, and so on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.30 Tue Jul 21 18:53:45 PDT 2015 GCC version: gcc version 5.2.1 20150825 (Ubuntu 5.2.1-15ubuntu5) ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Wed Sep 9 17:56:53 2015 DistUpgraded: 2014-08-06 01:18:55,244 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3614] MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fba348ec-fc7c-4c7f-b78b-026be76c4568 ro crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2014-08-05 (399 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F18 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF18:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Sep 9 15:10:08 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech G100s Optical Gaming Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1493921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851134] Re: setting custom keyboard shortcut fails for certain keys
I reported it here: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1397 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1397 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1397 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1851134 Title: setting custom keyboard shortcut fails for certain keys Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I click on settings in menu or press my settings icon key (above F9 key on Lenovo T450s keyboard). Navigate to "Keyboard Shortcuts". Scroll to bottom to press "+" to add a custom shortcut. Define function, then click on "Set Shortcut...". Then I press the "Explorer" key, which is above the F12 on my keyboard. Instead of setting the shortcut, it brings up a file browser. I can set my shortcut to shift-Explorer, but not to Explorer. This is even though no other keyboard shortcut listed is set to this key "Explorer". The "Home folder" Launcher is set to "Disabled". Changing the "Home folder" launcher keyboard shortcut to something else does not help. Instead, once I click on "set Shortcut", it should listen to whatever I choose. The same problem exists for the "Search" key. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 09:29:28 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (282 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-10-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931524] [NEW] package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error e
Public bug reported: Situation arose after trying to install RoseGarden and LilyPond on this newly upgraded system. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: texlive-binaries 2020.20200327.54578-7 Uname: Linux 5.4.73v64 aarch64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Jun 10 00:14:07 2021 DuplicateSignature: package:texlive-binaries:2020.20200327.54578-7 Setting up texlive-binaries (2020.20200327.54578-7) ... update-alternatives: error: unable to open file '/var/lib/dpkg/alternatives/my.cnf': No such device or address dpkg: error processing package texlive-binaries (--configure): installed texlive-binaries package post-installation script subprocess returned error exit status 2 ErrorMessage: installed texlive-binaries package post-installation script subprocess returned error exit status 2 ImageMediaBuild: 20201022 Python3Details: /usr/bin/python3.9, Python 3.9.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: texlive-bin Title: package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to hirsute on 2021-06-09 (0 days ago) ** Affects: texlive-bin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image hirsute raspi-image -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-bin in Ubuntu. https://bugs.launchpad.net/bugs/1931524 Title: package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error exit status 2 Status in texlive-bin package in Ubuntu: New Bug description: Situation arose after trying to install RoseGarden and LilyPond on this newly upgraded system. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: texlive-binaries 2020.20200327.54578-7 Uname: Linux 5.4.73v64 aarch64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Jun 10 00:14:07 2021 DuplicateSignature: package:texlive-binaries:2020.20200327.54578-7 Setting up texlive-binaries (2020.20200327.54578-7) ... update-alternatives: error: unable to open file '/var/lib/dpkg/alternatives/my.cnf': No such device or address dpkg: error processing package texlive-binaries (--configure): installed texlive-binaries package post-installation script subprocess returned error exit status 2 ErrorMessage: installed texlive-binaries package post-installation script subprocess returned error exit status 2 ImageMediaBuild: 20201022 Python3Details: /usr/bin/python3.9, Python 3.9.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: texlive-bin Title: package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to hirsute on 2021-06-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1931524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929209] [NEW] external monitor goes black for several seconds at a time, randomly
Public bug reported: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. There are other related behaviours reported in the past, but I am running Ubuntu 20.10. I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Description changed: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. - There are other related behaviours reported in the past. - I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. + There are other related behaviours reported in the past, but I am running Ubuntu 20.10. + I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo HD Graphics 5500 [17aa:5036] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine:
[Desktop-packages] [Bug 1923381] Re: [Lenovo ThinkPad T450s] regression: no display when waking from suspend
I followed your instructions for prevboot.rxt, though I removed from it a bunch of lines like (no idea what those are) May 09 06:30:36 T450s-low tracker-miner-f[2128]: Could not enumerate container / directory 'file:///home/meuser/Music/somemusicfolder, Error opening directory '/home/meuser/Music/somemusicfolder/somefile': Permission denied Also, there's nothing in /var/crash Also, the most recent listing in the whoopsie page was from January. Thank you. ** Attachment added: "sudo journalctl -b-1 | grep -v Music" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923381/+attachment/5495891/+files/prevboot-withoutSomeMusiccomplaints.txt -- 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/1923381 Title: [Lenovo ThinkPad T450s] regression: no display when waking from suspend Status in xorg-server package in Ubuntu: Incomplete Bug description: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927341] [NEW] gedit does not restore sessions
Public bug reported: extension "session saver" is installed I have a gedit session running with two open files. Then I close gedit and start it again. Instead of loading the previous session with the two open files, gedit starts a new, empty text file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 6 18:23:20 2021 InstallationDate: Installed on 2020-04-25 (375 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1927341 Title: gedit does not restore sessions Status in gedit package in Ubuntu: New Bug description: extension "session saver" is installed I have a gedit session running with two open files. Then I close gedit and start it again. Instead of loading the previous session with the two open files, gedit starts a new, empty text file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 6 18:23:20 2021 InstallationDate: Installed on 2020-04-25 (375 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1927341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926016] [NEW] package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.
Public bug reported: trying to reinstall this package after accidental removal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 24 10:40:53 2021 ErrorMessage: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.1.9-9805 InstallationDate: Installed on 2020-11-09 (166 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.1.9-9805 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1926016 Title: package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.1.9-9805 Status in libreoffice package in Ubuntu: New Bug description: trying to reinstall this package after accidental removal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 24 10:40:53 2021 ErrorMessage: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.1.9-9805 InstallationDate: Installed on 2020-11-09 (166 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.1.9-9805 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1926016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923381] [NEW] regression: no display when waking from suspend
Public bug reported: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1923381 Title: regression: no display when waking from suspend Status in xorg package in Ubuntu: New Bug description: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu
[Desktop-packages] [Bug 1234887] Re: [FFE] Update NetworkManager to 0.9.8.4
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => christopher wayne hess (hess8519) -- 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/1234887 Title: [FFE] Update NetworkManager to 0.9.8.4 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Saucy: Invalid Status in network-manager source package in Trusty: Fix Released Bug description: Let's update NetworkManager to 0.9.8.4; which is a bugfix release; minor version number change. Most specifically, multiple fixes for use-after-free and memory leaks, along with fixes for other possible crashes. Full list of commits is below. a450929 release: bump version to 0.9.8.4 578b7c1 release: update NEWS 4a4d58a libnm-glib: bump soname for added functions a00701d libnm-glib: fix annotations again: 0.9.8.4, not 0.9.8.6 46345e0 libnm-glib: change the "Since: 0.9.10" annotations to "Since: 0.9.8.6" 1d6947a ifcfg-rh: fix tests 90c957c build: fix builddir != srcdir when building D-Bus API spec HTML 72e3dd7 core: fix handling of ActiveConnections on Policy dispose() 65590de libnm-util: accept old-style UUIDs as valid a10dea3 agents: don't make method calls with a destroyed proxy 52b3810 core: fix NMPolicy/NMManager refcounting 59c165a build: don't use g_clear_pointer() 636387f trivial: nm_connectivity_check_async() returns void -> use g_return_if_fail() 226b9b1 core: fix warning about unused variable 299081e libnm-glib: Add NMClient:primary-connection and :activating-connection 61a81d1 core: add NMManager:primary-connection and :activating-connection 2489018 core: make NMPolicy a GObject 693112f libnm-glib: support new connectivity property/methods d34e77c core: provide additional network connectivity information a5eeeb7 core: improve NMManager:state transitions with connectivity checking 0d2ccfd core: add LOGD_CONCHECK, log unexpected concheck responses at LOGL_INFO 68356b5 core: build NMConnectivity unconditionally, possibly as a no-op a040f0b core: clean up connectivity code a bit 62e59ed ifcfg-rh: do not write IPV6_DEFAULTGW=:: for missing gateway ee58f2a policy: prevent double-deactivation of an NMActiveConnection after it's removed 49f8da5 wifi: change bgscan threshold parameter (fixes bug 1071942) 82be4aa ifcfg-rh: fix handling of VLAN parent PHYSDEV key f595624 systemd: fix up dispatcher unit install (rh #948433) 8dc646e core: don't log warnings when devices are removed 4f1e7e9 dhcp: kill dhclient on fatal errors 94f5d09 dnsmasq: does handle more than one nameserver per domain 886ee9a keyfile: ignore Emacs interlocking link named .# (rh #987629) 764f0e2 core: fix flushing of routes and updating legacy IPv4 address property 5628350 main: Set umask earlier 1a7e606 main: setenv(GIO_USE_VFS=local) *very* early dc70b48 libnm-glib: fix device description with newer udev versions b73b963 dhcp: don't crash checking lease config if no DHCP client is usable 89cb9e5 build: allow dhcpcd versions higher than 5 dad3e1c nm-online: describe '--timeout' option more exactly (rh #969363) c068709 dispatcher: fix tests after 42577c5269fdf4e9bea442eb96fcba7f8403bda5 42577c5 dispatcher: expose domains in IP4/6 config (bgo #701820) 65edeb9 dispatcher: publish vpn_ip6_config b0f23d2 libnm-util: fix possible crash when IP method is NULL d4d9d36 core: set GError on failure in nm_manager_deactivate_connection() (rh #976627) c38e901 keyfile: do not set GError over the top of a previous GError 3172ff1 dbus: fix dbus_connection_changed_cb() definition to take DBusConnection f324bfb keyfile: fix reading bonding options (bgo #701527) 8e9e392 libnm-util: remove 'downdelay' and 'updelay' when setting 'arp_interval' 261db76 libnm-util: verify() - can't set both IPv4 'disabled' and IPv6 'ignore' method 77b24af libnm-glib: fix the object creation warning for remote connections 665f42f wifi: fix checking AP mode and EAP-FAST support 050c979 agents: don't require root agents to be part of a login session 1c4f777 core: assume root always has a session for connection visibility 9b82977 release: bump version to 0.9.8.2 8d6828a libnm-util: fix 93c1041b9b3f48b42e35401b0dd756538935e870 for handling disabled 62bb5ec release: update NEWS 55ce7fe build: fix reporting of modemmanager-1 compilation status cca0bc9 wired: ignore carrier state for manual/static bridge and bond connections 9c57277 wifi: fix possible crash when IP configuration times out (rh #854073) 93c1041 libnm-util: recognize "disabled" as an IPv6 config method c126d97 modem-manager: read 'SupportedCapabilities' instead of 'ModemCapabilities' (bgo #701668) 0ff869e modem-manager: don't request allowed modes w
[Desktop-packages] [Bug 1917103] Re: Accessibility: Zoom: Mouse pointer leaves square trails as it moves across the screen
I took video showing the bug being reproduced on 21.04. Unfortunately it's not the best. The video in the bug I linked above is clearer. https://youtu.be/dSPUFTfpzZc ** Description changed: Steps to Reproduce: In the Settings applet choose Accessibility -> Zoom. Toggle the switch on. This happens whether or not you actually magnify the screen. When the mouse is moved anywhere on the screen, it leaves behind repeated partial square trails in its path. + + This is the same issue reported in: + https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.456 Date: Sat Feb 27 00:06:13 2021 DisplayManager: gdm3 GsettingsChanges: - + LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1917103 Title: Accessibility: Zoom: Mouse pointer leaves square trails as it moves across the screen Status in gnome-shell package in Ubuntu: New Bug description: Steps to Reproduce: In the Settings applet choose Accessibility -> Zoom. Toggle the switch on. This happens whether or not you actually magnify the screen. When the mouse is moved anywhere on the screen, it leaves behind repeated partial square trails in its path. This is the same issue reported in: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.456 Date: Sat Feb 27 00:06:13 2021 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917103] Re: Accessibility: Zoom: Mouse pointer leaves square trails as it moves across the screen
FWIW this is the same bug I reported in https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870 @guiverc suggested I report a new bug after reproducing this behavior on 21.04 which I have. Thanks in advance! -Chris -- 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/1917103 Title: Accessibility: Zoom: Mouse pointer leaves square trails as it moves across the screen Status in gnome-shell package in Ubuntu: New Bug description: Steps to Reproduce: In the Settings applet choose Accessibility -> Zoom. Toggle the switch on. This happens whether or not you actually magnify the screen. When the mouse is moved anywhere on the screen, it leaves behind repeated partial square trails in its path. This is the same issue reported in: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.456 Date: Sat Feb 27 00:06:13 2021 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917103] [NEW] Accessibility: Zoom: Mouse pointer leaves square trails as it moves across the screen
Public bug reported: Steps to Reproduce: In the Settings applet choose Accessibility -> Zoom. Toggle the switch on. This happens whether or not you actually magnify the screen. When the mouse is moved anywhere on the screen, it leaves behind repeated partial square trails in its path. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.456 Date: Sat Feb 27 00:06:13 2021 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- 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/1917103 Title: Accessibility: Zoom: Mouse pointer leaves square trails as it moves across the screen Status in gnome-shell package in Ubuntu: New Bug description: Steps to Reproduce: In the Settings applet choose Accessibility -> Zoom. Toggle the switch on. This happens whether or not you actually magnify the screen. When the mouse is moved anywhere on the screen, it leaves behind repeated partial square trails in its path. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.456 Date: Sat Feb 27 00:06:13 2021 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray
This also affects seadrive and seafile clients. I also see this on hp- systray and nextcloud. Enpass is not affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1903396] Re: libnl-route-3-200 unresolved symbols
linux-vdso.so.1 (0x7ffcf0521000) libnl-3.so.200 => /lib/x86_64-linux-gnu/libnl-3.so.200 (0x7f5a697da000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f5a697b7000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5a695c5000) /lib64/ld-linux-x86-64.so.2 (0x7f5a698a) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1903396 Title: libnl-route-3-200 unresolved symbols Status in libnl3 package in Ubuntu: Incomplete Bug description: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903396] [NEW] libnl-route-3-200 unresolved symbols
Public bug reported: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: New ** Project changed: calibre => libnl3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1903396 Title: libnl-route-3-200 unresolved symbols Status in libnl3 package in Ubuntu: New Bug description: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861025] Re: Keyboard shortcut "Search" shows as disabled, yet it still works, and custom shortcut unable to use the Search key
Reported to Gnome: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/issues/564 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #564 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/564 -- 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/1861025 Title: Keyboard shortcut "Search" shows as disabled, yet it still works, and custom shortcut unable to use the Search key Status in gnome-settings-daemon package in Ubuntu: New Bug description: Prior to the last upgrade (19.10), I used the Search key for one of my custom keyboard shortcuts. (I am using a Lenovo T450s, so the Search key is the button which works as F10 when the Fn key is also pressed.) In 19.10, this is no longer possible. The Search key is initially set up with the Search function, ie opens a magnifying glass text entry box to look for things. If I disable that function in the Keyboard dialogue, it still works! And therefore I cannot use the key as I wish. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 14:17:21 2020 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-xsettings InstallationDate: Installed on 2019-01-24 (368 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-10-31 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1861025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861025] Re: Keyboard shortcut "Search" shows as disabled, yet it still works, and custom shortcut unable to use the Search key
This problem is unaddressed on two computers after upgrading to Ubuntu 20.10. Now I can using the GUI set up a custom keyboard shortcut associated witth the "search" key, but it still does nothing. Pressing the "search" key just gives me the desktop search. -- 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/1861025 Title: Keyboard shortcut "Search" shows as disabled, yet it still works, and custom shortcut unable to use the Search key Status in gnome-settings-daemon package in Ubuntu: New Bug description: Prior to the last upgrade (19.10), I used the Search key for one of my custom keyboard shortcuts. (I am using a Lenovo T450s, so the Search key is the button which works as F10 when the Fn key is also pressed.) In 19.10, this is no longer possible. The Search key is initially set up with the Search function, ie opens a magnifying glass text entry box to look for things. If I disable that function in the Keyboard dialogue, it still works! And therefore I cannot use the key as I wish. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 14:17:21 2020 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-xsettings InstallationDate: Installed on 2019-01-24 (368 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-10-31 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1861025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861025] Re: Keyboard shortcut "Search" shows as disabled, yet it still works, and custom shortcut unable to use the Search key
This problem is no better on 20.04. -> In the Keyboard Shortcuts dialogue, no function is assigned to the "Search" key. -> There is a custom keyboard shortcut assigned to Ctrl-Search. It works fine. -> When I try to set a custom shortcut to the Search key, instead, the desktop pops into zoomed-out-view-all-my-windows view whenever I press the Search key, even though I have clicked "Set Shortcut" and the key should be trapped -> Moreover, even if I set the key with the command gsettings set org.gnome.settings-daemon.plugins.media-keys.custom- keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom- keybindings/custom8/ binding 'Search' It now shows up correctly in the dialogue listing shortcuts, but the action of the key is unchanged: it still just displays the Super-key overview view rather than carrying out my custom shortcut function The "Search" key corresponds to pressing the F10 key, without the Fn modifier, on this Lenovo T450s, running 20.04. Please help me disable this behaviour that seems hard-wired to this key! This is a regression since 19.10, as mentioned before. -- 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/1861025 Title: Keyboard shortcut "Search" shows as disabled, yet it still works, and custom shortcut unable to use the Search key Status in gnome-settings-daemon package in Ubuntu: New Bug description: Prior to the last upgrade (19.10), I used the Search key for one of my custom keyboard shortcuts. (I am using a Lenovo T450s, so the Search key is the button which works as F10 when the Fn key is also pressed.) In 19.10, this is no longer possible. The Search key is initially set up with the Search function, ie opens a magnifying glass text entry box to look for things. If I disable that function in the Keyboard dialogue, it still works! And therefore I cannot use the key as I wish. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 14:17:21 2020 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-xsettings InstallationDate: Installed on 2019-01-24 (368 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-10-31 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1861025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891972] [NEW] fingerprint will not recognize during login, acts like it doesnt scan and will not verify with fprintd-verify
Public bug reported: Fingerprint will not verify for login, acts like it doesn't even recognize the finger on swipe... fprintd-verify will not show a match when trying to match finger. please fix I got this laptop just for the fingerprint scanner lol ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fprintd 1.90.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 18 00:54:09 2020 InstallationDate: Installed on 2020-08-16 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fprintd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1891972 Title: fingerprint will not recognize during login, acts like it doesnt scan and will not verify with fprintd-verify Status in fprintd package in Ubuntu: New Bug description: Fingerprint will not verify for login, acts like it doesn't even recognize the finger on swipe... fprintd-verify will not show a match when trying to match finger. please fix I got this laptop just for the fingerprint scanner lol ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fprintd 1.90.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 18 00:54:09 2020 InstallationDate: Installed on 2020-08-16 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fprintd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1891972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891696] [NEW] fingerprint does not recognize after enrollment almost like drivers are not loaded all the way at boot or something not sure
Public bug reported: Using ASUS VivoBook, When attempting to use fingerprint sensor after enrollment it does not recognize any. Have done enrollment through both GUI and fprintd-enroll have also done fprintd-verify and none of them verify either. I enrolled one finger of every type and it still wont recognize any of them not sure what the problem is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fprintd 1.90.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:35:41 2020 InstallationDate: Installed on 2020-08-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fprintd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1891696 Title: fingerprint does not recognize after enrollment almost like drivers are not loaded all the way at boot or something not sure Status in fprintd package in Ubuntu: New Bug description: Using ASUS VivoBook, When attempting to use fingerprint sensor after enrollment it does not recognize any. Have done enrollment through both GUI and fprintd-enroll have also done fprintd-verify and none of them verify either. I enrolled one finger of every type and it still wont recognize any of them not sure what the problem is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fprintd 1.90.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:35:41 2020 InstallationDate: Installed on 2020-08-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fprintd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1891696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672931] Re: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar)
** Changed in: libertine/devel Status: In Progress => Triaged ** Changed in: libertine/devel Assignee: Christopher Townsend (townsend) => (unassigned) ** Changed in: libertine/devel Milestone: 1.8 => None ** Changed in: libertine/trunk Milestone: 1.8 => None ** Changed in: ubuntu-app-launch (Ubuntu) Status: In Progress => Triaged ** Changed in: ubuntu-app-launch (Ubuntu) Assignee: Christopher Townsend (townsend) => (unassigned) ** Changed in: xorg-server (Ubuntu) Status: In Progress => Triaged ** Changed in: xorg-server (Ubuntu) Assignee: Christopher Townsend (townsend) => (unassigned) -- 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/1672931 Title: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar) Status in Canonical System Image: Confirmed Status in Libertine: Triaged Status in Libertine devel series: Triaged Status in Libertine trunk series: Triaged Status in gtk+3.0 package in Ubuntu: Fix Released Status in libertine package in Ubuntu: Triaged Status in qtubuntu package in Ubuntu: Confirmed Status in ubuntu-app-launch package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt on Mir. I noticed a slight change in appearance and performance, but also: dan 25410 0.1 0.2 423316 38996 ?Sl 11:14 0:00 Xmir -rootless -displayfd 3 -mir org.gnome.Calculator dan 25456 1.8 0.5 606084 91736 ?Sl 11:14 0:03 Xmir -rootless -displayfd 3 -mir org.gnome.Nautilus dan 25611 1.7 0.2 345312 35520 ?Sl 11:18 0:00 Xmir -rootless -displayfd 3 -mir webbrowser-app_webbrowser-app_10 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874010] Re: [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot
I have the same exact problem, on Kubuntu 20.04 with Dell XPS 13 9300, using another kernel does fix it, but I have no wifi as a result and couldn't seem to solve that myself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1874010 Title: [Ice Lake] 2-second black screen blips when using Chrome or gnome- screenshot Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: Hi, Im using a HP 14s dq laptop with intel 630 graphics. I've tried both the mode setting and xserver-xorg-video-intel drivers, both result in the same 2-second black screen blips. The happens frequently using chrome, and always when using the gnome screenshot utility. Also, during boot teh screen flickers between black screen and boot splash a lot. setting nomodeset as a grub parameter stops the flickering, but is not a feasible solution as brightness can no longer be set. kind regards, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 08:15:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-21-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-24-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86c8] InstallationDate: Installed on 2020-04-16 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 14s-dq1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic root=UUID=54a7cc42-ac04-4466-b29f-16b1a7016ed0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2019 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C8 dmi.board.vendor: HP dmi.board.version: 56.31 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.09:bd12/20/2019:svnHP:pnHPLaptop14s-dq1xxx:pvr:rvnHP:rn86C8:rvr56.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14s-dq1xxx dmi.product.sku: 8BL04EA#ABH dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Still an issue in the latest Ubuntu 20.04 release. User winds up having to click the toggle over and over again while it stubbornly snaps back. Replicated on Many different machines with different hardware. Is there anyone who can not replicate this bug? ** Changed in: bluez (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Confirmed Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876211] [NEW] Bluetooth connection to headset works for volume buttons but not tests
Public bug reported: bluetooth worked fine under 19.10. Now, when bluetooth connects to my headset, I can hear noises from the increase/ decrease volume keys, but the "test" for Output Device in Sound settings makes sound on my laptop, not the headset. And all applications send sound to the laptop, not the headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 19:39:09 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-11-26 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BX001PUS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX001PUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX001PUS dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: DC:53:60:42:C0:97 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:22321 acl:74 sco:0 events:1206 errors:0 TX bytes:257018 acl:319 sco:0 commands:403 errors:0 syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1876211 Title: Bluetooth connection to headset works for volume buttons but not tests Status in bluez package in Ubuntu: New Bug description: bluetooth worked fine under 19.10. Now, when bluetooth connects to my headset, I can hear noises from the increase/ decrease volume keys, but the "test" for Output Device in Sound settings makes sound on my laptop, not the headset. And all applications send sound to the laptop, not the headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 19:39:09 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-11-26 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BX001PUS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX001PUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX001PUS dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:53:60:42:C0:97 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:22321 acl:74 sco:0 events:1206 errors:0 TX bytes:257018 acl:319 sco:0 commands:403 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1876211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
Thanks, raised here https://gitlab.com/sane- project/backends/-/issues/278 ** Bug watch added: gitlab.com/sane-project/backends/-/issues #278 https://gitlab.com/sane-project/backends/-/issues/278 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1759889 Title: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw Status in simple-scan package in Ubuntu: Incomplete Bug description: Hello, When scanning multiple pages from a Canon mf244dw via the LAN I only get the first page scanned, then an error message. Running "simple-scan -d" and looking at the output I see the following: [+123.87s] DEBUG: scanner.vala:1321: sane_read (7651) -> (SANE_STATUS_CANCELLED, 0) [+123.87s] WARNING: scanner.vala:1337: Unable to read frame from device: Operation was cancelled [+123.87s] DEBUG: scanner.vala:768: sane_cancel () [+123.87s] DEBUG: scanner.vala:771: sane_close () I do notice that the scanner is already feeding in the second page before the first page has completely rendered on screen - perhaps it's going too fast? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
Very similar failure observed - the 1st page scans, but the 2nd fails. Errors in logs are different however: $ SANE_DEBUG_PIXMA=3 xsane [sanei_debug] Setting debug level of pixma to 3. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.37 [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_find_scanners() found 1 devices (xsane:6919): Gdk-CRITICAL **: 12:08:35.630: IA__gdk_drawable_unref: assertion 'GDK_IS_DRAWABLE (drawable)' failed (xsane:6919): Gdk-CRITICAL **: 12:08:35.630: IA__gdk_drawable_unref: assertion 'GDK_IS_DRAWABLE (drawable)' failed [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_open(): Canon i-SENSYS MF240 Series [pixma] *iclass_open* This is a generation 2 scanner. * [pixma] Trying to clear the interrupt buffer... [pixma] no packets in buffer [xsane] ERROR: xsane-startimage not found. Looks like xsane is not installed correct. [pixma] Reader task started [pixma] Reader task id=140132160792320 (threaded) [pixma] [pixma] pixma_scan(): start [pixma] line_size=7680 image_size=32256000 channels=3 depth=8 [pixma] dpi=300x300 offset=(0,0) dimension=2560x4200 [pixma] gamma_table=0x55deb339ae38 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] adf-wait=0 [pixma] ADF page count: 0 [pixma] Setting non-blocking mode [pixma] raw_width = 2560 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_scan* start scanning * [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_finish_scan* wait for next page from ADF * [pixma] WARNING:image size mismatches [pixma] 32256000 expected (4200 lines) but 25489920 received (3319 lines) [pixma] pixma_read_image(): completed (underrun detected) [pixma] Reader task terminated [pixma] pixma_close(): Canon i-SENSYS MF240 Series vs $ SANE_DEBUG_PIXMA=3 simple-scan [sanei_debug] Setting debug level of pixma to 3. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.37 [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_find_scanners() found 1 devices [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_open(): Canon i-SENSYS MF240 Series [pixma] *iclass_open* This is a generation 2 scanner. * [pixma] Trying to clear the interrupt buffer... [pixma] no packets in buffer [pixma] Reader task started [pixma] Reader task id=140424282892032 (threaded) [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] [pixma] pixma_scan(): start [pixma] line_size=1280 image_size=2112000 channels=1 depth=8 [pixma] dpi=150x150 offset=(0,0) dimension=1275x1650 [pixma] gamma_table=0x7fb6fc28db88 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] adf-wait=0 [pixma] ADF page count: 0 [pixma] raw_width = 1280 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_scan* start scanning * [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_finish_scan* wait for next page from ADF * [pixma] pixma_read_image():completed [pixma] Reader task
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
To @kfunk @axet @troyready: That worked perfectly for me. Thank you so much!!! For those like me for whom these are all magical incantations, here's my sequence aggregated from advice above: Press the Ubuntu/Super key and type "Software" and pick the one that is called "Software & Updates". On the first tab, make sure "source code" is checked. Then, open a terminal and paste the following (line by line up to the apt line, then the rest can go together): ``` apt-get build-dep snapd TMPDIR=$(mktemp -d) cd $TMPDIR apt-get -y source snapd sed -i 's/"http", "https", "mailto", "snap", "help"/"http", "https", "mailto", "snap", "help", "apt", "zoommtg", "slack"/' snapd-*/usersession/userd/launcher.go sed -i 's/!osutil.GetenvBool(reExecKey, true)/true/' snapd-*/cmd/cmd_linux.go cd snapd-* && dch -l$(hostname) fix_missing_app_types cd .. cd snapd-* && DEB_BUILD_OPTIONS=nocheck debuild -b -uc -us cd .. sudo dpkg -i snapd_*.deb sudo service snapd restart killall snap ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
Attached as a file the full output for "simple-scan 3.34.1" when scanning 2 pages from the feeder, which still has this bug. Final few lines are here: [+53.69s] DEBUG: scanner.vala:1345: sane_read (15300) -> (SANE_STATUS_GOOD, 15300) [+55.00s] DEBUG: scanner.vala:1345: sane_read (15300) -> (SANE_STATUS_GOOD, 7649) [+55.00s] DEBUG: scanner.vala:1345: sane_read (15301) -> (SANE_STATUS_EOF, 0) [+55.00s] DEBUG: scanner.vala:1241: sane_start (page=1, pass=0) -> SANE_STATUS_GOOD [+55.00s] DEBUG: scanner.vala:1258: sane_get_parameters () -> SANE_STATUS_GOOD [+55.00s] DEBUG: scanner.vala:1270: Parameters: format=SANE_FRAME_RGB last_frame=SANE_TRUE bytes_per_line=7650 pixels_per_line=2550 lines=3300 depth=8 [+55.00s] DEBUG: autosave-manager.vala:349: Autosaving page pixels to /home/test-machine/.cache/simple-scan/autosaves/496152848.pixels [+55.02s] DEBUG: autosave-manager.vala:281: Autosaving book information [+55.02s] DEBUG: autosave-manager.vala:298: Autosaving page page-0 [+55.02s] CRITICAL: page_finish: assertion 'self != NULL' failed [+55.02s] DEBUG: simple-scan.vala:350: Page is 2550 pixels wide, 3300 pixels high, 8 bits per pixel [+55.03s] DEBUG: simple-scan.vala:284: Getting color profile for device pixma:MF240_canon-mfc.lan [+55.04s] DEBUG: simple-scan.vala:304: Unable to find colord device pixma:MF240_canon-mfc.lan: property match 'Serial'='sane:pixma:MF240_canon-mfc.lan' does not exist [+56.00s] DEBUG: scanner.vala:1345: sane_read (7651) -> (SANE_STATUS_NO_DOCS, 0) [+56.00s] DEBUG: scanner.vala:1214: sane_cancel () ** Attachment added: "output.txt" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+attachment/5356478/+files/output.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1759889 Title: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw Status in simple-scan package in Ubuntu: Incomplete Bug description: Hello, When scanning multiple pages from a Canon mf244dw via the LAN I only get the first page scanned, then an error message. Running "simple-scan -d" and looking at the output I see the following: [+123.87s] DEBUG: scanner.vala:1321: sane_read (7651) -> (SANE_STATUS_CANCELLED, 0) [+123.87s] WARNING: scanner.vala:1337: Unable to read frame from device: Operation was cancelled [+123.87s] DEBUG: scanner.vala:768: sane_cancel () [+123.87s] DEBUG: scanner.vala:771: sane_close () I do notice that the scanner is already feeding in the second page before the first page has completely rendered on screen - perhaps it's going too fast? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
wow, @kfunk and @axet, thank you so much for this effort! Alas, I get stuck at the very first step: sudo apt-get build-dep snapd Reading package lists... Done E: You must put some 'source' URIs in your sources.list -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799073] Re: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10
This works great in 20.04 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1799073 Title: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10 Status in gnome-shell package in Ubuntu: Fix Released Bug description: Hi all. I noticed this problem when I upgraded from 18.04 to 18.04.1 (Worked perfectly in stock 18.04) and then I was testing the 18.10 beta and hoped it would be fixed there but it's not. To reproduce: login to the regular Ubuntu desktop, hit Super+Alt+= (You can validate that your keyboard shortcut is set to the default in Settings->Keyboard.) I also tried changing the keyboard mapping for this action in case there was a conflict, and no matter what I set it to I couldn't zoom from the keyboard. As a partially blind user, this is a show stopper for me - I require screen zoom to be able to use Ubuntu at all for any serious work. Thanks for everything you do! -Chris (Happy to try any work-arounds or testing people can think up to help fix this problem) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2018-10-07 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Package: gnome-shell 3.30.1-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Ok sounds good. Should I expect these to come through as an update through the Software Updater eventually? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: In Progress Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Ok, thanks for keeping me updated, let me know if there's anything I can do to help troubleshoot! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Something I just noticed, if it means anything, is that I have a file in ~/.config/evolution/sources that seems to contain what would be my Nextcloud info, but it seems to be missing some information perhaps? I don't have a reference in front of me for what these normally look like. Contents pasted below [Data Source] DisplayName=leggett...@ambrose.leggett.dev Enabled=true Parent= [Authentication] Host= Method=none Port=0 ProxyUid=system-proxy RememberPassword=true User= CredentialName= IsExternal=true [Collection] BackendName=webdav CalendarEnabled=true ContactsEnabled=true Identity=leggettc18 MailEnabled=true AllowSourcesRename=false CalendarUrl= ContactsUrl= [GNOME Online Accounts] AccountId=account_1586225954_0 CalendarUrl=https://leggett...@ambrose.leggett.dev/remote.php/caldav/ ContactsUrl=https://leggett...@ambrose.leggett.dev/remote.php/carddav/ Name= Address= -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Absolutely, I've attached a txt file with the contents of `journalctl -b 0`. For the record, my actions for these logs were: 1. Boot 2. Sign in 3. Launch Firefox and navigate to my Nextcloud instance 4. Generate an app specific password (I use two-factor) 5. Add the Nextcloud account in the Online Accounts settings page. 6. Open the calendar app to make sure it didn't miraculously work this time. Worth noting is that I have the exact same issue in two different installations of the same 20.04 daily iso, so its not an issue specific to this particular installation. Tomorrow I'll see if I can set up an Endeavor OS install in a VM to see if it happens on a different distro running Gnome 3.36. Also, just wanted to say this is a small bump in an otherwise stellar looking release. Appreciate all the work you guys do at Canonical. ** Attachment added: "results of `journalctl -b 0` after attempting to add nextcloud account and not having it show up in the calendar app." https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+attachment/5348302/+files/logs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871137] Re: Recorded audio is super choppy with today's apt upgrade
After running another apt update && apt upgrade this problem seems to have resolved itself. I hate mysteries :) ** Attachment added: "Non choppy sound. yay." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+attachment/5347952/+files/Non%20choppy%20sound.%20yay. -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871137] Re: Recorded audio is super choppy with today's apt upgrade
** Attachment added: "Choppy sound with Gnome Sound Recorder" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+attachment/5347862/+files/Choppy%20sound%20with%20Gnome%20Sound%20Recorder -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871137] Re: Recorded audio is super choppy with today's apt upgrade
Install log for today as per request of lotuspsychje@ on ubuntu+1 freenode channel: https://paste.ubuntu.com/p/sxYkf9KtnW/ -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871137] [NEW] Recorded audio is super choppy with today's apt upgrade
Public bug reported: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Choppy audio WAV from latest 20.04" https://bugs.launchpad.net/bugs/1871137/+attachment/5347811/+files/choppyfocalfossaaudio.wav -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871019] [NEW] Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Public bug reported: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts package in Ubuntu: New Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869414] [NEW] Running applications always appear on the desktop
Public bug reported: Ubuntu 20.04 No matter which virtual desktop is in focus, applications running on other virtual desktop are displayed even if minimized. This makes it impossible to interact with desktop icons without closing all running applications. It is not possible to interact with the application itself when it's displayed erroneously, unless you return to its original virtual desktop. I've reinstalled from two different daily images and have been able to reproduce the problem each time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:22:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1458:2311] InstallationDate: Installed on 2020-03-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) MachineType: System76 Thelio ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_4u488c@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_4u488c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: System76 dmi.bios.version: F42a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF42aZ5:bd08/22/2019:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible 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/1869414 Title: Running applications always appear on the desktop Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04 No matter which virtual desktop is in focus, applications running on other virtual desktop are displayed even if minimized. This makes it impossible to interact with desktop icons without closing all running applications. It is not possible to interact with the application itself when it's displayed erroneously, unless you return to its original virtual desktop. I've reinstalled from two different daily images and have been able to reproduce the problem each time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:22:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1458:2311] InstallationDate: Installed on 2020-03-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) MachineType: System76 Thelio ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_4u488c@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_4u488c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install)
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
If the approach so far is to individually whitelist classes of links, surely can't this be better dealt with by doing something similar to how Chromium responds to me clicking on a downloaded file: it asks me if it's okay to have snap launch that file? Can't we do this for links that go to xdg-open without downloading a file? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Yeah, this can be labelled a COVID-relevant bug, since there are countless new users flooding to Zoom, etc... It looks like this is being worked on within the last four days: https://github.com/snapcore/snapd/pull/8304 But only for zoom?! And I'm not sure of the nature of the fix or who would get it. This may reflect the latest inclusions (see line 95 or so) ? It shows "apt" being included: https://github.com/snapcore/snapd/blob/master/tests/main/xdg- open/task.yaml -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825710] Re: Remove "Application is ready" notification
I will add that when I see this in Pidgin, it leads me to believe someone has highlighted me, but no, no one has and I just spent some time context switching. And this keeps happening over and over again... @dean, indeed, but Pidgin is wasting lots of my time with this nonsense:) -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825710] Re: Remove "Application is ready" notification
I'll add that since updating from 18.04 to 20.04, Pidgin has been doing this very consistently. Whenever I have Pidgin focused and then switch focus to another window, some time later, I get a notification saying: Pidgin Internet Messenger "#foo" is ready where #foo is the name of the last chat tab I had focused with Pidgin. This "new" behavior is atrocious. I'm not sure what changed in Pidgin and/or Gnome, but this is a terrible user experience. Also, this is related to https://bugs.launchpad.net/bugs/1861006. -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866277] [NEW] Power Saving settings "Wi-Fi can be turned off to save power" does not work as advertised
Public bug reported: In Settings -> Power under the "Power Saving" section, there are the following two on/off slider options: Wi-Fi Wi-Fi can be turned off to save power. Bluetooth Bluetooth can be turned off to save power. Rather than controlling something to do with power-saving, eg. when battery is low or the system is inactive, these appear to immediately turn off wifi, and bluetooth, respectively, when the machine is a laptop and is unplugged. Instead, they should control something more useful, or be relabeled. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-power-manager 3.32.0-1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 19:09:48 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-11-26 (100 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1866277 Title: Power Saving settings "Wi-Fi can be turned off to save power" does not work as advertised Status in gnome-power-manager package in Ubuntu: New Bug description: In Settings -> Power under the "Power Saving" section, there are the following two on/off slider options: Wi-Fi Wi-Fi can be turned off to save power. Bluetooth Bluetooth can be turned off to save power. Rather than controlling something to do with power-saving, eg. when battery is low or the system is inactive, these appear to immediately turn off wifi, and bluetooth, respectively, when the machine is a laptop and is unplugged. Instead, they should control something more useful, or be relabeled. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-power-manager 3.32.0-1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 19:09:48 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-11-26 (100 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1866277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Agreed. This seems like fundamental desktop functionality to me. My approach so far is to right click on the link, copy it, and then in a terminal type xdg-open "" where is the pasted link. In case it's useful, here's an updated list from above, but clearly there should be a way for people to choose themselves what to whitelist. Can someone explain how to add to the whitelist? - steam - apt - ssh - tg - magnet - urn - zoommtg - irc - git - tg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1858857] Re: gnome-calendar: Hits assert when timezone set to Etc/UTC
This is all fascinating. Thank fo updates. You are all super stars ! Enamoring Sincerely. Christopher Leslie-John Peters On Wed, Feb 19, 2020, 5:22 AM Launchpad Bug Tracker < 1858...@bugs.launchpad.net> wrote: > This bug was fixed in the package gnome-calendar - 3.34.2-1ubuntu1 > > --- > gnome-calendar (3.34.2-1ubuntu1) focal; urgency=medium > > * d/p/fall-back-to-UTC-when-timezone-is-unrecognized.patch: > - Fix a crash where the "Etc/UTC" timezone from Live CD > is not recongised by libical. (LP: #1858857) > > -- Matthew Ruffell Wed, 19 Feb 2020 > 13:09:39 +1300 > > ** Changed in: gnome-calendar (Ubuntu Focal) >Status: Fix Committed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1858857 > > Title: > gnome-calendar: Hits assert when timezone set to Etc/UTC > > Status in gnome-calendar package in Ubuntu: > Fix Released > Status in gnome-calendar source package in Focal: > Fix Released > > Bug description: > [Impact] > > When the system timezone is set to Etc/UTC, most notably in the 20.04 > Live CD environment, gnome-calendar fails to start, as it hits an > assert. > > > ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: > assertion failed: (ical_tz != NULL) > Bail out! > ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: > assertion failed: (ical_tz != NULL) > Aborted (core dumped) > > This is reproducible in focal with: gnome-calendar 3.34.2-1build1 > This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1 > > More seriously, this bug is triggered when a user presses the Super > key in the Live CD test environment and searches for an application, > as dbus will attempt to start the gnome-calendar service, and gnome- > calendar will crash due to this bug. > > [Test Case] > > Change system timezone to Etc/UTC and attempt to launch gnome- > calendar: > > ubuntu@ubuntu:/var/log$ sudo timedatectl set-timezone Etc/UTC > ubuntu@ubuntu:/var/log$ timedatectl > Local time: Tue 2020-02-18 02:49:21 UTC > Universal time: Tue 2020-02-18 02:49:21 UTC >RTC time: Tue 2020-02-18 02:49:22 > Time zone: Etc/UTC (UTC, +) > System clock synchronized: yes > NTP service: active > RTC in local TZ: no > ubuntu@ubuntu:/var/log$ gnome-calendar > ** > > ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: > assertion failed: (ical_tz != NULL) > Bail out! > ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: > assertion failed: (ical_tz != NULL) > Aborted (core dumped) > > [Regression Potential] > > The risk of regression is low due to the assert being removed and > replaced with a default to UTC time if the previous timezone pointer > is NULL. This is also only going to the focal development release, > where any impact to real users will be low. > > [Other Information] > > There is an upstream issue open: > > https://gitlab.gnome.org/GNOME/gnome-calendar/issues/485 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1858857/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1858857 Title: gnome-calendar: Hits assert when timezone set to Etc/UTC Status in gnome-calendar package in Ubuntu: Fix Released Status in gnome-calendar source package in Focal: Fix Released Bug description: [Impact] When the system timezone is set to Etc/UTC, most notably in the 20.04 Live CD environment, gnome-calendar fails to start, as it hits an assert. ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL) Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL) Aborted (core dumped) This is reproducible in focal with: gnome-calendar 3.34.2-1build1 This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1 More seriously, this bug is triggered when a user presses the Super key in the Live CD test environment and searches for an application, as dbus will attempt to start the gnome-calendar service, and gnome- calendar will crash due to this bug. [Test Case] Change system timezone to Etc/UTC and attempt to launch gnome- calendar: ubuntu@ubuntu:/var/log$ sudo timedatectl set-timezone
[Desktop-packages] [Bug 1799073] Re: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10
This is fixed in Ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1799073 Title: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi all. I noticed this problem when I upgraded from 18.04 to 18.04.1 (Worked perfectly in stock 18.04) and then I was testing the 18.10 beta and hoped it would be fixed there but it's not. To reproduce: login to the regular Ubuntu desktop, hit Super+Alt+= (You can validate that your keyboard shortcut is set to the default in Settings->Keyboard.) I also tried changing the keyboard mapping for this action in case there was a conflict, and no matter what I set it to I couldn't zoom from the keyboard. As a partially blind user, this is a show stopper for me - I require screen zoom to be able to use Ubuntu at all for any serious work. Thanks for everything you do! -Chris (Happy to try any work-arounds or testing people can think up to help fix this problem) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2018-10-07 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Package: gnome-shell 3.30.1-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861043] Re: GUI frozen when memory was exhausted (by non-GUI processes)
I was able to trigger this again with a sizeable Firefox webpage. This time I was able to CTRL+ALT+F4 to a different VT and even enter my username but was not able to login. I had to Hard Boot to recover the system. Similar messages in there about memory pressure. Thanks again for looking into this! ** Attachment added: "Second Triggering" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861043/+attachment/5324477/+files/ff_prevboot.txt -- 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/1861043 Title: GUI frozen when memory was exhausted (by non-GUI processes) Status in gnome-shell package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861043/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1861043] Re: Xorg freeze
Here's the prevboot. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861043/+attachment/5323859/+files/prevboot.txt -- 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/1861043 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted
Update: a kernel upgrade solved the mic white noise for me. I had been running a 5.0 kernel. Updating to a 5.4 kernel fixed it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827440 Title: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hopefully all the necessary info is in the extra stuff that automatically got sent. Basically, I didn't do anything fancy, but audio recorded with my microphone (through Skype, and arecord in the Terminal) has tons of static and the voice is distorted or saturated. Booting this computer on Windows doesn't have issues, so that's why I don't think it's the computer, I think it's the OS. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyler 1499 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 2 19:04:55 2019 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: tyler 1562 F...m pulseaudio /dev/snd/pcmC0D0p: tyler 1562 F...m pulseaudio /dev/snd/controlC0: tyler 1562 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHS1TG00 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted
Tyler, did you ever find a solution to this? I'm having the same problem with a the same laptop (X1 Carbon 6th gen) running Kubuntu 18.04. The only "solution" I've found is to turn off "internal mic boost" using alsa-mixer (hit F5 to show all channels, cursor all the way to the right) and keep the mic capture level below 20%. So it works, but far from ideal since the mic is low (but better than making the person on the other end of a call hearing a shitload of white noise that's produced otherwise). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827440 Title: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hopefully all the necessary info is in the extra stuff that automatically got sent. Basically, I didn't do anything fancy, but audio recorded with my microphone (through Skype, and arecord in the Terminal) has tons of static and the voice is distorted or saturated. Booting this computer on Windows doesn't have issues, so that's why I don't think it's the computer, I think it's the OS. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyler 1499 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 2 19:04:55 2019 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: tyler 1562 F...m pulseaudio /dev/snd/pcmC0D0p: tyler 1562 F...m pulseaudio /dev/snd/controlC0: tyler 1562 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHS1TG00 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
[Desktop-packages] [Bug 1861043] [NEW] Xorg freeze
Public bug reported: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze has-fix has-workaround 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/1861043 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also
[Desktop-packages] [Bug 1861025] [NEW] Keyboard shortcut "Search" shows as disabled, yet it still works, and custom shortcut unable to use the Search key
Public bug reported: Prior to the last upgrade (19.10), I used the Search key for one of my custom keyboard shortcuts. (I am using a Lenovo T450s, so the Search key is the button which works as F10 when the Fn key is also pressed.) In 19.10, this is no longer possible. The Search key is initially set up with the Search function, ie opens a magnifying glass text entry box to look for things. If I disable that function in the Keyboard dialogue, it still works! And therefore I cannot use the key as I wish. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 14:17:21 2020 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-xsettings InstallationDate: Installed on 2019-01-24 (368 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-10-31 (88 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1861025 Title: Keyboard shortcut "Search" shows as disabled, yet it still works, and custom shortcut unable to use the Search key Status in gnome-settings-daemon package in Ubuntu: New Bug description: Prior to the last upgrade (19.10), I used the Search key for one of my custom keyboard shortcuts. (I am using a Lenovo T450s, so the Search key is the button which works as F10 when the Fn key is also pressed.) In 19.10, this is no longer possible. The Search key is initially set up with the Search function, ie opens a magnifying glass text entry box to look for things. If I disable that function in the Keyboard dialogue, it still works! And therefore I cannot use the key as I wish. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 14:17:21 2020 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-xsettings InstallationDate: Installed on 2019-01-24 (368 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-10-31 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1861025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 463796] Re: Alsa doesn't detect external mic
Fix was apparently released, yet for me the problem arose first when I upgraded
to 19.10.
I now have no access to the microphone on my headset.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/463796
Title:
Alsa doesn't detect external mic
Status in alsa-driver package in Ubuntu:
Fix Released
Bug description:
I have a Logitech mini-jack headset with a mic. Sound playback works,
but recording does not; it only works through the computer's built-in
microphone.
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: josh 2688 F pulseaudio
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0x9240 irq 16'
Mixer name : 'IDT 92HD71B7X'
Components : 'HDA:111d76b2,103c3600,00100302'
Controls : 35
Simple ctrls : 22
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0x9231 irq 19'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,0010'
Controls : 4
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [off]
CheckboxSubmission: 6bacad257d07e21537e077802a955e05
CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
Date: Thu Oct 29 17:31:38 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: alsa-driver
Uname: Linux 2.6.31-14-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/463796/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858439] Re: When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232]
This is not just a problem when I dock. In fact, even when I correct the problem by selecting the correct output device in sound settings, it reverts after a while back to the incorrect one (HDMI/Display port) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1858439 Title: When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232] Status in alsa-driver package in Ubuntu: New Bug description: When my laptop is docked, I used to use a headset plugged into the dock for meetings. Both microphone and audio out were connected to my headset. Since the last update, my sound does not work like it used it, and I cannot make it work like I want. In particular, whenever I dock: - the output device changes to "HDMI/DisplayPort 2 - Built-in Audio". I do not know what that is (nothing is connected to HDMI), but it results in strange audio behaviour in which I can hear something through headphones but it's faint and does not respond to volume control. - audio input switches to internal microphone. Worse, there is no longer the choice to use the headset microphone, which is mandatory for those in my meeting not to hear my keyboard taps. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cpbl 3431 F pulseaudio /dev/snd/pcmC2D0c: cpbl 3431 F...m pulseaudio /dev/snd/controlC1: cpbl 3431 F pulseaudio /dev/snd/controlC0: cpbl 3431 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 06:36:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (346 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [20BXCTO1WW, Realtek ALC3232, Black Headphone Out, Right] fails after a while UpgradeStatus: Upgraded to eoan on 2019-10-31 (66 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1858439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 824255] Re: network-manager-openconnect can’t prompt for passwords
Howdy I was testing 20.04 (which has version 1.2.4-2ubuntu1 of network- manager-openconnect) and I believe this may still be an issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/824255 Title: network-manager-openconnect can’t prompt for passwords Status in network-manager-openconnect package in Ubuntu: Fix Released Status in network-manager-pptp package in Ubuntu: Fix Released Status in network-manager-vpnc package in Ubuntu: Fix Released Bug description: Activating an openconnect VPN fails silently. This goes to syslog: Aug 10 21:01:24 fixed-disk NetworkManager[27695]: Starting VPN service 'openconnect'... Aug 10 21:01:24 fixed-disk NetworkManager[27695]: VPN service 'openconnect' started (org.freedesktop.NetworkManager.openconnect), PID 27842 Aug 10 21:01:24 fixed-disk NetworkManager[27695]: VPN service 'openconnect' appeared; activating connections Aug 10 21:01:24 fixed-disk NetworkManager[27695]: VPN plugin state changed: 1 Aug 10 21:01:24 fixed-disk NetworkManager[27695]: [1313024484.634493] [nm-vpn-connection.c:882] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. I’m sure part of the problem is that network-manager-openconnect-gnome is missing /usr/lib/network-manager-openconnect/nm-openconnect-auth- dialog (which is built and installed but not packaged), but installing it by hand didn’t seem to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/824255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858439] [NEW] When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232]
Public bug reported: When my laptop is docked, I used to use a headset plugged into the dock for meetings. Both microphone and audio out were connected to my headset. Since the last update, my sound does not work like it used it, and I cannot make it work like I want. In particular, whenever I dock: - the output device changes to "HDMI/DisplayPort 2 - Built-in Audio". I do not know what that is (nothing is connected to HDMI), but it results in strange audio behaviour in which I can hear something through headphones but it's faint and does not respond to volume control. - audio input switches to internal microphone. Worse, there is no longer the choice to use the headset microphone, which is mandatory for those in my meeting not to hear my keyboard taps. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cpbl 3431 F pulseaudio /dev/snd/pcmC2D0c: cpbl 3431 F...m pulseaudio /dev/snd/controlC1: cpbl 3431 F pulseaudio /dev/snd/controlC0: cpbl 3431 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 06:36:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (346 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [20BXCTO1WW, Realtek ALC3232, Black Headphone Out, Right] fails after a while UpgradeStatus: Upgraded to eoan on 2019-10-31 (66 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Summary changed: - When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232, Black Headphone Out, Right] fails after a while + When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1858439 Title: When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232] Status in alsa-driver package in Ubuntu: New Bug description: When my laptop is docked, I used to use a headset plugged into the dock for meetings. Both microphone and audio out were connected to my headset. Since the last update, my sound does not work like it used it, and I cannot make it work like I want. In particular, whenever I dock: - the output device changes to "HDMI/DisplayPort 2 - Built-in Audio". I do not know what that is (nothing is connected to HDMI), but it results in strange audio behaviour in which I can hear something through headphones but it's faint and does not respond to volume control. - audio input switches to internal microphone. Worse, there is no longer the choice to use the headset microphone, which is mandatory for those in my meeting not to hear my keyboard taps. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cpbl 3431 F pulseaudio /dev/snd/pcmC2D0c: cpbl 3431 F...m pulseaudio /dev/snd/controlC1: cpbl 3431 F pulseaudio /dev/snd/controlC0: cpbl 3431 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 06:36:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (346 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver
[Desktop-packages] [Bug 1849257] Re: Firefox audio not playing via bluetooth
Hi I'm seeing this bug in 20.04. I upgraded from a fresh 19.10 install. I tried removing ~/.mozilla and the problem still persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849257 Title: Firefox audio not playing via bluetooth Status in firefox package in Ubuntu: Fix Released Bug description: When I am playing videos in Youtube, it plays through my laptop speakers instead of through the connected bluetooth device. I tried that with my USB headset but still audio plays out through my laptop speakers. Same for Prime Video. It works fine in Google chrome i.e. audio is re-routed through bluetooth speakers. I tried switching audio devices and still nothing changes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 69.0.3+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ashfaq 1386 F pulseaudio /dev/snd/pcmC0D0c: ashfaq 1386 F...m pulseaudio /dev/snd/pcmC0D0p: ashfaq 1386 F...m pulseaudio BuildID: 20191010103742 Channel: Unavailable Date: Tue Oct 22 10:58:03 2019 ForcedLayersAccel: False InstallationDate: Installed on 2019-10-18 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.57 metric 600 NoProfiles: True ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Suntory_KL dmi.board.vendor: KBL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd11/28/2017:svnAcer:pnSwiftSF314-52:pvrV1.08:rvnKBL:rnSuntory_KL:rvrV1.08:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-52 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save
Actually, it is not true that this is solved under 19.10. All that has happened is that the latency has shortened to 1-2 seconds. It is *still* the case that during that time, I cannot get the focus in any other window or do anything else in the operating system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this
[Desktop-packages] [Bug 1851134] [NEW] setting custom keyboard shortcut fails for certain keys
Public bug reported: I click on settings in menu or press my settings icon key (above F9 key on Lenovo T450s keyboard). Navigate to "Keyboard Shortcuts". Scroll to bottom to press "+" to add a custom shortcut. Define function, then click on "Set Shortcut...". Then I press the "Explorer" key, which is above the F12 on my keyboard. Instead of setting the shortcut, it brings up a file browser. I can set my shortcut to shift-Explorer, but not to Explorer. This is even though no other keyboard shortcut listed is set to this key "Explorer". The "Home folder" Launcher is set to "Disabled". Changing the "Home folder" launcher keyboard shortcut to something else does not help. Instead, once I click on "set Shortcut", it should listen to whatever I choose. The same problem exists for the "Search" key. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 09:29:28 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (282 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-10-31 (2 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "20191103_093407.jpg" https://bugs.launchpad.net/bugs/1851134/+attachment/5302441/+files/20191103_093407.jpg -- 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/1851134 Title: setting custom keyboard shortcut fails for certain keys Status in gnome-settings-daemon package in Ubuntu: New Bug description: I click on settings in menu or press my settings icon key (above F9 key on Lenovo T450s keyboard). Navigate to "Keyboard Shortcuts". Scroll to bottom to press "+" to add a custom shortcut. Define function, then click on "Set Shortcut...". Then I press the "Explorer" key, which is above the F12 on my keyboard. Instead of setting the shortcut, it brings up a file browser. I can set my shortcut to shift-Explorer, but not to Explorer. This is even though no other keyboard shortcut listed is set to this key "Explorer". The "Home folder" Launcher is set to "Disabled". Changing the "Home folder" launcher keyboard shortcut to something else does not help. Instead, once I click on "set Shortcut", it should listen to whatever I choose. The same problem exists for the "Search" key. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 09:29:28 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (282 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-10-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1851134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save
Yes, I have now very grudgingly upgraded to 19.10 and the problem seems to be resolved. This problem was new at some point in 19.04 (ie did not exist at first with 19.04) and I do not think pressuring eople to upgrade (so soon after a release) is a good solution. On the other hand, strangely, no one else has reported the bug. Thanks, Olivier! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO
[Desktop-packages] [Bug 424044] Re: [Upstream] Math Object formula changed causing resize saving .odt to .doc
Upstream root caused this as per
https://bugs.documentfoundation.org/show_bug.cgi?id=45284#c15 and still
reproducible in:
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c
The WORKAROUND patch would need to go through QA to be included in
upstream release.
** Changed in: libreoffice (Ubuntu)
Status: Incomplete => Triaged
--
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/424044
Title:
[Upstream] Math Object formula changed causing resize saving .odt to
.doc
Status in LibreOffice:
Confirmed
Status in OpenOffice:
Invalid
Status in libreoffice package in Ubuntu:
Triaged
Status in openoffice.org package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: openoffice.org-writer
1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
2) apt-cache policy libreoffice-writer
libreoffice-writer:
Installed: 1:3.3.3-1ubuntu2
Candidate: 1:3.3.3-1ubuntu2
Version table:
*** 1:3.3.3-1ubuntu2 0
100 /var/lib/dpkg/status
1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386
Packages
1:3.3.2-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
3) What is expected to happen in LibreOffice Writer via the Terminal:
cd ~/Desktop && wget
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/+attachment/2287815/+files/example.odt
&& lowriter -nologo example.odt
save to .doc and open the .doc it looks the same as the .odt.
4) What happens instead is the embedded Math equation is resized. The
Math equation changes from:
size 21{ Prod cSub { size 14{ ital "k="1} } cSup { size 14{N} } {p rSub {size
14 {k}
}^{size 14 n_{size 10 k} } } }
in the .odt to:
size 12{ Prod cSub { size 8{ ital "k="1} } cSup { size 8{N} } {p rSub
{ size 8{k} } rSup { size 8{n rSub {k} } } } } {}
in .doc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/424044/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 384553] Re: [Upstream] Text color changed to black importing Office 2007 PPTX
Scope of this report noted in Bug Description fixed in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Fix Released ** No longer affects: df-libreoffice ** Summary changed: - [Upstream] Text color changed to black importing Office 2007 PPTX + Text color changed to black importing Office 2007 PPTX -- 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/384553 Title: Text color changed to black importing Office 2007 PPTX Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Fix Released Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org-impress 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in Impress via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/+attachment/602148/+files/MDOP.pptx && lowriter -nologo MDOP.pptx is that slide 54 text color looks as it does in the MS Office 2007 screenshot: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384553/+attachment/2303006/+files /libre-office%20bug%20384553.tar.bz2 -O ex.tar.bz2 && file-roller -h ex.tar.bz && cd vista && eog page54.jpg 4) What happened instead is the text is changed to black. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: openoffice.org-core 1:3.0.1-9ubuntu3 ProcEnviron: PATH=(custom, user) LANG=fr_FR@euro SHELL=/bin/bash SourcePackage: openoffice.org Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/384553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 462564] Re: [Upstream] Deleting a column in Writer deletes whole table
Reproducible in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c Upstream reporters have made multiple duplicate upstream reports over last couple years. ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Triaged -- 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/462564 Title: [Upstream] Deleting a column in Writer deletes whole table Status in LibreOffice: Confirmed Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Triaged Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt && lowriter -nologo test.odt is when one highlights the second column of the table -> secondary clicks -> Column -> Delete is only that column is deleted. Please see movie for more details: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv 4) What happens instead is the whole table is deleted. Reproducible in: lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status WORKAROUND: Split the table then delete the column. WORKAROUND: Use Word via WINE. Microsoft Office Word 2003 (11.5604.6505) apt-cache policy wine1.3 wine1.3: Installed: 1.3.28-0ubuntu1~ppa1~natty1 Candidate: 1.3.28-0ubuntu1~ppa1~natty1 Version table: *** 1.3.28-0ubuntu1~ppa1~natty1 0 500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status 1.3.15-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages ProblemType: Bug Architecture: amd64 Date: Wed Oct 28 09:43:20 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/462564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 669248] Re: Spreadsheet Prints Chart on Multiple Pages
Stephen Rasku, this is still reproducible, and has a WORKAROUND in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c If this still affects you, please perform the steps requested in https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/669248/comments/8 . -- 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/669248 Title: Spreadsheet Prints Chart on Multiple Pages Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Expired Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Calc via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/669248/+attachment/1718719/+files/Printing%20Bug.ods -O example.ods && localc -nologo example.ods is when one attempts to print via File -> Print the entire file is printed in one page as in the Excel screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/669248/+attachment/2635295/+files/excel.png . 4) What happens instead is the chart is printed across multiple pages. WORKAROUND: File -> Print Preview -> Format Page -> change drop down Scaling mode to Fit print range(s) on number of pages -> combo box Number of pages 1 -> OK button -> File -> Print ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openoffice.org-core 1:3.2.0-7ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Oct 31 15:14:01 2010 ExecutablePath: /usr/lib/openoffice/program/soffice.bin InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: openoffice.org To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/669248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save
This problem does not affect a brand new user if I create one. So it is maybe to do with having upgraded, and having old settings? How do I reset the relevant settings? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1833114/+subscriptions
[Desktop-packages] [Bug 901390] Re: error in crop after rotate image in draw
Not reproducible in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c ** No longer affects: libreoffice (Ubuntu) ** Project changed: df-libreoffice => libreoffice (Ubuntu) ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- 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/901390 Title: error in crop after rotate image in draw Status in libreoffice package in Ubuntu: Fix Released Bug description: When I scanned a page and i rotate the page 180º and then i tried to crop, the crop function doesnt work well in draw. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/901390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183368] Re: [upstream] EDITING: Find by format doesn't work with non-integer font sizes
EliCoten, this is no longer reproducible in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c Ctrl+H > Format > Size: 11.5 > OK > Find: Hello > Find Next and the Hello with a 11.5 pt was highlighted. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** No longer affects: libreoffice (Ubuntu) ** Project changed: df-libreoffice => libreoffice (Ubuntu) ** Changed in: libreoffice (Ubuntu) Importance: Low => Undecided ** Changed in: libreoffice (Ubuntu) Status: Confirmed => New ** Changed in: libreoffice (Ubuntu) Remote watch: Document Foundation Bugzilla #64918 => None ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- 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/1183368 Title: [upstream] EDITING: Find by format doesn't work with non-integer font sizes Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:4.0.2-0ubuntu1 Candidate: 1:4.0.2-0ubuntu1 Version table: *** 1:4.0.2-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1183368/+attachment/3691990/+files/example.odt && lowriter --nologo example.odt Ctrl+H -> click dropdown box Search for -> button More Options -> button Format... -> in the Text Format(Search) window tab Font in text box Size type 11.5 -> button OK and underneath the Search dropdown box it notes 11.5, as it does in Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit). 4) What happens instead is it displays 12. However, it still successfully searches and finds 11.5 so this is a cosmetic UI issue. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 23 15:01:20 2013 MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-04-30 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1183368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1093765] Re: [upstream] switching paragraph style changes character orientation
Reproducible verbatim as per Bug Description in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c Given this is upstreamed already -> Triaged ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Triaged -- 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/1093765 Title: [upstream] switching paragraph style changes character orientation Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:4.0.2-0ubuntu1 Candidate: 1:4.0.2-0ubuntu1 Version table: *** 1:4.0.2-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/+attachment/3688368/+files/test-bug1093765.doc && lowriter --nologo test-bug1093765.doc is select all -> change combo box Apply Style from Text Body to Heading 1 and the text style changes, preserving the character order. 4) What happens instead is: (Example text=) טקסט לדוגמה changes to: טקסט לדוגמה (=Example text) Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit) changes it to: =)טקסט לדוגמהExample text( ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-core 1:3.6.2~rc2-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Wed Dec 26 11:20:42 2012 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-10-19 (67 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1093765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 879985] Re: "Remove hyperlink" also caused font of non-hyperlinked letters to become bold
Norman Roscher, this is tested fixed in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** No longer affects: df-libreoffice ** Changed in: libreoffice (Ubuntu) Status: Expired => Fix Released -- 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/879985 Title: "Remove hyperlink" also caused font of non-hyperlinked letters to become bold Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.3-3ubuntu2 Candidate: 1:3.4.3-3ubuntu2 Version table: *** 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/879985/+attachment/2567116/+files/example.odt && lowriter -nologo example.odt is one secondary clicks the hyperlink -> primary click Remove Hyperlink and the hyperlink is removed without any other changes to any other words in the document. 4) What happens instead is the hyperlink is removed but the word to the left is bolded erroneously. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice-writer 1:3.4.3-3ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Sat Oct 22 18:12:40 2011 InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-10-13 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/879985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1002097] Re: Sheet() function does not work upon opening .xlsx file
Dereck Wonnacott, this is tested fixed in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** No longer affects: libreoffice (Ubuntu) ** Project changed: df-libreoffice => libreoffice (Ubuntu) ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Fix Released ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- 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/1002097 Title: Sheet() function does not work upon opening .xlsx file Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.5.3-0ubuntu1 Candidate: 1:3.5.3-0ubuntu1 Version table: *** 1:3.5.3-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 3) What is expected to happen in Calc is when one uses the SHEET function and saves to .xlsx, upon reopening it still works. 4) What happens instead is one has #NAME? errors wherever the SHEET function was used. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-calc 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun May 20 20:14:18 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-05-03 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1002097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1035591] Re: Impress exporting to .pptx changes text color, font, and font size
Christopher Forester, this is tested fixed in: Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: libreoffice (Ubuntu) Status: Expired => Fix Released -- 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/1035591 Title: Impress exporting to .pptx changes text color, font, and font size Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.6.1~rc2-1ubuntu5 Candidate: 1:3.6.1~rc2-1ubuntu5 Version table: *** 1:3.6.1~rc2-1ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen via a terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1035591/+attachment/3256707/+files /pptxLayout-Bug%28reference%29.odp -O example.odp && loimpress --nologo example.odp Save As pptx is the resultant pptx looks as it did when an odp. 4) What happens instead is: + the text color changes from white to black + font changes from Albany to Arial + font size changes from 44/32 to 18 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.5.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sat Aug 11 12:04:53 2012 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (polkit-gnome-authentication-agent-1:1288): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed (polkit-gnome-authentication-agent-1:1288): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1035591/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
