[Desktop-packages] [Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
Here's another example that doesn't work in Kubuntu, but should:
https://mdn.github.io/web-speech-api/speak-easy-synthesis/
--
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/1866880
Title:
Firefox Speech Synthesis Not Working in Kubuntu
Status in KDE Base:
New
Status in firefox package in Ubuntu:
New
Bug description:
Modern web browsers, by spec, are supposed to support Speech
Synthesis. Although Firefox does indeed support it, it doesn't work in
Kubuntu 19.10.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
Something shorter, that you could type into the console (for testing)
is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after
doing this, but it doesn't working Kubuntu 19.10.
This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
20.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lonnie 1850 F pulseaudio
/dev/snd/controlC0: lonnie 1850 F pulseaudio
BuildID: 20200217142647
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 10 13:25:31 2020
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-03 (36 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NoProfiles: True
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76
To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/1866880/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859810] Re: [Inspiron 3268] audio esta mudo
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1859810 Title: [Inspiron 3268] audio esta mudo Status in pulseaudio package in Ubuntu: Expired Bug description: o audio esta mudo ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 15 08:28:41 2020 DistUpgraded: 2020-01-14 10:48:30,743 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0764] InstallationDate: Installed on 2020-01-11 (4 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 3268 ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=fd473502-2a31-400b-b303-9f46a74c2132 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2020-01-14 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 07F37C dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/25/2018:svnDellInc.:pnInspiron3268:pvr:rvnDellInc.:rn07F37C:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3268 dmi.product.sku: 0764 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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.0.1-1ubuntu1 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 xserver.bootTime: Mon Jan 13 20:38:33 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8758 vendor AOC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1859810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in Ubuntu MATE: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mate-session-manager package in Ubuntu: Confirmed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
Thanks a lot for the input, Ken! You were right, it is not related to BT, but to the sound devices being added and removed. I happend to have a Zoom microphone that can be connected as USB and creates a new audio interface (both input and output). Here are my new tests and findings: 1. Plug the Zoom USB device -> it appears in the Sound Settings Output Device and is automatically selected 2. Press Test and check the sound output -> the sound outputs on the internal speakers (NOK) After some investigation using pactl, I found how to fix the issue, for both the USB audio interface and the Bluetooth speaker: 1. Make sure the audio interface you want is connected (in my case, I connected both the USB and the Bluetooth speaker): $ pactl list short sinks 1 alsa_output.pci-_00_1f.3.analog-stereo module-alsa-card.c s16le 2ch 48000Hz SUSPENDED 6 alsa_output.usb-ZOOM_Corporation_H2n_-00.iec958-stereo module-alsa-card.c s16le 2ch 44100Hz SUSPENDED 7 bluez_sink.88_C6_26_1A_9E_AF.a2dp_sink module-bluez5-device.c s16le 2ch 44100Hz SUSPENDED 2. Play an audio stream, for instance a Youtube video. The output should come from the internal speakers, and can be seen in pactl as well: $ pactl list short sink-inputs 10 1 16 protocol-native.c float32le 2ch 44100Hz 3. Ask pactl to move the stream to the desired sink (output); for instance, the Bluetooth speaker: $ pactl move-sink-input 10 7 -> The sound outputs to the Bluetooth device! \o/ However, going back to Sound Settings (where the "Output Device" shows my Bluetooth Speaker) and clicking Test still outputs to the internal speakers Do you think it could be a GNOME issue? What should I do next? ** Summary changed: - After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker + After connecting an external output device (USB audio interface, Bluetooth speaker...), it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker ** Tags removed: a2dp -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: After connecting an external output device (USB audio interface, Bluetooth speaker...), it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
[Desktop-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Changed in: ubuntu-mate Status: New => Confirmed ** Information type changed from Public Security to Private Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in Ubuntu MATE: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mate-session-manager package in Ubuntu: Confirmed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865316] Re: Desktop blinks / flashes after unlocking the system ubuntu 18.04.4 (nvidia + amdgpu)
How do i do that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1865316 Title: Desktop blinks / flashes after unlocking the system ubuntu 18.04.4 (nvidia + amdgpu) Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: My ubuntu desktop gnome3 is started flashing after unlocking the machine, i tired lock and unlock twise still the problem remains. OS: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic System configuration Processor: AMD Ryzen 7-3750H processor, 2.3GHz Base speed (6MB cache, up to 4.0 GHz) Memory & Storage: 8GB DDR4 2400MHz RAM upgradeable upto 32GB RAM with| NVIDIA GeForce GTX 1650 GDDR5 4GB VRAM Graphics| Storage: 1TB 5400RPM 2.5' HDD + PCIe NVMe 256GB M.2 SSD please help me to resolve this issue --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-01 (7 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 Tags: bionic Uname: Linux 5.5.8-050508-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/1865316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=9cb7406d543b8db15e455903566fb72a23235c75 https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=6e93cf440908a87a1e30aec76bd54d52e0ad136c https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=2f2ea9613515dc90b75d32f6955dbf9d18876fde -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Some recent commits in BlueZ 5.54 suggest wide band support is being prepared starting in kernel 5.6: https://git.kernel.org/pub/scm/bluetooth/bluez.git Unfortunately both that kernel and bluez version seem to be too new to realistically make it into Ubuntu 20.04. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
*** This bug is a duplicate of bug 1860697 *** https://bugs.launchpad.net/bugs/1860697 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1860697, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug is no longer a duplicate of bug 1867474 [Dell Vostro 5590] PCI/internal sound card not detected ** This bug has been marked a duplicate of bug 1860697 Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 -- 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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 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:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
** Summary changed: - PCI/internal sound card not detected + [Dell Vostro 5590] PCI/internal sound card not detected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Tags added: champagne rls-ff-incoming -- 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/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) Status in mutter package in Ubuntu: Confirmed Bug description: When I play a video with mpv (or e.g. Firefox), it works just fine. When this video is fullscreened (e.g. in mpv by pressing f), the screen quickly turns off, and switches resolution modes in such a rate the screen is unusable. The native resolution of the screen is 1440p, but Xorg somehow increases the size to 3424x1926 for the fullscreen, then quickly switches back to 1440p, before increasing it again. As soon as the video is de-fullscreened (by pressing f again in mpv, or esc in Firefox), the funny resolution switching stops and the system is usable again. This also happens with the modesetting 2d-driver. This does not happen with Wayland. This can be seen in the Xorg-log: [20.215] (II) intel(0): EDID vendor "JDI", prod id 0 [20.215] (II) intel(0): Printing DDC gathered Modelines: [20.215] (II) intel(0): Modeline "2560x1440"x0.0 245.12 2560 2608 2640 2720 1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP) [ 258.869] (II) intel(0): resizing framebuffer to 3424x1926 [ 258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 268.955] (II) intel(0): resizing framebuffer to 2560x1440 [ 269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 270.383] (II) intel(0): resizing framebuffer to 3424x1926 [ 270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 271.852] (II) intel(0): resizing framebuffer to 2560x1440 [ 271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 273.294] (II) intel(0): resizing framebuffer to 3424x1926 [ 273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none When the resolution is increased, the Kernel complains about the framebuffer size: [ 269.830034] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. 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 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 00:00:07 2020 DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2259] MachineType: LENOVO 20LES01W00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET52W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LES01W00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LES01W00 dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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:
[Desktop-packages] [Bug 1797734] Re: slow calculator startup
That's a good case for keeping this bug logged here under gnome- calculator. Maybe we should just drop the snap and default to the deb. I'll assign this bug to ubuntu-meta for that... Although to say something is not physically possible is just inviting people to prove that statement wrong. It is technically true, but misses the main goal of just being fast enough that people don't notice. That is technically possible still. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: New Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867529] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) with PCA
OK, this bug has to be in the python3-swiftclient module. The real
problem is that Ubuntu is behind on versions. The latest version is
3.9.0 while the version in the snap is 3.5.0. Are you required to use
the snap version? If not you might want to try one of the installs
below.
* Stable tarball install - https://launchpad.net/duplicity/+download
* Daily duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/daily-dev-trunk
* Latest pip builds - “sudo pip install duplicity"
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => In Progress
** Changed in: duplicity
Milestone: None => 0.8.12
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1867529
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) with PCA
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
New
Bug description:
Same kind of bug after last fix :
I am using duplicity 0.8.11.1607 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200315T171233Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(util.fsdecode(source_path.name)))
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
520, in request
resp = self.send(prep, **send_kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
630, in send
r = adapter.send(request, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/adapters.py", line
460, in send
for i in request.body:
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/utils.py", line
279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/86/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1867529/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867529] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) with PCA
** Also affects: duplicity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1867529
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) with PCA
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
Same kind of bug after last fix :
I am using duplicity 0.8.11.1607 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200315T171233Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(util.fsdecode(source_path.name)))
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
520, in request
resp = self.send(prep, **send_kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
630, in send
r = adapter.send(request, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/adapters.py", line
460, in send
for i in request.body:
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/utils.py", line
279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/86/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1867529/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal
Excellent, thank you! ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/918 Importance: Unknown Status: Unknown -- 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/1867548 Title: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Bug description: As soon as the Keyboard Shortcuts tab window is invoked in the Settings Application, Right Alt key is switched off system-wide. This happens suddenly even without any action from the user - just simple invoking of the window is enough to break the settings. This obviously happens because of the new setting in the Keyboard Shortcuts appeared in focal: Alternate Characters Key. It sets Right Alt by default immediately as this window is opened. This setting doesn't have the Not Set option, so it is even not easy to switch back to the normal behavior. This setting can be unset only through the GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options - Key to choose the 3rd level - uncheck the box Right Alt. But this is not a good workaround since the Alt key setting will be destroyed again as soon as Keyboard Shortcuts are visited in Settings next time. The reasonable workaround seems to be introduction an option Not Set in the setting Alternate Characters Key and making it default. This will fix this bug and will introduce a sane default value because not every keyboard layout has a third-option for the keys. This is quite significant UX flaw since nothing should be changed without explicit user action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 22:33:08 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-04-25 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1867548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal
Thank you for the prompt response and for considering the report! The upstream issue: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/918 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #918 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/918 -- 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/1867548 Title: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal Status in gnome-control-center package in Ubuntu: Confirmed Bug description: As soon as the Keyboard Shortcuts tab window is invoked in the Settings Application, Right Alt key is switched off system-wide. This happens suddenly even without any action from the user - just simple invoking of the window is enough to break the settings. This obviously happens because of the new setting in the Keyboard Shortcuts appeared in focal: Alternate Characters Key. It sets Right Alt by default immediately as this window is opened. This setting doesn't have the Not Set option, so it is even not easy to switch back to the normal behavior. This setting can be unset only through the GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options - Key to choose the 3rd level - uncheck the box Right Alt. But this is not a good workaround since the Alt key setting will be destroyed again as soon as Keyboard Shortcuts are visited in Settings next time. The reasonable workaround seems to be introduction an option Not Set in the setting Alternate Characters Key and making it default. This will fix this bug and will introduce a sane default value because not every keyboard layout has a third-option for the keys. This is quite significant UX flaw since nothing should be changed without explicit user action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 22:33:08 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-04-25 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
I'm having the exact same issue, it's also caused by 150% fractional scaling in my case. I'm also noticing a lot of screen tearing when playing videos. All problems (resolution switching and screen tearing) disappear when I revert the scaling to 100%. -- 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/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) Status in mutter package in Ubuntu: Confirmed Bug description: When I play a video with mpv (or e.g. Firefox), it works just fine. When this video is fullscreened (e.g. in mpv by pressing f), the screen quickly turns off, and switches resolution modes in such a rate the screen is unusable. The native resolution of the screen is 1440p, but Xorg somehow increases the size to 3424x1926 for the fullscreen, then quickly switches back to 1440p, before increasing it again. As soon as the video is de-fullscreened (by pressing f again in mpv, or esc in Firefox), the funny resolution switching stops and the system is usable again. This also happens with the modesetting 2d-driver. This does not happen with Wayland. This can be seen in the Xorg-log: [20.215] (II) intel(0): EDID vendor "JDI", prod id 0 [20.215] (II) intel(0): Printing DDC gathered Modelines: [20.215] (II) intel(0): Modeline "2560x1440"x0.0 245.12 2560 2608 2640 2720 1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP) [ 258.869] (II) intel(0): resizing framebuffer to 3424x1926 [ 258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 268.955] (II) intel(0): resizing framebuffer to 2560x1440 [ 269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 270.383] (II) intel(0): resizing framebuffer to 3424x1926 [ 270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 271.852] (II) intel(0): resizing framebuffer to 2560x1440 [ 271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 273.294] (II) intel(0): resizing framebuffer to 3424x1926 [ 273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none When the resolution is increased, the Kernel complains about the framebuffer size: [ 269.830034] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. 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 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 00:00:07 2020 DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2259] MachineType: LENOVO 20LES01W00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET52W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LES01W00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LES01W00 dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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
[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
I have Asus ROG GX501VIK laptop with same issue. Device: Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog] Solution from comment #8 worked like a charm. -- 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/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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 failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
*** This bug is a duplicate of bug 1861395 ***
https://bugs.launchpad.net/bugs/1861395
Duplicate of LP:1861395
Per LP:1861395 both 5.4.0-17 (from the Kernel Team's Unstable PPA) and
5.4.0-18 (from -proposed) seems to fixes it for me.
** This bug has been marked a duplicate of bug 1861395
system hang: i915 Resetting rcs0 for hang on rcs0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on
[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal
Applicable spot in the source: https://gitlab.gnome.org/GNOME/gnome-control- center/-/blob/master/panels/keyboard/cc-alt-chars-key-dialog.c#L103 -- 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/1867548 Title: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal Status in gnome-control-center package in Ubuntu: Confirmed Bug description: As soon as the Keyboard Shortcuts tab window is invoked in the Settings Application, Right Alt key is switched off system-wide. This happens suddenly even without any action from the user - just simple invoking of the window is enough to break the settings. This obviously happens because of the new setting in the Keyboard Shortcuts appeared in focal: Alternate Characters Key. It sets Right Alt by default immediately as this window is opened. This setting doesn't have the Not Set option, so it is even not easy to switch back to the normal behavior. This setting can be unset only through the GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options - Key to choose the 3rd level - uncheck the box Right Alt. But this is not a good workaround since the Alt key setting will be destroyed again as soon as Keyboard Shortcuts are visited in Settings next time. The reasonable workaround seems to be introduction an option Not Set in the setting Alternate Characters Key and making it default. This will fix this bug and will introduce a sane default value because not every keyboard layout has a third-option for the keys. This is quite significant UX flaw since nothing should be changed without explicit user action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 22:33:08 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-04-25 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal
Thanks for your report! I could easily reproduce this design flaw, which really should be fixed before the release of Ubuntu 20.04 IMO. It's an upstream thing, so it would be great if you could also file an upstream issue: https://gitlab.gnome.org/GNOME/gnome-control-center/issues If you do, please post a comment here with the URL to the upstream issue. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Tags added: rls-ff-incoming -- 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/1867548 Title: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal Status in gnome-control-center package in Ubuntu: Confirmed Bug description: As soon as the Keyboard Shortcuts tab window is invoked in the Settings Application, Right Alt key is switched off system-wide. This happens suddenly even without any action from the user - just simple invoking of the window is enough to break the settings. This obviously happens because of the new setting in the Keyboard Shortcuts appeared in focal: Alternate Characters Key. It sets Right Alt by default immediately as this window is opened. This setting doesn't have the Not Set option, so it is even not easy to switch back to the normal behavior. This setting can be unset only through the GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options - Key to choose the 3rd level - uncheck the box Right Alt. But this is not a good workaround since the Alt key setting will be destroyed again as soon as Keyboard Shortcuts are visited in Settings next time. The reasonable workaround seems to be introduction an option Not Set in the setting Alternate Characters Key and making it default. This will fix this bug and will introduce a sane default value because not every keyboard layout has a third-option for the keys. This is quite significant UX flaw since nothing should be changed without explicit user action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 22:33:08 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-04-25 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11
I can get sound to work with a 5.4 kernel - but it's still not great... I haven't found a UCM file that let's it just work yet. What does work is using the alsactl -f downloaded/asound.state.txt bit and then VLC is able to play sound with Audio device set to chtmax98090, Direct hardware device without any conversions. My most recent attempt had me force installing (to ignore other depends) the Gallium deb http://apt.galliumos.org/pool/main/g/galliumos-baytrail/galliumos-baytrail_3.0_all.deb (this still lets the above alsa restore, vlc bit work, but pulseaudio fails to load) -- 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/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832885] Re: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lirc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1832885 Title: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 Status in lirc package in Ubuntu: Confirmed Bug description: I tried to install vdr. lirc comes as a dependency... ProblemType: Package DistroRelease: Ubuntu 19.04 Package: lirc 0.10.1-5.2 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 Date: Fri Jun 14 21:14:27 2019 ErrorMessage: installed lirc package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: lirc Title: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1832885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867548] [NEW] Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal
Public bug reported: As soon as the Keyboard Shortcuts tab window is invoked in the Settings Application, Right Alt key is switched off system-wide. This happens suddenly even without any action from the user - just simple invoking of the window is enough to break the settings. This obviously happens because of the new setting in the Keyboard Shortcuts appeared in focal: Alternate Characters Key. It sets Right Alt by default immediately as this window is opened. This setting doesn't have the Not Set option, so it is even not easy to switch back to the normal behavior. This setting can be unset only through the GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options - Key to choose the 3rd level - uncheck the box Right Alt. But this is not a good workaround since the Alt key setting will be destroyed again as soon as Keyboard Shortcuts are visited in Settings next time. The reasonable workaround seems to be introduction an option Not Set in the setting Alternate Characters Key and making it default. This will fix this bug and will introduce a sane default value because not every keyboard layout has a third-option for the keys. This is quite significant UX flaw since nothing should be changed without explicit user action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 22:33:08 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-04-25 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug focal -- 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/1867548 Title: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal Status in gnome-control-center package in Ubuntu: New Bug description: As soon as the Keyboard Shortcuts tab window is invoked in the Settings Application, Right Alt key is switched off system-wide. This happens suddenly even without any action from the user - just simple invoking of the window is enough to break the settings. This obviously happens because of the new setting in the Keyboard Shortcuts appeared in focal: Alternate Characters Key. It sets Right Alt by default immediately as this window is opened. This setting doesn't have the Not Set option, so it is even not easy to switch back to the normal behavior. This setting can be unset only through the GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options - Key to choose the 3rd level - uncheck the box Right Alt. But this is not a good workaround since the Alt key setting will be destroyed again as soon as Keyboard Shortcuts are visited in Settings next time. The reasonable workaround seems to be introduction an option Not Set in the setting Alternate Characters Key and making it default. This will fix this bug and will introduce a sane default value because not every keyboard layout has a third-option for the keys. This is quite significant UX flaw since nothing should be changed without explicit user action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 22:33:08 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-04-25 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865298] Re: [FFe] Request for update: HPLIP 3.20.3
Upstream (Debian) has fixed the Python 3.8 support, overtaking exactly the patch which we are using. They are only renaming all patches and so it does not look that obvious. The version I ask for getting synced is hplip_3.20.3+dfsg0-1 from Debian unstable: https://packages.debian.org/sid/hplip Here is the full debian/changelog: https://metadata.ftp- master.debian.org/changelogs//main/h/hplip/hplip_3.20.3+dfsg0-1_changelog The Python 3.8 patch got introduced in version 3.20.2+dfsg0-2 already. It is named 0072-Fix-building-with-Python-3.8.patch and you dee by the attached build log that the package actually builds under Focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1865298 Title: [FFe] Request for update: HPLIP 3.20.3 Status in hplip package in Ubuntu: New Bug description: Version 3.20.3 of HPLIP was released in March supporting these new printers: HP Neverstop Laser MFP 1200n HP Neverstop Laser MFP 1201n HP Neverstop Laser MFP 1200nw HP Neverstop Laser MFP 1202nw HP Laser NS MFP 1005n HP Neverstop Laser 1000n HP Neverstop Laser 1001nw HP Laser NS 1020n HP ScanJet Pro 2000 s2 HP ScanJet Pro 3000 s4 HP ScanJet Pro N4000 snw1 HP ScanJet Enterprise Flow 5000 s5 HP ScanJet Enterprise Flow N7000 snw1 Version 3.20.2 of HPLIP was released in February but had a severe bug (bug 1866291) making many users not able to print. The bug is fixed in version 3.20.3. 3.20.2 got withdrawn on HP's web site. To extend the range of hardware devices supported in Focal we should get this HPLIP 3.20.3 into Focal. There is no file containing information about what has been changed or added in version 3.20.3 compared to 3.19.12. There is also no public version control system where one could see the changes. The only information is that the devices listed above are newly supported in 3.20.3. HPLIP 3.20.3 got already packaged for Debian Unstable and there is no Ubuntu-specific change left which is not contained in the Debian package. Therefore I request the sync of the Debian package (hplip_3.20.3+dfsg0-1) into Focal. I have tested this Debian package of HPLIP 3.20.3 now and it seems that it is working so far. I can print and scan both via network and USB and also start GUI tools like hp-toolbox and hp-setup. hp-toolbox correctly lists jobs, settable options, and ink levels and with hp- setup I was able to create print queues for my printer. My printer is the HP OfficeJet Pro 8730 which is already supported for a longer time and I do not see any difference, especially no regression compared to older versions of HPLIP. Logs of the package build with pbuilder and of the package update on a Focal system are attached. See comments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1865298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865298] Re: [FFe] Request for update: HPLIP 3.20.3
>Hans Joachim Desserud, the Ubuntu delta is small, only a patch to fix the build with Python 3.8.The patch file is debian/patches/python3.8.diff. Yes, I saw the Ubuntu delta was small. However, at the time the Debian changelog didn't mention python 3.8 so I didn't know if that part was resolved in Debian or not. It didn' seem to integrate the Ubuntu patch, but a) Debian could have added an equivalent patch or b) upstream had fixed python 3.8 support or c) a merge would be needed. Most likely a merge would be needed, but a bit tricky to tell. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1865298 Title: [FFe] Request for update: HPLIP 3.20.3 Status in hplip package in Ubuntu: New Bug description: Version 3.20.3 of HPLIP was released in March supporting these new printers: HP Neverstop Laser MFP 1200n HP Neverstop Laser MFP 1201n HP Neverstop Laser MFP 1200nw HP Neverstop Laser MFP 1202nw HP Laser NS MFP 1005n HP Neverstop Laser 1000n HP Neverstop Laser 1001nw HP Laser NS 1020n HP ScanJet Pro 2000 s2 HP ScanJet Pro 3000 s4 HP ScanJet Pro N4000 snw1 HP ScanJet Enterprise Flow 5000 s5 HP ScanJet Enterprise Flow N7000 snw1 Version 3.20.2 of HPLIP was released in February but had a severe bug (bug 1866291) making many users not able to print. The bug is fixed in version 3.20.3. 3.20.2 got withdrawn on HP's web site. To extend the range of hardware devices supported in Focal we should get this HPLIP 3.20.3 into Focal. There is no file containing information about what has been changed or added in version 3.20.3 compared to 3.19.12. There is also no public version control system where one could see the changes. The only information is that the devices listed above are newly supported in 3.20.3. HPLIP 3.20.3 got already packaged for Debian Unstable and there is no Ubuntu-specific change left which is not contained in the Debian package. Therefore I request the sync of the Debian package (hplip_3.20.3+dfsg0-1) into Focal. I have tested this Debian package of HPLIP 3.20.3 now and it seems that it is working so far. I can print and scan both via network and USB and also start GUI tools like hp-toolbox and hp-setup. hp-toolbox correctly lists jobs, settable options, and ink levels and with hp- setup I was able to create print queues for my printer. My printer is the HP OfficeJet Pro 8730 which is already supported for a longer time and I do not see any difference, especially no regression compared to older versions of HPLIP. Logs of the package build with pbuilder and of the package update on a Focal system are attached. See comments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1865298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
No fixes yet! -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867529] [NEW] UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) with PCA
Public bug reported:
Same kind of bug after last fix :
I am using duplicity 0.8.11.1607 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200315T171233Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(util.fsdecode(source_path.name)))
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File "/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py",
line 520, in request
resp = self.send(prep, **send_kwargs)
File "/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py",
line 630, in send
r = adapter.send(request, **kwargs)
File "/snap/duplicity/86/usr/lib/python3/dist-packages/requests/adapters.py",
line 460, in send
for i in request.body:
File "/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/utils.py",
line 279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/86/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
** Affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1867529
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) with PCA
Status in duplicity package in Ubuntu:
New
Bug description:
Same kind of bug after last fix :
I am using duplicity 0.8.11.1607 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200315T171233Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(util.fsdecode(source_path.name)))
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display
And here we are in March 2020 and I still get a small @$$ cursor. I mean come on man, I'm pretty sure than since you said that the fix was merged LibreOffice and surely many other snaps have been rebuilt. I am using LibreOffice snap version 6.4.1.2 and still the cursor looks awful, small and black (where instead I have a white cursor on my system). I have this problem with nearly every other snap, only a small amount do actually respect the HiDPI and the theme of the cursor being consistent with the rest of my OS. The only ones that do work properly are Visual Studio Code, Blender and GIMP -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: Fix Released Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display
Here we are in March 2020 and I still have a small @$$ cursor in LibreOffice snap version 6.4.1.2. What the hell? I'm pretty sure the snap has been rebuilt since that fix that you say it's been merged. And it's not only with LibreOffice but with EVERY OTHER SNAP APP! -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: Fix Released Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866813] Re: chromium moved profile without warning on deb->snap transition
So this is a bug in the snap package? or might be a bug in snap itself? (as it's not using the standard chromium settings directory) Where do I file the bug report? I'm not concerned, it already copied data from secure partition to unsecured location. It should be protected against this. -- 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/1866813 Title: chromium moved profile without warning on deb->snap transition Status in chromium-browser package in Ubuntu: Invalid Bug description: From what I've read on the snap package it copied the profile. My profile was kept on encrypted drive and bind mounted to .config/chromium Freely copying user data, most often delicate (passwords, browser history) without any warning is a bad thing. At least I'd expect apt warn me that the profile will move. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797734] Re: slow calculator startup
It is not physically possible to ever get a snap to start as fast as a native application. The entire purpose of a snap is that it uses its own set of dependencies, which means that by definition it cannot share those dependencies with other applications on the system, which means that they must be loaded separately, which will take longer, use more system resources, etc. snaps should be used for applications which (a) are difficult to package, and/or (b) want to be used across multiple versions where prerequisites might change, and/or (c) snaps downsides are not as relevant (for example, they are left running for longer periods of time and are large enough that they aren't expected to start quickly, to amortize the increased start time and resource usage). None of those criteria hold true for a desktop calculator utility. We need to get to the point where I can hit the calculator button on the keyboard and a calculator window appears virtually instantaneously. gnome-calculator was always too slow to start, but now it's far slower: it's moving in exactly the wrong direction. Using it as a way to experiment with snaps just gives both snaps and gnome-calculator a bad reputation. This bug is not trying to say "we must improve snap startup times". This bug is trying to say "gnome-calculator is not an appropriate application to be snapped and should be changed back to a native application". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Confirmed Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825760] Re: multiple results for the same program
*** This bug is a duplicate of bug 1790814 *** https://bugs.launchpad.net/bugs/1790814 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1825760 Title: multiple results for the same program Status in gnome-software package in Ubuntu: Confirmed Bug description: If I search for a program, I see multiple results, making it confusing what to install. If I search for "gimp" I see 2 different programs with the same icon and similar names. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.30.6-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 17:23:37 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Has anyone found a solution to this problem? I have it too, my computer is an HP Envy x360 Convertible. Any help would be greatly appreciated! -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 518966] Re: Wrong pitch and crackling sound with 5.1 output on Extigy USB card
I can confirm that there seems to be a regression in the alsa audio
driver. I was trying this soundcard directly with alsa and get
distoreted audio and rumble in *some* apps.
--
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/518966
Title:
Wrong pitch and crackling sound with 5.1 output on Extigy USB card
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Binary package hint: pulseaudio
Since i upgraded to Karmic, my 5.1 sound output on my creative labs extigy
USB card is broken.
The previous release did work with alsa, and was working fine.
Now with Pulseaudio, the sound is only working correctly with stereo output,
with 5.1, the sound is crackling, and the pitch is too high.
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Extigy [Sound Blaster Extigy], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jean-luc 2681 F pulseaudio
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xfe9fc000 irq 29'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100100'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Extigy'/'Creative Technology Ltd. Sound Blaster Extigy at
usb-:00:1a.0-2, full speed'
Mixer name : 'USB Mixer'
Components : 'USB041e:3000'
Controls : 23
Simple ctrls : 17
Date: Mon Feb 8 19:48:40 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: alsa-driver
Uname: Linux 2.6.31-19-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/518966/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867514] Re: crashed when attempting to install lbry from software cente gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1858414 *** https://bugs.launchpad.net/bugs/1858414 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1858414, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Package changed: ubuntu => gnome-shell (Ubuntu) ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1867514/+attachment/5337166/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1867514/+attachment/5337168/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1867514/+attachment/5337172/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1867514/+attachment/5337173/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1867514/+attachment/5337174/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1867514/+attachment/5337176/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1867514/+attachment/5337177/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1858414 gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867514 Title: crashed when attempting to install lbry from software cente gnome- shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Thinkpad T470s Reinstalled Origin: Ubuntu Label: Ubuntu Suite: focal Version: 20.04 Codename: focal Date: Fri, 24 Jan 2020 6:58:25 UTC Architectures: amd64 i386 Components: main restricted Description: Ubuntu Focal 20.04 and preformed updates then rebooted. Attempted to change the theme to bright and the screen flickered but nothing changed, had Firefox downloading files in the background. Opened the software center to install LBRY when the screen froze then flicker and reset with the error report. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 19:57:44 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-03-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: PCI/internal sound card not detected
Ok, I will check this once more in a few days. Thanks for your support. :) -- 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/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841783] Re: Update to 1.2.0?
** Description changed: - The source was split in rc2, Debian didn't follow the change and we are + The source was split in rc2, Debian didn't follow the change, and we are in sync, do we want to update? + + Speex and SpeexDSP + + https://git.xiph.org/?p=speex.git;a=summary + + https://git.xiph.org/?p=speexdsp.git;a=summary -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speex in Ubuntu. https://bugs.launchpad.net/bugs/1841783 Title: Update to 1.2.0? Status in speex package in Ubuntu: Triaged Status in speex package in Debian: New Bug description: The source was split in rc2, Debian didn't follow the change, and we are in sync, do we want to update? Speex and SpeexDSP https://git.xiph.org/?p=speex.git;a=summary https://git.xiph.org/?p=speexdsp.git;a=summary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/1841783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: PCI/internal sound card not detected
The sof-firmware was just merged to linux-firmware last week, maybe it needs to wait for a couple of more days. -- 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/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867510] [NEW] Realtek ALC255 cannot play at higher than 48 khz - defaults to generic Intel driver?
Public bug reported: Hi. I am trying to use an onboard Realtek ALC255 soundcard to play audio files that are 192khz. The card supports sampling rates up to 192khz and the machine (Asus mini PC) successfully plays them at that rate under Windows. However, under Ubuntu 18.04(and Debian 10), the sampling rate is maxed out at 48 Khz. Changing the Alsa configuration to force a higher sampling rate (or to play without resampling) has no effect. I tried to upgrade the Linux kernel to this one https://drive.google.com/drive/folders/16OBmEmWPYncLOT-QVlo6vkyy3Ar819aX (unsigned 5.021) as I hoped it contains custom drivers for ALC255, but the result is still the same. Any idea if this has been solved in any kernel version? regards Christo ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/1867510 Title: Realtek ALC255 cannot play at higher than 48 khz - defaults to generic Intel driver? Status in alsa-driver package in Ubuntu: New Bug description: Hi. I am trying to use an onboard Realtek ALC255 soundcard to play audio files that are 192khz. The card supports sampling rates up to 192khz and the machine (Asus mini PC) successfully plays them at that rate under Windows. However, under Ubuntu 18.04(and Debian 10), the sampling rate is maxed out at 48 Khz. Changing the Alsa configuration to force a higher sampling rate (or to play without resampling) has no effect. I tried to upgrade the Linux kernel to this one https://drive.google.com/drive/folders/16OBmEmWPYncLOT- QVlo6vkyy3Ar819aX (unsigned 5.021) as I hoped it contains custom drivers for ALC255, but the result is still the same. Any idea if this has been solved in any kernel version? regards Christo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867466] Re: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the ba
I can't give you a photo or a video because I had to restart the computer because it was unusable I also add that being stuck at the desk with a double click on the desk the last program I had used in this case firefox which was always open , so I managed to report the bug otherwise I would not have been able to do it because everything was blocked, I also helped myself with alt + f2. I don't know which application was affected, a user told me gnome-shell however everything that was seen on the screen was affected except the programs, bar on the left, bar on the top and desk. The activity button worked only if you pressed the windows button from the keyboard, clicking on it with the mouse nothing so everything else I have talked about so far. Even once apoerto from the keyboard anything you touched on that screen nothing happened so I had to press it again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867466 Title: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the bar nor turn off the computer, only the open tabs work Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the bar nor turn off the computer, only the open tabs work. Even some app icons that I closed don't show up and if I click on all apps it doesn't work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 21:33:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1867466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: PCI/internal sound card not detected
linux-image-generic is already the newest version (5.4.0.18.22). pulseaudio is already the newest version (1:13.99.1-1ubuntu1). linux-firmware is already the newest version (1.186). alsa-ucm-conf is already the newest version (1.2.2-1). uname -a Linux Vostro-5590 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux But audio is still not working dmesg shows this error: [4.126575] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [4.126578] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [4.126579] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [4.126847] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I'm attaching complete dmesg output Thanks ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+attachment/5337136/+files/dmesg.txt -- 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/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867466] Re: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the ba
Can you please provide a photo or video of the problem? Also let us know which applications are affected? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- 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/1867466 Title: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the bar nor turn off the computer, only the open tabs work Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the bar nor turn off the computer, only the open tabs work. Even some app icons that I closed don't show up and if I click on all apps it doesn't work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 21:33:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1867466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866146] Re: GNOME Shell 3.35.91 extension's preferences doesn't load
** Tags added: fixed-upstream ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1866146 Title: GNOME Shell 3.35.91 extension's preferences doesn't load Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Using Ubuntu Focal Fossa development with gnome-shell 3.35.91 and preferences for extensions doesn't load. Tried opening using the browser, gnome-tweaks, or the new extensions app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 12:36:15 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-03 (518 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-10 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867406] Re: When the dock is located at the bottom of the screen it is difficult to rearrange the icons within it
** Summary changed: - Ubuntu 20.04 Dock/Taskbar icons + When the dock is located at the bottom of the screen it is difficult to rearrange the icons within it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867406 Title: When the dock is located at the bottom of the screen it is difficult to rearrange the icons within it Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When the taskbar/dock is located at the bottom of the screen it is near impossible to rearrange the icons within it. I posted to a forum and one other user confirmed he has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867337] Re: even after login the login page was displaying everywhere.
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: New Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. 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: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) NonfreeKernelModules: wl Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal third-party-packages Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
Thanks for the update Peter. That makes this bug apparently closed. Anyone still experiencing issues should open new bugs of their own. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1797734] Re: slow calculator startup
Last month some of Canonical engineering met up for a regular conference. There a couple of talks were given about what's being done to speed up snap launch times. I was surprised and encouraged there were a couple of efforts in progress. So better performance is coming... For this particular bug however, we might be in the wrong place. Any improvement in performance would be in some snap* project, not just in the gnome-calculator package. Maybe this bug needs to be moved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Confirmed Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1368147] Re: Lenovo Thinkpad Twist: Mobile Broadbad not working any more
I do not use this laptop any more. So I am closing this bug. ** Changed in: network-manager (Ubuntu) Status: Incomplete => Invalid -- 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/1368147 Title: Lenovo Thinkpad Twist: Mobile Broadbad not working any more Status in network-manager package in Ubuntu: Invalid Bug description: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click "Enable Mobile Broadband" in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying "Connection activation failed, (32) The connection was not supportedby oFono". I am using Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
*** This bug is a duplicate of bug 1867474 *** https://bugs.launchpad.net/bugs/1867474 Did you install the linux-firmware from the -proposed? It is also possible the latest linux-firmware is not in the -proposed yet, please wait for a couple of more days. -- 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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 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:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
The bug seems to have "gone away" when using a DVD of an early March beta version of Focal Fossa 20.04. It boots very happily with no obvious display problems. Sorry that I could not track down exactly what the problem was. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No
[Desktop-packages] [Bug 1586771] Re: unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04.
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1586771 Title: unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04. Status in network-manager package in Ubuntu: Incomplete Bug description: Previously Wifi was in working condition By adding extra packages from software updates -> Additional Drivers. But now I can not able to connect with wifi. It only shows in Air Plane mode. I am using Laptop Thinkpad T520 OS = ubuntu gnome 16.04 Network card = Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (Centrino Advanced-N 6205 AGN) Kernel version = 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 29 18:26:15 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-16 (42 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.1.1 dev enp0s25 proto static metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.105 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected/org/freedesktop/NetworkManager/Devices/1 enp0s25 dacd31ad-8949-42a6-8115-142800960f1c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1586771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
