[Desktop-packages] [Bug 1033141] Re: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound running media players like Clementine, VLC, SMPlayer and Gnome-MPlay
I'm really sorry this issue went unanswered for so long. The backlog we've accrued here is truly unfortunate. We'd really like to see the situation improve, but with over 3000 open bugs, manually testing each has become virtually impossible. The aim in pinging neglected bugs such as this is to allow those still effected to get their issue back on the radar. Is this still an issue for you? -- 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/1033141 Title: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound running media players like Clementine, VLC, SMPlayer and Gnome-MPlayer Status in alsa-driver package in Ubuntu: Incomplete Bug description: I'm not sure about the package but there's a bug with my sound. A lot of cracks. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: maico 1846 F pulseaudio /dev/snd/controlC2: maico 1846 F pulseaudio /dev/snd/controlC0: maico 1846 F pulseaudio /dev/snd/pcmC0D0p: maico 1846 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfcffc000 irq 43' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1028043e,00100101' Controls : 34 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'DigitalCamera'/'PixArt Imaging Inc. Digital_Camera at usb-:00:1d.1-1, full speed' Mixer name : 'USB Mixer' Components : 'USB093a:2900' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 2 Mono: Capture 0 [0%] [30.00dB] [on] Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xfe97c000 irq 17' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 24 Simple ctrls : 4 Date: Sun Aug 5 03:02:18 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Áudio embutido - HDA Intel Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07N90W dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/17/2010:svnDellInc.:pnVostro230:pvr00:rvnDellInc.:rn07N90W:rvrA02:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Vostro 230 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1033141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 774542] Re: [ICH4 - Intel ICH6, playback] No sound at all
Thanks for the update Steven. I’ll close the bug. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Won't Fix -- 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/774542 Title: [ICH4 - Intel ICH6, playback] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Both 10.10 and 11.04 have no sound for LE1600 Tablet ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: solarboy 1246 F pulseaudio Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with STAC9758,59 at irq 17' Mixer name : 'SigmaTel STAC9758,59' Components : 'AC97a:83847658' Controls : 50 Simple ctrls : 37 CheckboxSubmission: 3fa4bb708fb73202cfcfe0c9bb22f401 CheckboxSystem: c925ed66fbb6fb95ab27315f9d025b66 Date: Sat Apr 30 16:44:48 2011 InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH6 failed Symptom_Card: Internal Audio - Intel ICH6 Symptom_DevicesInUse: 1246 Symptom_Type: No sound at all Title: [ICH4 - Intel ICH6, playback] No sound at all UpgradeStatus: Upgraded to natty on 2011-04-30 (0 days ago) dmi.bios.date: 12/19/2006 dmi.bios.vendor: Motion Computing - LE1600 dmi.bios.version: A12 dmi.board.name: Compal DX20 dmi.board.vendor: Compal Computer Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal Computer Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnMotionComputing-LE1600:bvrA12:bd12/19/2006:svnMotionComputing:pnLE1600:pvrA0:rvnCompalComputerCorporation:rnCompalDX20:rvrNone:cvnCompalComputerCorporation:ct10:cvrN/A: dmi.product.name: LE1600 dmi.product.version: A0 dmi.sys.vendor: Motion Computing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/774542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245200] Re: [ Philips Freevents , ALC260, playback] No sound at all
Hi Philip, thank you for your detailed response. Your help with this is much appreciated. I’m really sorry to all effected that this bug went untouched for so long, but I must agree that this is not an issue much worth pursuing any longer. Closing. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Won't Fix -- 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/1245200 Title: [ Philips Freevents ,ALC260, playback] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: No sound on anything whether playing cd/dvd or listening to music /radio there's just no sound, i have an hda-intel ALC260 on a philips freevents laptop. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio CurrentDmesg: [ 142.597606] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [ 226.036095] usb 3-1: USB disconnect, device number 2 [ 267.538113] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Date: Sun Oct 27 14:54:41 2013 InstallationDate: Installed on 2013-10-26 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080013 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080013:bd05/10/2006:svnDIXONSXP:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: DIXONSXP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 694407] Re: [ICH - SiS SI7012] Playback problem
I'm so sorry this issue went unanswered for so long. The backlog we've
accrued here is truly unfortunate. We'd really like to see the situation
improve, but with over 3000 open bugs, manually testing each has become
virtually impossible. The aim in pinging neglected bugs such as this is
to allow those still effected to get their issue back on the radar.
I take it this is no longer an issue then. Closing. Thanks for the
update Adrian.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
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/694407
Title:
[ICH - SiS SI7012] Playback problem
Status in alsa-driver package in Ubuntu:
Invalid
Bug description:
No sound after initial opening of Diablo II when running under Wine
Ubuntu 10.04 LTS
Wine 1.2
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: adrian 1332 F pulseaudio
adrian21093 F winecfg.exe
/dev/snd/pcmC0D0p: adrian 1332 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'SI7012'/'SiS SI7012 with AD1888 at irq 18'
Mixer name : 'Analog Devices AD1888'
Components : 'AC97a:41445368'
Controls : 45
Simple ctrls : 31
Date: Sat Dec 25 22:37:22 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SelectedCard: 0 SI7012 ICH - SiS SI7012
SourcePackage: alsa-driver
Symptom: audio
Title: [ICH - SiS SI7012] Playback problem
dmi.bios.date: 10/08/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: 760GXK8MC
dmi.board.vendor: WinFast
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/08/2005:svn:pn:pvr:rvnWinFast:rn760GXK8MC:rvr:cvn:ct3:cvr:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/694407/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866444] [NEW] [MacBook2, 1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem
Public bug reported: What you expected to happen Settings -> Sound -> Input to list internal mic (to test orange bars for recording from internal mic) What actually happened Settings -> Sound -> Input only lists "Digital Input (S/PDIF)" (no bars move because no digital input connected) If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program" 1. Open Settings 2. Select Sound setting 3. Select Input tab -- NOTE: ultimately, I want recording to work in apps such as Chrome, Firefox, Zoom, etc. NOTE 2: mic recording was last working in Ubuntu 18.04.x (32-bit) instance on *same* MacBook hardware (this installation went corrupt so I can't reverify it still works unfortunately - I will add to this issue if I get the cycles to reinstall or at your request) NOTE 3: interestingly enough, while using "ubuntu-bug" it was able to record from the mic on the 1st (of 2 tests the bug collector initiated). -- $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 from "apt list --installed" alsa-base/bionic,bionic,bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installed] alsa-utils/bionic,bionic,now 1.1.3-1ubuntu1 amd64 [installed] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_76_86_generic_63 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1c: chinarut 1724 F...m pulseaudio /dev/snd/controlC0: chinarut 1724 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 22:41:25 2020 InstallationDate: Installed on 2020-01-24 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Intel failed Symptom_Type: Only some of inputs are working Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "screenshot of Sound setting with missing internal mic input" https://bugs.launchpad.net/bugs/1866444/+attachment/5334434/+files/Ubuntu%2018.04.4%20%28amd64%29%20Macbook%202%2C1%20-%20Settings%20-%20Sound%20-%20Input.png -- 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/1866444 Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: What you expected to happen Settings -> Sound -> Input to list internal mic (to test orange bars for recording from internal mic) What actually happened Settings -> Sound -> Input only lists "Digital Input (S/PDIF)" (no bars move because no digital input connected) If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program" 1. Open Settings 2. Select Sound setting 3. Select Input tab -- NOTE: ultimately, I want recording to work in apps such as Chrome, Firefox, Zoom, etc. NOTE 2: mic recording was last working in Ubuntu 18.04.x (32-bit) instance on *same* MacBook hardware (this installation went corrupt so I can't reverify it still works unfortunately - I will add to this issue if I get the cycles to reinstall or at your request) NOTE 3: interestingly enough, while using "ubuntu-bug" it was able to record from the mic on the 1st (of 2 tests the bug collector initiated). -- $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 from "apt list --installed" alsa-base/bionic,bionic,bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installed] alsa-utils/bionic,bionic,now 1.1.3-1ubuntu1 amd64
[Desktop-packages] [Bug 1033141] Re: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound running media players like Clementine, VLC, SMPlayer and Gnome-MPlay
Wow! I've got an answer exactly 7 years and 7 months Later. -- 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/1033141 Title: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound running media players like Clementine, VLC, SMPlayer and Gnome-MPlayer Status in alsa-driver package in Ubuntu: Incomplete Bug description: I'm not sure about the package but there's a bug with my sound. A lot of cracks. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: maico 1846 F pulseaudio /dev/snd/controlC2: maico 1846 F pulseaudio /dev/snd/controlC0: maico 1846 F pulseaudio /dev/snd/pcmC0D0p: maico 1846 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfcffc000 irq 43' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1028043e,00100101' Controls : 34 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'DigitalCamera'/'PixArt Imaging Inc. Digital_Camera at usb-:00:1d.1-1, full speed' Mixer name : 'USB Mixer' Components : 'USB093a:2900' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 2 Mono: Capture 0 [0%] [30.00dB] [on] Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xfe97c000 irq 17' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 24 Simple ctrls : 4 Date: Sun Aug 5 03:02:18 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Áudio embutido - HDA Intel Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07N90W dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/17/2010:svnDellInc.:pnVostro230:pvr00:rvnDellInc.:rn07N90W:rvrA02:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Vostro 230 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1033141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers
Have the same problems on p50 after installing NVIDIA-Linux-x86_64-440.64. Linux 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1826597 Title: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or trackpoint), does not respond to any input after installing ubuntu 19.04. The same machine has been working fine with ubuntu 16.04 and 18.10. To be more correct it is still working in 16.04 hwe which I'm dual booting. If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and replace with noveau drivers it works just fine (by the way there seems to be no other issues with the nvidia driver as of yet). I have also the nvidia-driver-390 also suggested in the graphical software updates tool, to no avail. I will attach relevant logs. Please let me know if there is more I should supply. And thanks for all your hard (and brilliant) work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 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 BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 20:36:18 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2019-04-26 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20EQS0PQ00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash synaptic_intertouch=0 vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS0PQ00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EQS0PQ00 dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858209] Re: Software has problem with .DEB package
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- 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/1858209 Title: Software has problem with .DEB package Status in gnome-software package in Ubuntu: Expired Bug description: Hello In Ubuntu 20.04 is a problem in Software! This not install my new Hibiscus .DEB Package I can not test this. control the systemstart time! control the cyberjack driver in recources "SP13" the old "SP09" is broken! Best Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1858209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858362] Re: /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_malloc:g_source_set_callback:g_task_attach_source
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1858362 Title: /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_malloc:g_source_set_callback:g_task_attach_source Status in nautilus package in Ubuntu: Expired Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/d27a750c5eaf7972c99c001fbb86cb2e6500594f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1858362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866428] Re: gnome-control-center crashed with SIGSEGV in gtk_flow_box_select_child()
*** This bug is a duplicate of bug 1866246 *** https://bugs.launchpad.net/bugs/1866246 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 #1866246, 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. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1866428/+attachment/5334420/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1866428/+attachment/5334422/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1866428/+attachment/5334425/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1866428/+attachment/5334426/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1866428/+attachment/5334427/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1866428/+attachment/5334428/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1866428/+attachment/5334429/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1866246 ** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1866428 Title: gnome-control-center crashed with SIGSEGV in gtk_flow_box_select_child() Status in gnome-control-center package in Ubuntu: New Bug description: Just installed. Did updtes. Went shopping for software. Somewhere around there, I got the error code. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.92-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 CurrentDesktop: Budgie:GNOME Date: Fri Mar 6 21:54:17 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-03-07 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200305) ProcCmdline: gnome-control-center ProcEnviron: SHELL=/bin/bash LANGUAGE=en_US LANG=en_US.UTF-8 XDG_RUNTIME_DIR= PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fcb898dc55e : cmp %rsi,(%rax) PC (0x7fcb898dc55e) ok source "%rsi" ok destination "(%rax)" (0x0041) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: gtk_flow_box_select_child () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in gtk_flow_box_select_child() 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-control-center/+bug/1866428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865907] Re: Loading IM context type 'ibus' failed
glib2.0 2.64.0-1 migrated to -release. Closing this bug. ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865907 Title: Loading IM context type 'ibus' failed Status in glib2.0 package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Bug description: Regression issue caused by recent system updates on Ubuntu 20.04 Focal Fossa (development branch) Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... reported below error in syslog or console as, ... (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 'ibus' failed (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch) ... and Pinyin input method does not work in these applications. Symptom occurs since I updated below 17 packages some hours before, gir1.2-ibus-1.0 gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs ibus ibus-data ibus-gtk ibus-gtk3 libglib2.0-0 libgtk-3-0 libgtk2.0-0 libibus-1.0-5 python3-ibus-1.0 current versions of above packages are, gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic] gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed] gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed] gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed] ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic] ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] libglib2.0-0/focal,now 2.63.5-2 amd64 [installed] libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed] libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed] libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed] python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 774542] Re: [ICH4 - Intel ICH6, playback] No sound at all
Hi Marcus, this is no longer an issue. Those tablets have been retired. Not sure what I can do to clear/close this report. - Steven B. Reeves On Thu, Mar 5, 2020 at 8:30 PM Marcus Tomlinson < marcus.tomlin...@canonical.com> wrote: > This release of Ubuntu is no longer receiving maintenance updates. If > this is still an issue on a maintained version of Ubuntu please let us > know. > > ** Changed in: alsa-driver (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/774542 > > Title: > [ICH4 - Intel ICH6, playback] No sound at all > > Status in alsa-driver package in Ubuntu: > Incomplete > > Bug description: > Both 10.10 and 11.04 have no sound for LE1600 Tablet > > ProblemType: Bug > DistroRelease: Ubuntu 11.04 > Package: alsa-base 1.0.24+dfsg-0ubuntu1 > ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 > Uname: Linux 2.6.38-8-generic i686 > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. > Architecture: i386 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: solarboy 1246 F pulseaudio > Card0.Amixer.info: >Card hw:0 'ICH6'/'Intel ICH6 with STAC9758,59 at irq 17' > Mixer name : 'SigmaTel STAC9758,59' > Components : 'AC97a:83847658' > Controls : 50 > Simple ctrls : 37 > CheckboxSubmission: 3fa4bb708fb73202cfcfe0c9bb22f401 > CheckboxSystem: c925ed66fbb6fb95ab27315f9d025b66 > Date: Sat Apr 30 16:44:48 2011 > InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release > i386 (20101007) > PackageArchitecture: all > ProcEnviron: >LANGUAGE=en_CA:en >LANG=en_CA.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH6 failed > Symptom_Card: Internal Audio - Intel ICH6 > Symptom_DevicesInUse: 1246 > Symptom_Type: No sound at all > Title: [ICH4 - Intel ICH6, playback] No sound at all > UpgradeStatus: Upgraded to natty on 2011-04-30 (0 days ago) > dmi.bios.date: 12/19/2006 > dmi.bios.vendor: Motion Computing - LE1600 > dmi.bios.version: A12 > dmi.board.name: Compal DX20 > dmi.board.vendor: Compal Computer Corporation > dmi.board.version: None > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Compal Computer Corporation > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnMotionComputing-LE1600:bvrA12:bd12/19/2006:svnMotionComputing:pnLE1600:pvrA0:rvnCompalComputerCorporation:rnCompalDX20:rvrNone:cvnCompalComputerCorporation:ct10:cvrN/A: > dmi.product.name: LE1600 > dmi.product.version: A0 > dmi.sys.vendor: Motion Computing > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/774542/+subscriptions > -- 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/774542 Title: [ICH4 - Intel ICH6, playback] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Both 10.10 and 11.04 have no sound for LE1600 Tablet ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: solarboy 1246 F pulseaudio Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with STAC9758,59 at irq 17' Mixer name : 'SigmaTel STAC9758,59' Components : 'AC97a:83847658' Controls : 50 Simple ctrls : 37 CheckboxSubmission: 3fa4bb708fb73202cfcfe0c9bb22f401 CheckboxSystem: c925ed66fbb6fb95ab27315f9d025b66 Date: Sat Apr 30 16:44:48 2011 InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH6 failed Symptom_Card: Internal Audio - Intel ICH6 Symptom_DevicesInUse: 1246 Symptom_Type: No sound at all Title: [ICH4 - Intel ICH6, playback] No sound at all UpgradeStatus: Upgraded to natty on 2011-04-30 (0 days ago) dmi.bios.date: 12/19/2006 dmi.bios.vendor: Motion Computing - LE1600 dmi.bios.version: A12 dmi.board.name: Compal DX20 dmi.board.vendor: Compal Computer Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal Computer Corporation dmi.chassis.version: N/A dmi.modalias:
Re: [Desktop-packages] [Bug 1245200] Re: [ Philips Freevents , ALC260, playback] No sound at all
Hi Marcus,Many thanks for the alert. I've added a post to the Launchpad thread so won't do a big repeat here but sufficient to say it was still unable to produce sound using Ubuntu 18.04. Sadly it died just last week and at 14 years of age lazarus is an unexpected event for it. The workaround for no sound was also pretty simple with a USB sound card which aways worked perfectly for not too much money. I can't see that more work on this is really justified. It seems to apply just to the Philips models which I don't think were produced for all that long so the law of diminishing returns is well and truly engaged with it.I was though rather touched to get your message and humbled that you and your colleagues were still keeping my original post in mind over 6 years after I wrote. Thank you for all that attention and thank you once again for the alert. Philip Philip Jones On Friday, 6 March 2020, 07:35:13 GMT, Marcus Tomlinson wrote: This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1245200 Title: [ Philips Freevents ,ALC260, playback] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: No sound on anything whether playing cd/dvd or listening to music /radio there's just no sound, i have an hda-intel ALC260 on a philips freevents laptop. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio CurrentDmesg: [ 142.597606] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [ 226.036095] usb 3-1: USB disconnect, device number 2 [ 267.538113] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Date: Sun Oct 27 14:54:41 2013 InstallationDate: Installed on 2013-10-26 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080013 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080013:bd05/10/2006:svnDIXONSXP:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: DIXONSXP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245200/+subscriptions -- 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/1245200 Title: [ Philips Freevents ,ALC260, playback] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: No sound on anything whether playing cd/dvd or listening to music /radio there's just no sound, i have an hda-intel ALC260 on a philips freevents laptop. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio CurrentDmesg: [ 142.597606] [UFW BLOCK] IN=eth0 OUT=
[Desktop-packages] [Bug 1245200] Re: [ Philips Freevents , ALC260, playback] No sound at all
Brilliant you still pursue this after all this time. My laptop sadly died just last week, but at 14 years of age and a life that included 2-3 years rough gaming by an enthusiastic teenager I reckon that's not bad. For a long time I used a workaround by buying a USB sound card which worked perfectly but it did have 18.04 installed on it and that didn't work either, though it had progressed by identifying the onboard sound card correctly without any fiddling with user configuration files, so that was progress of a sort. But despite knowing what was there it still seemed unable to identify it as a source in use. It was all a bit weird as in every other way the laptop flourished with my move to Linux and became a goto device for testing out any other problems I came across. Whether it's worth still pursuing is debateable. The laptop models are all pretty elderly and the workaround is straightforward at a pretty small expense. I certainly wouldn't feel let down if you abandoned the search at this point and appreciate you sticking with it for so long. -- 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/1245200 Title: [ Philips Freevents ,ALC260, playback] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: No sound on anything whether playing cd/dvd or listening to music /radio there's just no sound, i have an hda-intel ALC260 on a philips freevents laptop. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio CurrentDmesg: [ 142.597606] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [ 226.036095] usb 3-1: USB disconnect, device number 2 [ 267.538113] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Date: Sun Oct 27 14:54:41 2013 InstallationDate: Installed on 2013-10-26 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080013 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080013:bd05/10/2006:svnDIXONSXP:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: DIXONSXP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866059] Re: firefox-locale-* packages do not enable localization => post-install localization is not complete
This bug was fixed in the package firefox - 74.0+build2-0ubuntu2 --- firefox (74.0+build2-0ubuntu2) focal; urgency=medium * Really allow sideloading langpacks (LP: #1866059) - debian/build/rules.mk - debian/config/mozconfig.in -- Olivier Tilloy Fri, 06 Mar 2020 11:34:59 +0100 ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Released -- 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/1866059 Title: firefox-locale-* packages do not enable localization => post-install localization is not complete Status in firefox package in Ubuntu: Fix Released Bug description: On 2020-03-03 I installed a Focal system from the latest ISO image and chose the Italian localization at install time. The localization setting worked as expected, but not for Firefox: its interface is still in English. No "Italian" option shows up in the 'Preferences -> Language' menu (the menu is empty). The firefox-locale-it package is correctly installed. I tried installing firefox-locale-fr and restart Firefox, but I still got no French option in the Language menu. On the other hand letting Firefox download the language pack itself *does* work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
There are a few s2idle fixes and workaround in mainline kernel, and it may worth a try. If it can fix your problem, fixes can be backported to bionic latest mainline kernel: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.6-rc4/ instructions: https://askubuntu.com/questions/879888/how-do-i-update- kernel-to-the-latest-mainline-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor:
[Desktop-packages] [Bug 1866416] [NEW] Ubuntu 18.04 system freezes when attempting to switch user
Public bug reported: Ubuntu 18.04 freezes and must be manually powered down and rebooted when attempting to "Switch User". Prerequisites: - Use Ubuntu 18.04 - You need at least 2 users (e.g. user1 and user2) Expected behavior: - While logged in as any user, choose "Switch User" from top power drop down. - Click "Log in as another user" - Enter another user's credentials and login Bug behavior and steps to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - Returns to login screen, with prompt to enter user1 password - Click "Log in as another user" - RESULT: the screen freezes with no ability to type or move the mouse. It is never possible to login in as either user1 or user2 and the system must be manually powered down and restarted. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. "Switch User" ends up with the same freeze issue. NOTE 2: I've been getting crash reports at login that say "System program problem detected / Do you want to report the problem now?". I am unsure whether or not this is related, but the cat _usr_lib_gnome- session_gnome-session-check-accelerated.121.crash file in /var/crash provides the following information at the top of the report: ProblemType: Crash Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Mar 6 11:28:30 2020 DistroRelease: Ubuntu 18.04 ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated ExecutableTimestamp: 1525246842 ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 11:49:25 2020 InstallationDate: Installed on 2020-03-03 (2 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1866416 Title: Ubuntu 18.04 system freezes when attempting to switch user Status in gdm3 package in Ubuntu: New Bug description: Ubuntu 18.04 freezes and must be manually powered down and rebooted when attempting to "Switch User". Prerequisites: - Use Ubuntu 18.04 - You need at least 2 users (e.g. user1 and user2) Expected behavior: - While logged in as any user, choose "Switch User" from top power drop down. - Click "Log in as another user" - Enter another user's credentials and login Bug behavior and steps to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - Returns to login screen, with prompt to enter user1 password - Click "Log in as another user" - RESULT: the screen freezes with no ability to type or move the mouse. It is never possible to login in as either user1 or user2 and the system must be manually powered down and restarted. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. "Switch User" ends up with the same freeze issue. NOTE 2: I've been getting crash reports at login that say "System program problem detected / Do you want to report the problem now?". I am unsure whether or not this is related, but the cat _usr_lib_gnome- session_gnome-session-check-accelerated.121.crash file in /var/crash provides the following information at the top of the report: ProblemType: Crash Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Mar 6 11:28:30 2020 DistroRelease: Ubuntu 18.04 ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated ExecutableTimestamp: 1525246842 ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 11:49:25 2020
Re: [Desktop-packages] [Bug 694407] Re: [ICH - SiS SI7012] Playback problem
This was an old problem many years ago, I am suprised that I got this
notification now especially as I am now using 18.04LTS and 19.10.
On 05/03/2020 07:01, Marcus Tomlinson wrote:
> This release of Ubuntu is no longer receiving maintenance updates. If
> this is still an issue on a maintained version of Ubuntu please let us
> know.
>
> ** Changed in: alsa-driver (Ubuntu)
> Status: Confirmed => Incomplete
>
--
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/694407
Title:
[ICH - SiS SI7012] Playback problem
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
No sound after initial opening of Diablo II when running under Wine
Ubuntu 10.04 LTS
Wine 1.2
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: adrian 1332 F pulseaudio
adrian21093 F winecfg.exe
/dev/snd/pcmC0D0p: adrian 1332 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'SI7012'/'SiS SI7012 with AD1888 at irq 18'
Mixer name : 'Analog Devices AD1888'
Components : 'AC97a:41445368'
Controls : 45
Simple ctrls : 31
Date: Sat Dec 25 22:37:22 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SelectedCard: 0 SI7012 ICH - SiS SI7012
SourcePackage: alsa-driver
Symptom: audio
Title: [ICH - SiS SI7012] Playback problem
dmi.bios.date: 10/08/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: 760GXK8MC
dmi.board.vendor: WinFast
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/08/2005:svn:pn:pvr:rvnWinFast:rn760GXK8MC:rvr:cvn:ct3:cvr:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/694407/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865308] Re: gvfs fails to mount previously working SMB share (from nautilus)
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1865308 Title: gvfs fails to mount previously working SMB share (from nautilus) Status in gvfs package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: New Bug description: When accessing my SMB share (samba on linux/openwrt) Nautilus reports that the mount operation failed. I enabled gvfsd debug and got the following debug output. smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x55be028f8080 (GVfsBackendSmb) smb: Queued new job 0x55be028f9960 (GVfsJobMount) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 smb2: 10 smb2_credits: 10 dsdb_audit: 10 dsdb_json_audit: 10 dsdb_password_audit: 10 dsdb_password_json_audit: 10 dsdb_transaction_audit: 10 dsdb_transaction_json_audit: 10 dsdb_group_audit: 10 dsdb_group_json_audit: 10 Using netbios name DOOMELITE. Using workgroup WORKGROUP. smb: do_mount - URI = smb://openwrt/doom smb: do_mount - try #0 smbc_stat(smb://openwrt/doom) smb: auth_callback - kerberos pass smb: auth_callback - out: last_user = 'doommaster', last_domain = 'WORKGROUP' SMBC_server: server_n=[openwrt] server=[openwrt] -> server_n=[openwrt] server=[openwrt] Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied sitename_fetch: No stored sitename for realm '' internal_resolve_name: looking up openwrt#20 (sitename (null)) Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied no entry for openwrt#20 found. resolve_lmhosts: Attempting lmhosts lookup for name openwrt<0x20> startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name openwrt<0x20> resolve_hosts: getaddrinfo failed for name openwrt [Name or service not known] name_resolve_bcast: Attempting broadcast lookup for name openwrt<0x20> parse_nmb: packet id = 17529 nmb packet from 192.168.42.1(35072) header: id=17529 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=OPENWRT<20> rr_type=32 rr_class=1 ttl=259200 answers 0 char *. hex C0A82A01 Got a positive name query response from 192.168.42.1 ( 192.168.42.1 ) remove_duplicate_addrs2: looking for duplicate address/port pairs namecache_store: storing 1 address for openwrt#20: 192.168.42.1 Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied internal_resolve_name: returning 1 addresses: 192.168.42.1:0 Connecting to 192.168.42.1 at port 445 Socket options: SO_KEEPALIVE = 0 SO_REUSEADDR = 0 SO_BROADCAST = 0 TCP_NODELAY = 1 TCP_KEEPCNT = 9 TCP_KEEPIDLE = 7200 TCP_KEEPINTVL = 75 IPTOS_LOWDELAY = 0 IPTOS_THROUGHPUT = 0 SO_REUSEPORT = 0 SO_SNDBUF = 87040 SO_RCVBUF = 131072 SO_SNDLOWAT = 1 SO_RCVLOWAT = 1 SO_SNDTIMEO = 0 SO_RCVTIMEO = 0 TCP_QUICKACK = 1 TCP_DEFER_ACCEPT = 0 map_errno_from_nt_status: 32 bit codes: code=c20c smb: do_mount - [smb://openwrt/doom; 0] res = -1, cancelled = 0, errno = [103] 'Software caused connection abort' smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking smb: send_reply(0x55be028f9960), failed=1 (Failed to mount Windows share: Software caused connection abort) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1865308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 473089] Re: internal mic doesnt work dell inspiron 1545
Hello,
I do not have the Dell inspiron 1545 anymore
Tks for your help,
Best regards,
Alexander Gabirondo
On Thu, Mar 5, 2020, 3:34 PM Marcus Tomlinson <
marcus.tomlin...@canonical.com> wrote:
> This release of Ubuntu is no longer receiving maintenance updates. If
> this is still an issue on a maintained version of Ubuntu please let us
> know.
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/473089
>
> Title:
> internal mic doesnt work dell inspiron 1545
>
> Status in alsa-driver package in Ubuntu:
> Incomplete
>
> Bug description:
> I only upgrade from 9.04 to 9.10
> and my mic doesnt work :S
>
> ProblemType: Bug
> Architecture: i386
> ArecordDevices:
> List of CAPTURE Hardware Devices
>card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 2/2
> Subdevice #0: subdevice #0
> Subdevice #1: subdevice #1
> AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0: xndr 1762 F pulseaudio
>/dev/snd/pcmC0D0p: xndr 1762 F...m pulseaudio
> Card0.Amixer.info:
>Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 21'
> Mixer name : 'IDT 92HD71B7X'
> Components : 'HDA:111d76b2,102802aa,00100302'
> Controls : 32
> Simple ctrls : 19
> CheckboxCommand: alsa_record_playback
> CheckboxDescription:
>Pair a Bluetooth headset with your system. Then open the volume
> control application by right-clicking on the speaker icon in the panel and
> selecting "Sound Preferences". Select the "Input" tab and choose your
> Bluetooth device. Select the "Output" tab and choose your Bluetooth
> device. When you are done, click the Test button, then speak into the
> microphone. After a few seconds, your speech will be played back to you.
>
>Did you hear your speech played back?
> CheckboxTest: alsa_record_playback_bluetooth
> CurrentDmesg:
>[ 22.694064] sky2 eth0: enabling interface
>[ 22.694255] ADDRCONF(NETDEV_UP): eth0: link is not ready
>[ 25.841280] ppdev: user-space parallel port driver
>[ 33.512047] eth1: no IPv6 routers present
> Date: Tue Nov 3 13:58:58 2009
> DistroRelease: Ubuntu 9.10
> NonfreeKernelModules: wl
> Package: alsa-base 1.0.20+dfsg-1ubuntu5
> PackageArchitecture: all
> ProcEnviron:
>SHELL=/bin/bash
>LANG=en_US.UTF-8
> ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
> SourcePackage: alsa-driver
> Tags: checkbox-bug
> Uname: Linux 2.6.31-14-generic i686
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/473089/+subscriptions
>
--
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/473089
Title:
internal mic doesnt work dell inspiron 1545
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
I only upgrade from 9.04 to 9.10
and my mic doesnt work :S
ProblemType: Bug
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: xndr 1762 F pulseaudio
/dev/snd/pcmC0D0p: xndr 1762 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 21'
Mixer name : 'IDT 92HD71B7X'
Components : 'HDA:111d76b2,102802aa,00100302'
Controls : 32
Simple ctrls : 19
CheckboxCommand: alsa_record_playback
CheckboxDescription:
Pair a Bluetooth headset with your system. Then open the volume control
application by right-clicking on the speaker icon in the panel and selecting
"Sound Preferences". Select the "Input" tab and choose your Bluetooth device.
Select the "Output" tab and choose your Bluetooth device. When you are done,
click the Test button, then speak into the microphone. After a few seconds,
your speech will be played back to you.
Did you hear your speech played back?
CheckboxTest: alsa_record_playback_bluetooth
CurrentDmesg:
[ 22.694064] sky2 eth0: enabling interface
[ 22.694255] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 25.841280] ppdev: user-space parallel port driver
[ 33.512047] eth1: no IPv6 routers present
Date: Tue Nov 3 13:58:58 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: alsa-driver
Tags: checkbox-bug
Uname: Linux 2.6.31-14-generic i686
To manage
[Desktop-packages] [Bug 1865308] Re: gvfs fails to mount previously working SMB share (from nautilus)
I wondered why I am still alone, this is a quite essential feature which makes me wonder if there is anything else that I can do to determine the issue in case it cannot be replicated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1865308 Title: gvfs fails to mount previously working SMB share (from nautilus) Status in gvfs package in Ubuntu: Confirmed Bug description: When accessing my SMB share (samba on linux/openwrt) Nautilus reports that the mount operation failed. I enabled gvfsd debug and got the following debug output. smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x55be028f8080 (GVfsBackendSmb) smb: Queued new job 0x55be028f9960 (GVfsJobMount) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 smb2: 10 smb2_credits: 10 dsdb_audit: 10 dsdb_json_audit: 10 dsdb_password_audit: 10 dsdb_password_json_audit: 10 dsdb_transaction_audit: 10 dsdb_transaction_json_audit: 10 dsdb_group_audit: 10 dsdb_group_json_audit: 10 Using netbios name DOOMELITE. Using workgroup WORKGROUP. smb: do_mount - URI = smb://openwrt/doom smb: do_mount - try #0 smbc_stat(smb://openwrt/doom) smb: auth_callback - kerberos pass smb: auth_callback - out: last_user = 'doommaster', last_domain = 'WORKGROUP' SMBC_server: server_n=[openwrt] server=[openwrt] -> server_n=[openwrt] server=[openwrt] Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied sitename_fetch: No stored sitename for realm '' internal_resolve_name: looking up openwrt#20 (sitename (null)) Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied no entry for openwrt#20 found. resolve_lmhosts: Attempting lmhosts lookup for name openwrt<0x20> startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name openwrt<0x20> resolve_hosts: getaddrinfo failed for name openwrt [Name or service not known] name_resolve_bcast: Attempting broadcast lookup for name openwrt<0x20> parse_nmb: packet id = 17529 nmb packet from 192.168.42.1(35072) header: id=17529 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=OPENWRT<20> rr_type=32 rr_class=1 ttl=259200 answers 0 char *. hex C0A82A01 Got a positive name query response from 192.168.42.1 ( 192.168.42.1 ) remove_duplicate_addrs2: looking for duplicate address/port pairs namecache_store: storing 1 address for openwrt#20: 192.168.42.1 Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied internal_resolve_name: returning 1 addresses: 192.168.42.1:0 Connecting to 192.168.42.1 at port 445 Socket options: SO_KEEPALIVE = 0 SO_REUSEADDR = 0 SO_BROADCAST = 0 TCP_NODELAY = 1 TCP_KEEPCNT = 9 TCP_KEEPIDLE = 7200 TCP_KEEPINTVL = 75 IPTOS_LOWDELAY = 0 IPTOS_THROUGHPUT = 0 SO_REUSEPORT = 0 SO_SNDBUF = 87040 SO_RCVBUF = 131072 SO_SNDLOWAT = 1 SO_RCVLOWAT = 1 SO_SNDTIMEO = 0 SO_RCVTIMEO = 0 TCP_QUICKACK = 1 TCP_DEFER_ACCEPT = 0 map_errno_from_nt_status: 32 bit codes: code=c20c smb: do_mount - [smb://openwrt/doom; 0] res = -1, cancelled = 0, errno = [103] 'Software caused connection abort' smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking smb: send_reply(0x55be028f9960), failed=1 (Failed to mount Windows share: Software caused connection abort) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1865308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1866069] Re: Investigate segfault on Mir
Found the underlying bug in Mir. (Re-uploading to a texture from
multiple threads.)
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
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/1866069
Title:
Investigate segfault on Mir
Status in mesa package in Ubuntu:
Invalid
Bug description:
This occurs with the development version of Mir running on 18.04LTS
(not seen on later series). (This version of Mir can be installed from
ppa:mir-team/dev).
1. Start multiscreen Mir-on-X: miral-app -demo-server --x11-output
640x480:800x600.
2. Position windows side-by-side to make it easy to move cursor across
windows.
3. Drag the terminal window back and forth between windows.
Expect: everything works smoothly.
Actual: Eventually (can take 30sec) a core dump.
It looks like internal mesa state is inconsistent as src_mt is assigned with
intelImage->mt and not changed in ntel_miptree_copy_teximage() but...
...
multi-thre Thread 0x7fee68b117 In: intel_miptree_copy_teximage
L1438 PC: 0x7fee6bd1739a
(gdb) f 1
#1 0x7fee6bd1739a in intel_miptree_copy_teximage (brw=0x55e9f1a066a0,
intelImage=0x7fee58075fc0, dst_mt=0x7fee5807b120)
at ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1438
(gdb) p src_mt
$1 = (struct intel_mipmap_tree *) 0x0
(gdb) p intelImage->mt
$2 = (struct intel_mipmap_tree *) 0x7fee5807b120
Backtrace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fee6bd16ea6 in intel_miptree_copy_slice (brw=0x55e9f1a066a0,
src_mt=0x0, src_level=0, src_layer=0, dst_mt=0x7fee5807b120,
dst_level=0, dst_layer=0) at
../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1332
1332 ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c: No such file or
directory.
[Current thread is 1 (Thread 0x7fee68b11700 (LWP 7872))]
(gdb) bt
#0 0x7fee6bd16ea6 in intel_miptree_copy_slice (brw=0x55e9f1a066a0,
src_mt=0x0, src_level=0, src_layer=0, dst_mt=
0x7fee5807b120, dst_level=0, dst_layer=0) at
../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1332
#1 0x7fee6bd1739a in intel_miptree_copy_teximage (brw=0x55e9f1a066a0,
intelImage=0x7fee58075fc0, dst_mt=0x7fee5807b120)
at ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1438
#2 0x7fee6bd280e6 in intel_finalize_mipmap_tree (brw=0x55e9f1a066a0,
tObj=0x7fee58086910)
at ../src/mesa/drivers/dri/i965/intel_tex_validate.c:179
#3 0x7fee6bd281fb in brw_validate_textures (brw=0x55e9f1a066a0) at
../src/mesa/drivers/dri/i965/intel_tex_validate.c:219
#4 0x7fee6bce3932 in brw_prepare_drawing (ctx=0x55e9f1a066a0, ib=0x0,
index_bounds_valid=true, min_index=0, max_index=3)
at ../src/mesa/drivers/dri/i965/brw_draw.c:816
#5 0x7fee6bce4496 in brw_draw_prims (ctx=0x55e9f1a066a0,
prims=0x7fee68b10480, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001',
min_index=0, max_index=3, gl_xfb_obj=0x0, stream=0, indirect=0x0) at
../src/mesa/drivers/dri/i965/brw_draw.c:1148
#6 0x7fee6c0e4163 in _mesa_draw_arrays (ctx=0x55e9f1a066a0, mode=5,
start=0, count=4, numInstances=1, baseInstance=0, drawID=0)
at ../src/mesa/main/draw.c:374
#7 0x7fee6c0e48eb in _mesa_DrawArrays (mode=5, start=0, count=4) at
../src/mesa/main/draw.c:531
#8 0x7fee77148a8a in
mir::renderer::gl::Renderer::draw(mir::graphics::Renderable const&) const
(this=0x7fee58000b20, renderable=
...) at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:631
#9 0x7fee77147e13 in
mir::renderer::gl::Renderer::render(std::vector,
std::allocator > > const&) const
(this=0x7fee58000b20, renderables=std::vector of length 2, capacity 2 = {...})
at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:437
#10 0x7fee76f0c728 in
mir::compositor::DefaultDisplayBufferCompositor::composite(std::vector,
std::allocator > >&&)
(this=0x7fee5800c840, scene_elements=...)
at
/home/alan/display_server/mir/src/server/compositor/default_display_buffer_compositor.cpp:84
#11 0x7fee76f12781 in mir::compositor::CompositingFunctor::operator()()
(this=0x55e9f1b6a3a0)
at
/home/alan/display_server/mir/src/server/compositor/multi_threaded_compositor.cpp:141
#12 0x7fee76f18311 in std::__invoke_impl(std::__invoke_other,
mir::compositor::CompositingFunctor&) (__f=...) at
/usr/include/c++/7/bits/invoke.h:60
#13 0x7fee76f178b4 in
std::__invoke(mir::compositor::CompositingFunctor&)
(__fn=...)
at /usr/include/c++/7/bits/invoke.h:95
#14 0x7fee76f16ae0 in
std::reference_wrapper::operator()<>()
const (this=0x7fee68b10af0)
at /usr/include/c++/7/bits/refwrap.h:356
#15 0x7fee76f15aac in std::_Function_handler
>::_M_invoke(std::_Any_data const&) (__functor=...) at
/usr/include/c++/7/bits/std_function.h:316
#16 0x7fee76daedbc in
[Desktop-packages] [Bug 1866371] Re: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1866371 Title: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update Status in mutter package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu 20.04 (Gnome Shell) development version. Since I made the updates on 5th March, I have no more mouse cursor visible, on the login screen nor on the desktop session. Mouse is OK, as if I move it I can see some items / buttons highlighted, and if I click the mouse, it works well. I tried Yaru and DMZ Black themes, no cursor, it's completely invisible. I started several times, always no cursor. But if I switch to the Xorg (X11) session, mouse cursor is well back and visible. My graphic card : description: VGA compatible controller produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X] fabricant: Advanced Micro Devices, Inc. [AMD/ATI] identifiant matériel: 0 information bus: pci@:01:00.0 version: 00 bits: 64 bits horloge: 33MHz fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list rom configuration : driver=radeon latency=0 Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866371] Re: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1866371 Title: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update Status in mutter package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu 20.04 (Gnome Shell) development version. Since I made the updates on 5th March, I have no more mouse cursor visible, on the login screen nor on the desktop session. Mouse is OK, as if I move it I can see some items / buttons highlighted, and if I click the mouse, it works well. I tried Yaru and DMZ Black themes, no cursor, it's completely invisible. I started several times, always no cursor. But if I switch to the Xorg (X11) session, mouse cursor is well back and visible. My graphic card : description: VGA compatible controller produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X] fabricant: Advanced Micro Devices, Inc. [AMD/ATI] identifiant matériel: 0 information bus: pci@:01:00.0 version: 00 bits: 64 bits horloge: 33MHz fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list rom configuration : driver=radeon latency=0 Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 940919] Re: clock is not automatically set in live session
Thanks for the update Yogesh. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/940919 Title: clock is not automatically set in live session Status in Unity Control Center: Invalid Status in ubiquity package in Ubuntu: Invalid Status in unity-control-center package in Ubuntu: Invalid Bug description: Hello Launch a live session, choose a a language outside of the UTC (italian is UTC+1), when the live session will be launched the clock will be set to UTC instead of localized even if the net is working. expected A fully localized environenment at startup probably related to bug 940908 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 CasperVersion: 1.304 Date: Sat Feb 25 12:42:07 2012 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120225) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.2-0ubuntu2 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu2 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/940919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866222] Re: GNOME Shell crashed with signal 11
Here is a log with a few crashes. It seems to always come after a few of these: Mar 6 01:24:57 wolfenstein rtkit-daemon[1197]: Supervising 9 threads of 5 processes of 1 users. Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: message repeated 19 times: [ Supervising 9 threads of 5 processes of 1 users.] Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: Successfully made thread 122522 of process 122427 owned by '1000' RT at priority 10. The log lacks the last crash (~19:20) since I attached gdb to the running gnome-shell process but couldn't switch back to the console gdb was started from (frozen screen, but I could hear the video was still playing). Will try attaching through ssh from another computer next time. ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+attachment/5334373/+files/log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has crashed twice on me today. Unfortunately there's nothing in /var/crash. There's nothing in the journalctl log prior to the crash that explains it. I've attached a log of everything between when the crash happened and when I logged back in (though I suspect most of it is not relevant). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 13:04:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (201 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865308] Re: gvfs fails to mount previously working SMB share (from nautilus)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1865308 Title: gvfs fails to mount previously working SMB share (from nautilus) Status in gvfs package in Ubuntu: Confirmed Bug description: When accessing my SMB share (samba on linux/openwrt) Nautilus reports that the mount operation failed. I enabled gvfsd debug and got the following debug output. smb: g_vfs_backend_smb_init: default workgroup = 'NULL' smb: Added new job source 0x55be028f8080 (GVfsBackendSmb) smb: Queued new job 0x55be028f9960 (GVfsJobMount) INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 auth_audit: 10 auth_json_audit: 10 kerberos: 10 drs_repl: 10 smb2: 10 smb2_credits: 10 dsdb_audit: 10 dsdb_json_audit: 10 dsdb_password_audit: 10 dsdb_password_json_audit: 10 dsdb_transaction_audit: 10 dsdb_transaction_json_audit: 10 dsdb_group_audit: 10 dsdb_group_json_audit: 10 Using netbios name DOOMELITE. Using workgroup WORKGROUP. smb: do_mount - URI = smb://openwrt/doom smb: do_mount - try #0 smbc_stat(smb://openwrt/doom) smb: auth_callback - kerberos pass smb: auth_callback - out: last_user = 'doommaster', last_domain = 'WORKGROUP' SMBC_server: server_n=[openwrt] server=[openwrt] -> server_n=[openwrt] server=[openwrt] Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied sitename_fetch: No stored sitename for realm '' internal_resolve_name: looking up openwrt#20 (sitename (null)) Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied no entry for openwrt#20 found. resolve_lmhosts: Attempting lmhosts lookup for name openwrt<0x20> startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name openwrt<0x20> resolve_hosts: getaddrinfo failed for name openwrt [Name or service not known] name_resolve_bcast: Attempting broadcast lookup for name openwrt<0x20> parse_nmb: packet id = 17529 nmb packet from 192.168.42.1(35072) header: id=17529 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=OPENWRT<20> rr_type=32 rr_class=1 ttl=259200 answers 0 char *. hex C0A82A01 Got a positive name query response from 192.168.42.1 ( 192.168.42.1 ) remove_duplicate_addrs2: looking for duplicate address/port pairs namecache_store: storing 1 address for openwrt#20: 192.168.42.1 Opening cache file at /run/samba/gencache.tdb tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permission denied Opening /run/samba/gencache.tdb failed: Permission denied internal_resolve_name: returning 1 addresses: 192.168.42.1:0 Connecting to 192.168.42.1 at port 445 Socket options: SO_KEEPALIVE = 0 SO_REUSEADDR = 0 SO_BROADCAST = 0 TCP_NODELAY = 1 TCP_KEEPCNT = 9 TCP_KEEPIDLE = 7200 TCP_KEEPINTVL = 75 IPTOS_LOWDELAY = 0 IPTOS_THROUGHPUT = 0 SO_REUSEPORT = 0 SO_SNDBUF = 87040 SO_RCVBUF = 131072 SO_SNDLOWAT = 1 SO_RCVLOWAT = 1 SO_SNDTIMEO = 0 SO_RCVTIMEO = 0 TCP_QUICKACK = 1 TCP_DEFER_ACCEPT = 0 map_errno_from_nt_status: 32 bit codes: code=c20c smb: do_mount - [smb://openwrt/doom; 0] res = -1, cancelled = 0, errno = [103] 'Software caused connection abort' smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking smb: send_reply(0x55be028f9960), failed=1 (Failed to mount Windows share: Software caused connection abort) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1865308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 940919] Re: clock is not automatically set in live session
Hi Marcus Please close this 8 year old bug. Also thanks for responding. -- Yogesh Gupta Hyderabad, India +91 7207624465, *"Think GREEN, keep it on the SCREEN"* On Fri, Mar 6, 2020 at 3:44 AM Marcus Tomlinson < marcus.tomlin...@canonical.com> wrote: > This release of Ubuntu is no longer receiving maintenance updates. If > this is still an issue on a maintained version of Ubuntu please let us > know. > > ** Changed in: ubiquity (Ubuntu) >Status: Triaged => Incomplete > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (988582). > https://bugs.launchpad.net/bugs/940919 > > Title: > clock is not automatically set in live session > > Status in Unity Control Center: > Invalid > Status in ubiquity package in Ubuntu: > Incomplete > Status in unity-control-center package in Ubuntu: > Invalid > > Bug description: > Hello > Launch a live session, choose a a language outside of the UTC (italian > is UTC+1), when the live session will be launched the clock will be set to > UTC instead of localized even if the net is working. > expected > A fully localized environenment at startup > probably related to bug 940908 > ProblemType: Bug > DistroRelease: Ubuntu 12.04 > Package: gnome-control-center 1:3.3.90-0ubuntu2 > ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 > Uname: Linux 3.2.0-17-generic x86_64 > ApportVersion: 1.93-0ubuntu2 > Architecture: amd64 > CasperVersion: 1.304 > Date: Sat Feb 25 12:42:07 2012 > LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 > (20120225) > ProcEnviron: >TERM=xterm >PATH=(custom, no user) >LANG=it_IT.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > usr_lib_gnome-control-center: >activity-log-manager-control-center 0.9.2-0ubuntu2 >deja-dup21.90-0ubuntu1 >gnome-bluetooth 3.2.2-0ubuntu2 >indicator-datetime 0.3.90-0ubuntu1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/unity-control-center/+bug/940919/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/940919 Title: clock is not automatically set in live session Status in Unity Control Center: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in unity-control-center package in Ubuntu: Invalid Bug description: Hello Launch a live session, choose a a language outside of the UTC (italian is UTC+1), when the live session will be launched the clock will be set to UTC instead of localized even if the net is working. expected A fully localized environenment at startup probably related to bug 940908 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 CasperVersion: 1.304 Date: Sat Feb 25 12:42:07 2012 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120225) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.2-0ubuntu2 deja-dup21.90-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu2 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/940919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865555] Re: libxml2
People made me notice that I stopped reading at the first section, before the `apt-get -f install` bit… That multiarch breakage is fixed in the version currently blocked in propsed, starting with 2.9.10+dfsg-4 ** Changed in: libxml2 (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/186 Title: libxml2 Status in libxml2 package in Ubuntu: Fix Released Bug description: when i want to install a package for example reportbug this happens: Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libxml2-dev : Breaks: libxml2-dev:i386 (!= 2.9.10+dfsg-1ubuntu3) but 2.9.4+dfsg1-8ubuntu3 is to be installed libxml2-dev:i386 : Depends: libxml2:i386 (= 2.9.4+dfsg1-8ubuntu3) but 2.9.10+dfsg-1ubuntu3 is to be installed Breaks: libxml2-dev (!= 2.9.4+dfsg1-8ubuntu3) but 2.9.10+dfsg-1ubuntu3 is to be installed reportbug : Depends: python3-reportbug (= 7.6.0ubuntu1) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). And with apt --fix-broken install: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libxml2-dev:i386 The following packages will be upgraded: libxml2-dev:i386 1 upgraded, 0 newly installed, 0 to remove and 217 not upgraded. 1 not fully installed or removed. Need to get 0 B/799 kB of archives. After this operation, 30,7 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 540117 files and directories currently installed.) Preparing to unpack .../libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb ... Unpacking libxml2-dev:i386 (2.9.10+dfsg-1ubuntu3) over (2.9.4+dfsg1-8ubuntu3) .. . dpkg: error processing archive /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1 ubuntu3_i386.deb (--unpack): trying to overwrite shared '/usr/bin/xml2-config', which is different from othe r instances of package libxml2-dev:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libxml2 2.9.10+dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 20:46:30 2020 InstallationDate: Installed on 2020-01-23 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libxml2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866381] [NEW] evince no longer remembers last used folder/directory when saving
Public bug reported: On upgrading from Xubuntu 16.04 (xenial) to Xubuntu 18.04.2 LTS (bionic), evince no longer saves a copy of a downloaded document to the previously used directory for saving documents but defaults to $HOME every time. As a workaround, downgrading evince, evince-common, libevdocument3-4 and libevview3-3 from their bionic version 3.28.4-0ubuntu1 to their xenial version 3.18.2-1ubuntu4.6 restores the expected behaviour. For users unfamiliar, those old packages may be obtained for example from:- https://launchpad.net/ubuntu/xenial/amd64/evince/ Regards. ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: settings xubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1866381 Title: evince no longer remembers last used folder/directory when saving Status in evince package in Ubuntu: New Bug description: On upgrading from Xubuntu 16.04 (xenial) to Xubuntu 18.04.2 LTS (bionic), evince no longer saves a copy of a downloaded document to the previously used directory for saving documents but defaults to $HOME every time. As a workaround, downgrading evince, evince-common, libevdocument3-4 and libevview3-3 from their bionic version 3.28.4-0ubuntu1 to their xenial version 3.18.2-1ubuntu4.6 restores the expected behaviour. For users unfamiliar, those old packages may be obtained for example from:- https://launchpad.net/ubuntu/xenial/amd64/evince/ Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1866381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245020] Re: [Acer AO722] Internal microphone don't work
Thanks for the update Sushenjit. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Fix Released -- 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/1245020 Title: [Acer AO722] Internal microphone don't work Status in alsa-driver package in Ubuntu: Fix Released Bug description: The "Mic Boost" setting in Alsamixer reverts to zero after each boot and the microphone stops working until alsamixer setting is changed again. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sushenjit 2368 F pulseaudio /dev/snd/pcmC1D0p: sushenjit 2368 F...m pulseaudio /dev/snd/controlC0: sushenjit 2368 F pulseaudio Date: Sat Oct 26 13:13:55 2013 HibernationDevice: RESUME=UUID=67e8714a-d8e0-422e-b9fb-f41ebf64d499 InstallationDate: Installed on 2012-05-20 (524 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Lsusb: Bus 002 Device 004: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO722 MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b42fc94e-bbb7-444d-a5e8-25218dfc4101 ro elevator=noop quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-23 (3 days ago) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08: dmi.product.name: AO722 dmi.product.version: V1.08 dmi.sys.vendor: Acer --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sushenjit 2437 F pulseaudio /dev/snd/pcmC1D0p: sushenjit 2437 F...m pulseaudio /dev/snd/controlC0: sushenjit 2437 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=67e8714a-d8e0-422e-b9fb-f41ebf64d499 InstallationDate: Installed on 2012-05-20 (527 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Lsusb: Bus 002 Device 002: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO722 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b42fc94e-bbb7-444d-a5e8-25218dfc4101 ro elevator=noop quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-23 (6 days ago) UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo WifiSyslog: Oct 29 07:41:58 Arthur NetworkManager[1048]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted dmi.bios.date: 09/25/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnAcer:bvrV1.11:bd09/25/2012:svnAcer:pnAO722:pvrV1.11:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11: dmi.product.name: AO722 dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to:
[Desktop-packages] [Bug 1245020] Re: [Acer AO722] Internal microphone don't work
This problem is fixed in a later kernel update. It does not affect Ubuntu 18.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/1245020 Title: [Acer AO722] Internal microphone don't work Status in alsa-driver package in Ubuntu: Incomplete Bug description: The "Mic Boost" setting in Alsamixer reverts to zero after each boot and the microphone stops working until alsamixer setting is changed again. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sushenjit 2368 F pulseaudio /dev/snd/pcmC1D0p: sushenjit 2368 F...m pulseaudio /dev/snd/controlC0: sushenjit 2368 F pulseaudio Date: Sat Oct 26 13:13:55 2013 HibernationDevice: RESUME=UUID=67e8714a-d8e0-422e-b9fb-f41ebf64d499 InstallationDate: Installed on 2012-05-20 (524 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Lsusb: Bus 002 Device 004: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO722 MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b42fc94e-bbb7-444d-a5e8-25218dfc4101 ro elevator=noop quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-23 (3 days ago) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08: dmi.product.name: AO722 dmi.product.version: V1.08 dmi.sys.vendor: Acer --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sushenjit 2437 F pulseaudio /dev/snd/pcmC1D0p: sushenjit 2437 F...m pulseaudio /dev/snd/controlC0: sushenjit 2437 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=67e8714a-d8e0-422e-b9fb-f41ebf64d499 InstallationDate: Installed on 2012-05-20 (527 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Lsusb: Bus 002 Device 002: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO722 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b42fc94e-bbb7-444d-a5e8-25218dfc4101 ro elevator=noop quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-23 (6 days ago) UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo WifiSyslog: Oct 29 07:41:58 Arthur NetworkManager[1048]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted dmi.bios.date: 09/25/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnAcer:bvrV1.11:bd09/25/2012:svnAcer:pnAO722:pvrV1.11:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11: dmi.product.name: AO722 dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245020/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1866355] Re: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
*** This bug is a duplicate of bug 1863414 *** https://bugs.launchpad.net/bugs/1863414 ** This bug has been marked a duplicate of bug 1863414 Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage -- 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/1866355 Title: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used Status in libreoffice package in Ubuntu: New Bug description: python3-uno (1:6.4.0-0ubuntu7) wird eingerichtet ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-uno 1:6.4.0-0ubuntu7 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 CurrentDesktop: XFCE Date: Fri Mar 6 15:17:42 2020 InstallationDate: Installed on 2020-01-16 (49 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-01-21 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1866355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865555] Re: libxml2
you: * shouldn't use a development version if you don't know what you are doing * never use the -proposed pocket of a development release unless you are very clear on what you are doing, since that pocket is supposed to be consumed only by programs. ** Changed in: libxml2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/186 Title: libxml2 Status in libxml2 package in Ubuntu: Invalid Bug description: when i want to install a package for example reportbug this happens: Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libxml2-dev : Breaks: libxml2-dev:i386 (!= 2.9.10+dfsg-1ubuntu3) but 2.9.4+dfsg1-8ubuntu3 is to be installed libxml2-dev:i386 : Depends: libxml2:i386 (= 2.9.4+dfsg1-8ubuntu3) but 2.9.10+dfsg-1ubuntu3 is to be installed Breaks: libxml2-dev (!= 2.9.4+dfsg1-8ubuntu3) but 2.9.10+dfsg-1ubuntu3 is to be installed reportbug : Depends: python3-reportbug (= 7.6.0ubuntu1) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). And with apt --fix-broken install: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libxml2-dev:i386 The following packages will be upgraded: libxml2-dev:i386 1 upgraded, 0 newly installed, 0 to remove and 217 not upgraded. 1 not fully installed or removed. Need to get 0 B/799 kB of archives. After this operation, 30,7 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 540117 files and directories currently installed.) Preparing to unpack .../libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb ... Unpacking libxml2-dev:i386 (2.9.10+dfsg-1ubuntu3) over (2.9.4+dfsg1-8ubuntu3) .. . dpkg: error processing archive /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1 ubuntu3_i386.deb (--unpack): trying to overwrite shared '/usr/bin/xml2-config', which is different from othe r instances of package libxml2-dev:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libxml2 2.9.10+dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 20:46:30 2020 InstallationDate: Installed on 2020-01-23 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libxml2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866371] [NEW] Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update
Public bug reported: Hi, I run Ubuntu 20.04 (Gnome Shell) development version. Since I made the updates on 5th March, I have no more mouse cursor visible, on the login screen nor on the desktop session. Mouse is OK, as if I move it I can see some items / buttons highlighted, and if I click the mouse, it works well. I tried Yaru and DMZ Black themes, no cursor, it's completely invisible. I started several times, always no cursor. But if I switch to the Xorg (X11) session, mouse cursor is well back and visible. My graphic card : description: VGA compatible controller produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X] fabricant: Advanced Micro Devices, Inc. [AMD/ATI] identifiant matériel: 0 information bus: pci@:01:00.0 version: 00 bits: 64 bits horloge: 33MHz fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list rom configuration : driver=radeon latency=0 Thanks ! ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- 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/1866371 Title: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update Status in mutter package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Hi, I run Ubuntu 20.04 (Gnome Shell) development version. Since I made the updates on 5th March, I have no more mouse cursor visible, on the login screen nor on the desktop session. Mouse is OK, as if I move it I can see some items / buttons highlighted, and if I click the mouse, it works well. I tried Yaru and DMZ Black themes, no cursor, it's completely invisible. I started several times, always no cursor. But if I switch to the Xorg (X11) session, mouse cursor is well back and visible. My graphic card : description: VGA compatible controller produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X] fabricant: Advanced Micro Devices, Inc. [AMD/ATI] identifiant matériel: 0 information bus: pci@:01:00.0 version: 00 bits: 64 bits horloge: 33MHz fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list rom configuration : driver=radeon latency=0 Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing
Hi Olivier, Thanks for looking into this, much appreciated. Here's the output of the locale command: > $ locale > LANG=en_US.UTF-8 > LANGUAGE=en > LC_CTYPE="en_US.UTF-8" > LC_NUMERIC=fr_FR.UTF-8 > LC_TIME=fr_FR.UTF-8 > LC_COLLATE="en_US.UTF-8" > LC_MONETARY=fr_FR.UTF-8 > LC_MESSAGES="en_US.UTF-8" > LC_PAPER=fr_FR.UTF-8 > LC_NAME=fr_FR.UTF-8 > LC_ADDRESS=fr_FR.UTF-8 > LC_TELEPHONE=fr_FR.UTF-8 > LC_MEASUREMENT=fr_FR.UTF-8 > LC_IDENTIFICATION=fr_FR.UTF-8 > LC_ALL= The computer is operated in US english with FR regional settings. Here's the output of the command you gave me : > $ chromium --enable-logging=stderr > Gtk-Message: 17:08:26.449: Failed to load module "canberra-gtk-module" > Gtk-Message: 17:08:26.450: Failed to load module "canberra-gtk-module" > [810:810:0306/170827.138080:ERROR:sandbox_linux.cc(374)] > InitializeSandbox() called with multiple threads in process gpu-process. > [853:1:0306/170828.283307:ERROR:child_process_sandbox_support_impl_linux.cc(79)] > > FontService unique font name matching request did not receive a response. > [853:1:0306/170828.283625:ERROR:child_process_sandbox_support_impl_linux.cc(79)] > > FontService unique font name matching request did not receive a response. > [661:661:0306/170829.374429:INFO:CONSOLE(1127)] "Application Cache API > use is deprecated and will be removed in M82, around April 2020. See > https://www.chromestatus.com/features/6192449487634432 for more > details.", source: > https://docs.google.com/static/doclist/client/js/924573575-frame_bin.js > (1127) > [661:661:0306/170829.595400:INFO:CONSOLE(0)] "A cookie associated with > a cross-site resource at http://google.com/ was set without the > `SameSite` attribute. A future release of Chrome will only deliver > cookies with cross-site requests if they are set with `SameSite=None` > and `Secure`. You can review cookies in developer tools under > Application>Storage>Cookies and see more details at > https://www.chromestatus.com/feature/5088147346030592 and > https://www.chromestatus.com/feature/5633521622188032.;, source: > chrome-extension://ghbmnnjooekpmoecnnnilnnbdlolhkhi/_generated_background_page.html > > (0) > [661:661:0306/170829.595473:INFO:CONSOLE(0)] "A cookie associated with > a cross-site resource at https://google.com/ was set without the > `SameSite` attribute. A future release of Chrome will only deliver > cookies with cross-site requests if they are set with `SameSite=None` > and `Secure`. You can review cookies in developer tools under > Application>Storage>Cookies and see more details at > https://www.chromestatus.com/feature/5088147346030592 and > https://www.chromestatus.com/feature/5633521622188032.;, source: > chrome-extension://ghbmnnjooekpmoecnnnilnnbdlolhkhi/_generated_background_page.html > > (0) > [661:661:0306/170829.709280:INFO:CONSOLE(0)] "A cookie associated with > a cross-site resource at https://docs.google.com/ was set without the > `SameSite` attribute. A future release of Chrome will only deliver > cookies with cross-site requests if they are set with `SameSite=None` > and `Secure`. You can review cookies in developer tools under > Application>Storage>Cookies and see more details at > https://www.chromestatus.com/feature/5088147346030592 and > https://www.chromestatus.com/feature/5633521622188032.;, source: > chrome-extension://ghbmnnjooekpmoecnnnilnnbdlolhkhi/_generated_background_page.html > > (0) > [661:661:0306/170832.530031:WARNING:CONSOLE(0)] "A cookie associated > with a cross-site resource at https://ogs.google.com/ was set without > the `SameSite` attribute. A future release of Chrome will only deliver > cookies with cross-site requests if they are set with `SameSite=None` > and `Secure`. You can review cookies in developer tools under > Application>Storage>Cookies and see more details at > https://www.chromestatus.com/feature/5088147346030592 and > https://www.chromestatus.com/feature/5633521622188032.;, source: > chrome-search://local-ntp/local-ntp.html (0) > [661:661:0306/170832.530132:WARNING:CONSOLE(0)] "A cookie associated > with a cross-site resource at http://google.com/ was set without the > `SameSite` attribute. A future release of Chrome will only deliver > cookies with cross-site requests if they are set with `SameSite=None` > and `Secure`. You can review cookies in developer tools under > Application>Storage>Cookies and see more details at > https://www.chromestatus.com/feature/5088147346030592 and > https://www.chromestatus.com/feature/5633521622188032.;, source: > chrome-search://local-ntp/local-ntp.html (0) > [661:661:0306/170832.530221:WARNING:CONSOLE(0)] "A cookie associated > with a cross-site resource at https://google.com/ was set without the > `SameSite` attribute. A future release of Chrome will only deliver > cookies with cross-site requests if they are set with `SameSite=None` > and `Secure`. You can review cookies in developer tools under > Application>Storage>Cookies and
[Desktop-packages] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym
Comments #17 and #19 might be a different bug (bug 1866356). I'm not sure yet... -- 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/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in Libva: Fix Released Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in intel-vaapi-driver source package in Bionic: Confirmed Status in libva source package in Bionic: Confirmed Status in mesa source package in Bionic: Invalid Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866219] Re: Login screen hangs
Please start by uninstalling these extensions: b'org.gnome.shell' b'enabled-extensions' b"['dash-to- pa...@jderose9.github.com', 'system-moni...@paradoxxx.zero.gmail.com', 'cpufreq@konkor', 'no...@maestroschan.fr', 'system_moni...@bghome.gmail.com', 'systemi...@noctrl.eu', 'un...@hardpixel.eu', 'b...@yozoon.dev.gmail.com', 'gnome-radio@gnome- shell-exstensions.fffilo.github.com', 'services-syst...@abteil.org', 'ra...@hslbck.gmail.com', 'sensory-percept...@harlemsquirrel.github.io', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'Internet-Speed- Meter@TH3L0N3C0D3R']" We need to check if removing them makes a difference because so often gnome-shell bugs (and the login screen is gnome-shell) are caused by extensions. And we need to uninstall them and not just disable them because a buggy extension can still interfere even when disabled. ** Changed in: gnome-shell (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/1866219 Title: Login screen hangs Status in gnome-shell package in Ubuntu: Incomplete Bug description: One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. * lsb_release -rd: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 * Software Center version: 3.35.91 * What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully. * What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:02:36 2020 DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:39f2] InstallationDate: Installed on 2019-12-14 (82 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80S7 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-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN31WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 510-14ISK dmi.modalias:
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
I don't think that's necessary and probably not helpful. There are already multiple moving parts here so it would be easier to deal with if the theme was not changed simultaneously. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: New Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866369] [NEW] [snap] 80.0.3987.132 require new apparmor rules
Public bug reported: Since the snap upgrade to 80.0.3987.132, chromium keeps complaining about I/O errors that are apparently due to missing Apparmor rules. Here is what gets logged by "journalctl -f -o cat" when starting and closing chromium: AVC apparmor="DENIED" operation="unlink" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F4C6173742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000 AVC apparmor="DENIED" operation="rename_src" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F43757272656E742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" fsuid=1000 ouid=1000 audit: type=1400 audit(1583509664.429:3450): apparmor="DENIED" operation="unlink" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F4C6173742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000 audit: type=1400 audit(1583509664.429:3451): apparmor="DENIED" operation="rename_src" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F43757272656E742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" fsuid=1000 ouid=1000 AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F4C6173742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 AVC apparmor="DENIED" operation="unlink" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F43757272656E742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000 AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F43757272656E742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 audit: type=1400 audit(1583509664.433:3452): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F4C6173742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 audit: type=1400 audit(1583509664.433:3453): apparmor="DENIED" operation="unlink" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F43757272656E742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000 audit: type=1400 audit(1583509664.433:3454): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name=2F686F6D652F7364657A69656C2F736E61702F6368726F6D69756D2F313034302F2E636F6E6669672F6368726F6D69756D2F44656661756C742F43757272656E742053657373696F6E pid=6794 comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 [6794:6794:0306/104744.442966:ERROR:browser_main_loop.cc(277)] Gtk: gtk_icon_info_load_symbolic_for_context: assertion 'icon_info != NULL' failed gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed [6794:6794:0306/104744.443908:ERROR:browser_main_loop.cc(277)] Gtk: gtk_icon_info_load_symbolic_for_context: assertion 'icon_info != NULL' failed gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed [6794:6794:0306/104744.52:ERROR:browser_main_loop.cc(277)] Gtk: gtk_icon_info_load_symbolic_for_context: assertion 'icon_info != NULL' failed gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed Opening in existing browser session. AVC apparmor="DENIED" operation="truncate" profile="snap.chromium.chromium" name="/home/sdeziel/snap/chromium/1040/.config/chromium/Default/History-journal" pid=6794 comm="Chrome_HistoryT" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [6794:6937:0306/104744.470760:ERROR:database.cc(1584)] History sqlite error 1546, errno 0: disk I/O error, sql: SELECT segment_id, time_slot, visit_count FROM segment_usage WHERE time_slot >= ? ORDER BY segment_id audit: type=1400 audit(1583509664.465:3455):
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2255 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Tags added: fixed-upstream -- 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/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866222] Re: GNOME Shell crashed with signal 11
Unfortunately the bug is still incomplete because all we have is: [79676.217368] jik-x1 gnome-shell[3082]: GNOME Shell crashed with signal 11 meaning nobody can possibly work on this yet. Next time it happens, please reboot and then immediately run: journalctl -b-1 > prevboot.txt and attach the file 'prevboot.txt' here. ** Changed in: gnome-shell (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/1866222 Title: GNOME Shell crashed with signal 11 Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has crashed twice on me today. Unfortunately there's nothing in /var/crash. There's nothing in the journalctl log prior to the crash that explains it. I've attached a log of everything between when the crash happened and when I logged back in (though I suspect most of it is not relevant). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 13:04:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (201 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866367] Re: NetworkManager can't disable IPv6 properly
Thank you for your bugn that's probalby worth reporting upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- 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/1866367 Title: NetworkManager can't disable IPv6 properly Status in network-manager package in Ubuntu: New Bug description: Clicking 'disable' on the IPv6 tag doesn't appear to remove auto- configured IPv6 addresses or turn off the IPv6 operations on the specified interface. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.8-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 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 15:24:21 2020 InstallationDate: Installed on 2020-03-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) IpRoute: default via 192.168.1.254 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.1.0/24 dev ens33 proto kernel scope link src 192.168.1.86 metric 100 IwConfig: lono wireless extensions. ens33 no wireless extensions. RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 9f785e0c-8a0d-310a-8a14-c603fd38083c ethernet 1583508227 Fri 06 Mar 2020 15:23:47 GMT yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes ens33 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH ens33 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 9f785e0c-8a0d-310a-8a14-c603fd38083c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.8 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866367] [NEW] NetworkManager can't disable IPv6 properly
Public bug reported: Clicking 'disable' on the IPv6 tag doesn't appear to remove auto- configured IPv6 addresses or turn off the IPv6 operations on the specified interface. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.8-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 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 15:24:21 2020 InstallationDate: Installed on 2020-03-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) IpRoute: default via 192.168.1.254 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.1.0/24 dev ens33 proto kernel scope link src 192.168.1.86 metric 100 IwConfig: lono wireless extensions. ens33 no wireless extensions. RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 9f785e0c-8a0d-310a-8a14-c603fd38083c ethernet 1583508227 Fri 06 Mar 2020 15:23:47 GMT yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes ens33 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH ens33 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 9f785e0c-8a0d-310a-8a14-c603fd38083c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.8 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1866367 Title: NetworkManager can't disable IPv6 properly Status in network-manager package in Ubuntu: New Bug description: Clicking 'disable' on the IPv6 tag doesn't appear to remove auto- configured IPv6 addresses or turn off the IPv6 operations on the specified interface. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.8-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 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 15:24:21 2020 InstallationDate: Installed on 2020-03-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) IpRoute: default via 192.168.1.254 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.1.0/24 dev ens33 proto kernel scope link src 192.168.1.86 metric 100 IwConfig: lono wireless extensions. ens33 no wireless extensions. RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 9f785e0c-8a0d-310a-8a14-c603fd38083c ethernet 1583508227 Fri 06 Mar 2020 15:23:47 GMT yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes ens33 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Hi Daniel, do you think that removing Yaru's style would have a positive impact on this issue or it would be useless? The slice of css you reported comes from a file containing specific style for applications that can be dropped easily if not necessary (and even more easily if harmful) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: New Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1134069] Re: [HP Envy 4 Sleekbook] external audio jacks are reversed
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Won't Fix
--
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/1134069
Title:
[HP Envy 4 Sleekbook] external audio jacks are reversed
Status in alsa-driver package in Ubuntu:
Won't Fix
Bug description:
Looking at the outside of the system, the external audio jacks are in
this order:
Mic ___Headphone ___
However, on testing, it appears that they are either mislabled, or the
outputs are reversed internally. I had to plug the headphones into
the Mic jack to hear sound, and plug the mic into the headphone jack
to record sound.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1545 F pulseaudio
/dev/snd/pcmC0D0c: ubuntu 1545 F...m pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x5071 irq 48'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:111d76e0,103c1894,00100102
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 11
Date: Wed Feb 27 03:05:29 2013
HibernationDevice: RESUME=UUID=286b25cc-7928-4406-854e-6c1cae69a6e6
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic
root=UUID=0c6af5a9-e287-43f5-8ce6-647a4ae228f2 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-25-generic N/A
linux-backports-modules-3.5.0-25-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2012
dmi.bios.vendor: Insyde
dmi.bios.version: B.38
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1894
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 72.66
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrB.38:bd10/31/2012:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr088810250E102:rvnHewlett-Packard:rn1894:rvr72.66:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dm4 Notebook PC
dmi.product.version: 088810250E102
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1134069/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym
This is still an issue which requires a fix asap. It is affecting bionic release 18.04.4 LTS please see my bug report here: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1866356 Could we get an update on this, thanks. -- 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/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in Libva: Fix Released Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in intel-vaapi-driver source package in Bionic: Confirmed Status in libva source package in Bionic: Confirmed Status in mesa source package in Bionic: Invalid Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
My issue has been marked as duplicate of https://gitlab.gnome.org/GNOME /gnome-shell/issues/2255 which is already fixed 1 week ago. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2255 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2255 -- 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/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in gnome-shell package in Ubuntu: New Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865306] Re: package chromium-browser 80.0.3987.87-0ubuntu1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit statu
Relevant error from DpkgTerminalLog.txt:
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
erreur : cannot perform the following tasks:
- Télécharger un paquet Snap "chromium" (1040) à partir du canal "stable" (Get
https://api.snapcraft.io/api/v1/snaps/download/XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R_1040.snap:
dial tcp 91.189.92.41:443: i/o timeout)
There was a problem when downloading the chromium snap (which is what
the chromium-browser transitional package installs). Can you retry and
let us know whether it works now?
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Incomplete
--
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/1865306
Title:
package chromium-browser 80.0.3987.87-0ubuntu1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 1
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
Error when trying to install chromium-browser.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 80.0.3987.87-0ubuntu1
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
Date: Sat Feb 29 19:38:14 2020
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 1
InstallationDate: Installed on 2020-02-29 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191121)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
3.8.0-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu2
apt 1.9.10
Snap.Changes:
ID Status Spawn Ready Summary
4Error 2020-02-29T19:32:26+01:00 2020-02-29T19:38:14+01:00 Installer
le paquet Snap "chromium"
7Done2020-02-29T20:53:40+01:00 2020-02-29T20:57:32+01:00 Installer
le paquet Snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.122
(cf72c4c4f7db75bc3da689cd76513962d31c7b52-refs/branch-heads/3987@{#943})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 80.0.3987.122 snap
SourcePackage: chromium-browser
Title: package chromium-browser 80.0.3987.87-0ubuntu1 failed to
install/upgrade: new chromium-browser package pre-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/chromium-browser/+bug/1865306/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
I'm not familiar with gnome-terminal and not much with CSS, but I have
decided to dig into this bug and see what's happening.
My first finding is that yes we should just drop the 'scrollbar-
background-theming.patch' from gnome-terminal and fix the theme. So I
made that change to gnome-terminal...
My second finding is that the Yaru theme is already correct and doesn't
seem to need fixing:
terminal-window {
notebook {
scrollbar {
background-color: transparent;
It seems Yaru's request for 'transparent' comes out as white. Any other
colour seems to work -- it's only 'transparent' that doesn't. So this
appears to be a bug in either GTK or gnome-terminal failing to honour
'transparent'. And yes we should still remove the patch scrollbar-
background-theming.patch as well.
I'll be away for the next week or so, so maybe someone else can finish
this or I will look into it further when I return.
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1691678
Title:
Scrollbars escape the bottom and right side of the Terminal window by
1px
Status in GNOME Terminal:
Fix Released
Status in gnome-terminal package in Ubuntu:
Triaged
Status in gtk+3.0 package in Ubuntu:
New
Status in yaru-theme package in Ubuntu:
Fix Released
Bug description:
Ubuntu's orange overlay scrollbars escape the bottom of the window
during resizing.
To reproduce try gnome-shell on artful using the Ambiance theme. Open
a Terminal window and resize it vertically, quickly. Notice the bottom
of the overlay scrollbar overruns the bottom of the window.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.5-0ubuntu3
Architecture: amd64
Date: Thu May 18 15:28:33 2017
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'app-picker-view' b'uint32 1'
b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop',
'org.gnome.Terminal.desktop', 'rhythmbox.desktop',
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
InstallationDate: Installed on 2017-05-03 (15 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing
What's your locale? Can you run chromium in a terminal with the following command, reproduce the problem, save the output to a file and share it here? chromium --enable-logging=stderr Thanks! ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1864365 Title: [snap] Dialog font missing Status in chromium-browser package in Ubuntu: Incomplete Bug description: $ lsb_release -rb Description: Ubuntu 19.10 Release: 19.10 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 01:56 CET channels: stable:80.0.3987.116 2020-02-19 (1036) 160MB - candidate: 80.0.3987.116 2020-02-19 (1036) 160MB - beta: 81.0.4044.17 2020-02-17 (1028) 161MB - edge: 81.0.4044.17 2020-02-14 (1028) 161MB - installed: 80.0.3987.116(1036) 160MB - Basic Ubuntu 19.10 installation using "factory default" font settings. Expected : When opening any file dialog (to open or upload a file, for example) from Chromium snap application, the file dialog renders normally. What happened instead: When opening any file dialog (to open or upload a file, for example) from Chromium snap application, all characters in the dialog box are empty squares (see attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866355] [NEW] RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
Public bug reported: python3-uno (1:6.4.0-0ubuntu7) wird eingerichtet ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-uno 1:6.4.0-0ubuntu7 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 CurrentDesktop: XFCE Date: Fri Mar 6 15:17:42 2020 InstallationDate: Installed on 2020-01-16 (49 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-01-21 (44 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1866355 Title: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used Status in libreoffice package in Ubuntu: New Bug description: python3-uno (1:6.4.0-0ubuntu7) wird eingerichtet ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-uno 1:6.4.0-0ubuntu7 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 CurrentDesktop: XFCE Date: Fri Mar 6 15:17:42 2020 InstallationDate: Installed on 2020-01-16 (49 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-01-21 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1866355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865128] Re: English US spelling dictionary appears in the languages' menu even though it's not installed
Paul, firefox uses the spelling dictionaries installed system-wide in /usr/share/hunspell, independently of the language pack extensions. As far as en-US is concerned, this is the default locale that firefox is built in, so the corresponding dictionary is embedded in firefox. There is no way to make a locale-agnostic build. If you really wanted to get rid of the embedded dictionary, you would need to unpack /usr/lib/firefox/omni.ja (zip format), delete the contents of the 'dictionaries' directory, and repack it. ** Changed in: firefox (Ubuntu) Status: Confirmed => Invalid -- 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/1865128 Title: English US spelling dictionary appears in the languages' menu even though it's not installed Status in firefox package in Ubuntu: Invalid Bug description: Even though I don't have the English US spelling dictionary (hunspell- en-us) installed neither system-wide nor locally in Firefox, it appears in the languages' context menu (when you right-click in a text field). Is it hard-packaged with Firefox? Please remove it if it's packaged with Firefox by mistake. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 73.0.1+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr2204 F pulseaudio /dev/snd/pcmC0D0p: amr2204 F...m pulseaudio BuildID: 20200217142647 Channel: Unavailable CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 10:27:51 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-11-29 (455 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.254 dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.114 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:740 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=73.0/20200207195153 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET59W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS01800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET59W(1.36):bd10/16/2019:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LTS01800 dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866222] Re: GNOME Shell crashed with signal 11
I already have the workaround in bug 994921 and have for a long time. My system has generated and reported crashes as recently as February 28. There's no crash for this in /var/crash. There's no crash for this on errors.ubuntu.com. For some reason, when this crash occurs it's not generating a crash that can be reported to Ubuntu. It's still a bug that needs to be fixed, though, obviously, so I am changing the status of this bug from Incomplete back to New. ** 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/1866222 Title: GNOME Shell crashed with signal 11 Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell has crashed twice on me today. Unfortunately there's nothing in /var/crash. There's nothing in the journalctl log prior to the crash that explains it. I've attached a log of everything between when the crash happened and when I logged back in (though I suspect most of it is not relevant). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 13:04:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (201 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1493964] Re: Gnome terminal scrollbars background is not themable
** Bug watch added: bugzilla.gnome.org/ #754796 https://bugzilla.gnome.org/show_bug.cgi?id=754796 ** Changed in: gnome-terminal Importance: Medium => Unknown ** Changed in: gnome-terminal Status: In Progress => Unknown ** Changed in: gnome-terminal Remote watch: GNOME Bug Tracker #754796 => bugzilla.gnome.org/ #754796 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1493964 Title: Gnome terminal scrollbars background is not themable Status in GNOME Terminal: Unknown Status in gnome-terminal package in Ubuntu: Fix Released Bug description: This is related to bug #1451924, however upstream proposed fix is not yet ready to use. Basically gnome-terminal provides a scroll bar which is boxed horizontally with the terminal itself, and currently the scrollbar background is not inherited from terminal itself, leading to a white background. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1493964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866348] Re: gnome-shell[81291] trap int3 ip:7fc2d73a5065 sp:7fc284e6d710 error:0 in libglib-2.0.so.0.6305.0[7fc2d7369000+84000]
Something very similar is reported at https://bugzilla.redhat.com/show_bug.cgi?id=1797736. Downgrading fixed the problem there, but I can't see how to downgrade glib-2.0 on focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1866348 Title: gnome-shell[81291] trap int3 ip:7fc2d73a5065 sp:7fc284e6d710 error:0 in libglib-2.0.so.0.6305.0[7fc2d7369000+84000] Status in glib2.0 package in Ubuntu: New Bug description: I'm running on Focal. Since recently, Gnome crashes with ``` Mar 6 14:03:16 ishanca gnome-shell[77303]: Failed to set scheduler settings: Operation not permitted Mar 6 14:03:16 ishanca kernel: [33974.584854] traps: gnome-shell[81291] trap int3 ip:7fc2d73a5065 sp:7fc284e6d710 error:0 in libglib-2.0.so.0.6305.0[7fc2d7369000+84000] [...] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1866348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866348] [NEW] gnome-shell[81291] trap int3 ip:7fc2d73a5065 sp:7fc284e6d710 error:0 in libglib-2.0.so.0.6305.0[7fc2d7369000+84000]
Public bug reported: I'm running on Focal. Since recently, Gnome crashes with ``` Mar 6 14:03:16 ishanca gnome-shell[77303]: Failed to set scheduler settings: Operation not permitted Mar 6 14:03:16 ishanca kernel: [33974.584854] traps: gnome-shell[81291] trap int3 ip:7fc2d73a5065 sp:7fc284e6d710 error:0 in libglib-2.0.so.0.6305.0[7fc2d7369000+84000] [...] ``` ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Red Hat Bugzilla #1797736 https://bugzilla.redhat.com/show_bug.cgi?id=1797736 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1866348 Title: gnome-shell[81291] trap int3 ip:7fc2d73a5065 sp:7fc284e6d710 error:0 in libglib-2.0.so.0.6305.0[7fc2d7369000+84000] Status in glib2.0 package in Ubuntu: New Bug description: I'm running on Focal. Since recently, Gnome crashes with ``` Mar 6 14:03:16 ishanca gnome-shell[77303]: Failed to set scheduler settings: Operation not permitted Mar 6 14:03:16 ishanca kernel: [33974.584854] traps: gnome-shell[81291] trap int3 ip:7fc2d73a5065 sp:7fc284e6d710 error:0 in libglib-2.0.so.0.6305.0[7fc2d7369000+84000] [...] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1866348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865363] Re: nm-applet unstable behaviour when multiple AP have the same name
OK I've finally directly found the project page, so I reported it there https://gitlab.gnome.org/GNOME/network-manager-applet/issues/90 ** Bug watch added: gitlab.gnome.org/GNOME/network-manager-applet/issues #90 https://gitlab.gnome.org/GNOME/network-manager-applet/issues/90 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1865363 Title: nm-applet unstable behaviour when multiple AP have the same name Status in network-manager-applet package in Ubuntu: New Bug description: Hi, I'm using a public wifi network to access the internet (in the spirit of FON - https://fon.com/). Let's name it XXX. There are multiple access points with the same name that "offer" this network. Many are in conflict with one another, using the same channel. Also, each AP is regularly switching channel, so I cannot associate a channel to a bssid and work with bssids instead of network name. nm-applet manages this situation very badly: - nm-applet seems to select the AP with the strongest signal, even if it is in conflict with 10s of others APs, leading to a very bad connexion, while still displaying an icon showing very good signal; - Also, as a consequence of its selection, quite often, nm-applet switches from one AP to the other, creating very instable situations, leading to even worse connexions throughput; - Trying to solve the problem, I saved the network, modified the connexion manually to fix one channel (let's name it YYY1), saved the connexion as "XXX-c[han]YYY1", then disconnected. Then I reconnected to the network, but nm-applet seemed to have switched to another AP using another chanel (YYY2), so I repeated the operation, and saved a "XXX-c[han]YYY2" network. Now, nm-applet, in its list of available networks, now randomly displays either simply "XXX", or at times "XXX >" (with a triangular char showing that there are sunetworks available) with "XXX-channelYYY1" are "XXX-channelYYY2" as sub networks. In the second case, if I select the network with less/no channel conflict, then the connexion is quite good and stable. > As can be seen in the attached picture, in the terminal, there are many access points available for XXX network, several using channel 11 or 7. As can also be seen there are 2 saved networks in nm-applet "Edit networks", one fixed to chan7, one fixed to chan11. However, nm- applet just lists "XXX" in its list of available networks... - Finally, there is no simple way in "Edit connections" to copy an existing configuration, so I cannot easily create a connection for each possible chanel. So, even if point above would be solved and nm- applet always display the avaliable "XXX-c[han]YYY" sub networks, I cannot simply create an entry for each channel and manually select the channel that is less in conflict than the others, based on my script that lists all the APs and the channels they use. Does anyone has a solution to this kind of situation? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1865363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866219] Re: Login screen hangs
@vanvugt I have ran the suggested command on my Ubuntu machine. Please let me know how may I help you in collecting more details regarding the stated issue. Thanks ** Tags added: apport-collected ** Description changed: One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. * lsb_release -rd: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 * Software Center version: 3.35.91 * What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully. * What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:02:36 2020 DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:39f2] InstallationDate: Installed on 2019-12-14 (82 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80S7 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-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN31WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 510-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0VCN31WW(V1.15):bd06/19/2018:svnLENOVO:pn80S7:pvrLenovoYOGA510-14ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct31:cvrLenovoYOGA510-14ISK: dmi.product.family: YOGA 510-14ISK dmi.product.name: 80S7 dmi.product.sku: LENOVO_MT_80S7_BU_idea_FM_YOGA 510-14ISK dmi.product.version: Lenovo YOGA 510-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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-0ubuntu18 + Architecture: amd64 +
[Desktop-packages] [Bug 1866219] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1866219/+attachment/5334298/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866219 Title: Login screen hangs Status in gnome-shell package in Ubuntu: New Bug description: One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. * lsb_release -rd: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 * Software Center version: 3.35.91 * What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully. * What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:02:36 2020 DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:39f2] InstallationDate: Installed on 2019-12-14 (82 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80S7 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-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN31WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 510-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0VCN31WW(V1.15):bd06/19/2018:svnLENOVO:pn80S7:pvrLenovoYOGA510-14ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct31:cvrLenovoYOGA510-14ISK: dmi.product.family: YOGA 510-14ISK dmi.product.name: 80S7 dmi.product.sku: LENOVO_MT_80S7_BU_idea_FM_YOGA 510-14ISK dmi.product.version: Lenovo YOGA 510-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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
[Desktop-packages] [Bug 1866219] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1866219/+attachment/5334302/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866219 Title: Login screen hangs Status in gnome-shell package in Ubuntu: New Bug description: One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. * lsb_release -rd: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 * Software Center version: 3.35.91 * What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully. * What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:02:36 2020 DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:39f2] InstallationDate: Installed on 2019-12-14 (82 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80S7 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-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN31WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 510-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0VCN31WW(V1.15):bd06/19/2018:svnLENOVO:pn80S7:pvrLenovoYOGA510-14ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct31:cvrLenovoYOGA510-14ISK: dmi.product.family: YOGA 510-14ISK dmi.product.name: 80S7 dmi.product.sku: LENOVO_MT_80S7_BU_idea_FM_YOGA 510-14ISK dmi.product.version: Lenovo YOGA 510-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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
[Desktop-packages] [Bug 1866219] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1866219/+attachment/5334301/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866219 Title: Login screen hangs Status in gnome-shell package in Ubuntu: New Bug description: One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. * lsb_release -rd: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 * Software Center version: 3.35.91 * What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully. * What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:02:36 2020 DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:39f2] InstallationDate: Installed on 2019-12-14 (82 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80S7 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-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN31WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 510-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0VCN31WW(V1.15):bd06/19/2018:svnLENOVO:pn80S7:pvrLenovoYOGA510-14ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct31:cvrLenovoYOGA510-14ISK: dmi.product.family: YOGA 510-14ISK dmi.product.name: 80S7 dmi.product.sku: LENOVO_MT_80S7_BU_idea_FM_YOGA 510-14ISK dmi.product.version: Lenovo YOGA 510-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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
[Desktop-packages] [Bug 1866219] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1866219/+attachment/5334300/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866219 Title: Login screen hangs Status in gnome-shell package in Ubuntu: New Bug description: One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. * lsb_release -rd: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 * Software Center version: 3.35.91 * What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully. * What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:02:36 2020 DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:39f2] InstallationDate: Installed on 2019-12-14 (82 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80S7 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-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN31WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 510-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0VCN31WW(V1.15):bd06/19/2018:svnLENOVO:pn80S7:pvrLenovoYOGA510-14ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct31:cvrLenovoYOGA510-14ISK: dmi.product.family: YOGA 510-14ISK dmi.product.name: 80S7 dmi.product.sku: LENOVO_MT_80S7_BU_idea_FM_YOGA 510-14ISK dmi.product.version: Lenovo YOGA 510-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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
[Desktop-packages] [Bug 1866219] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1866219/+attachment/5334299/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866219 Title: Login screen hangs Status in gnome-shell package in Ubuntu: New Bug description: One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. * lsb_release -rd: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 * Software Center version: 3.35.91 * What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully. * What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:02:36 2020 DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:39f2] InstallationDate: Installed on 2019-12-14 (82 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80S7 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-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN31WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 510-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0VCN31WW(V1.15):bd06/19/2018:svnLENOVO:pn80S7:pvrLenovoYOGA510-14ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct31:cvrLenovoYOGA510-14ISK: dmi.product.family: YOGA 510-14ISK dmi.product.name: 80S7 dmi.product.sku: LENOVO_MT_80S7_BU_idea_FM_YOGA 510-14ISK dmi.product.version: Lenovo YOGA 510-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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
[Desktop-packages] [Bug 1865385] Re: eog is not the default option to open images (jpg, png, svg)
The default issue is fixed with https://launchpad.net/ubuntu/+source /desktop-file-utils/0.24-1ubuntu2 ** Changed in: eog (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1865385 Title: eog is not the default option to open images (jpg, png, svg) Status in eog package in Ubuntu: Fix Released Bug description: After updating to focal dev, when opening a jpg or png file, it is opened by Gimp instead of eog as it was in eoan. Also, eog doesn't even appear as an option in the "open with..." menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.35.91-0ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 18:42:07 2020 InstallationDate: Installed on 2018-02-23 (736 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: eog UpgradeStatus: Upgraded to focal on 2020-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1865385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866000] Re: incorrect default apps for calendar and photos
https://launchpad.net/ubuntu/+source/desktop-file-utils/0.24-1ubuntu2 ** Package changed: ubuntu-settings (Ubuntu) => desktop-file-utils (Ubuntu) ** Changed in: desktop-file-utils (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1866000 Title: incorrect default apps for calendar and photos Status in desktop-file-utils package in Ubuntu: Fix Released Bug description: Open settings > Default Applications and you'll see 'Text Editor' set for Calendar and 'Firefox' set for Photos, though Image Viewer and Shotwell are listed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 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 CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 08:20:54 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1866000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697373] Re: [screensaver] Screen blanks during video playback in Chrome and Firefox under Xwayland
Having this issue on Xubuntu 19.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1697373 Title: [screensaver] Screen blanks during video playback in Chrome and Firefox under Xwayland Status in X.Org X server: New Status in xorg-server package in Ubuntu: Triaged Bug description: gnome-shell / gdm / wayland Test Case: 1. Launch netflix in chrome 2. Play a video 3. Wait until the display times out. Expected result The screen does not dim Actual result The display goes black. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 12 09:21:46 2017 DisplayManager: gdm3 InstallationDate: Installed on 2013-09-03 (1377 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1697373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804568] Re: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode
** Summary changed: - click position is flipped to cursor position when in tent mode + [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode -- 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/1804568 Title: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1950 F pulseaudio /dev/snd/controlC1: imi1950 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.60 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1333 F pulseaudio /dev/snd/controlC1: imi1333 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-10-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/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX
[Desktop-packages] [Bug 1866326] Re: Login freezes when using Nvidia drivers 435 and 440
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-435 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866326 Title: Login freezes when using Nvidia drivers 435 and 440 Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: I have a Lenovo P53 which has hybrid graphics (Intel and Nvidia). I have chosen to use "discrete graphics" which means that I am using the Nvidia card. Until a recent update everything was working fine. After the automatic update and the upgrade from kernel 5.3.0-28 to 5.3.0-40 (and possibly an upgrade of the Nvidia drivers) the opearing system hands after I enter the login credentials. I have tried to get some output from the startup screen by removing the "quite splash" from the grub file but it does not give any error information. It just hangs. I am using Nouveau to login to the computer, but with Nouveau I the HDMI port is not working I can try to add more debugging information if one helps me to collect it I am using Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 11:39:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: I don't know GpuHangStarted: I don't know GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2297] NVIDIA Corporation Device [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2297] InstallationDate: Installed on 2020-02-29 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20QQS1JE00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET34W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS1JE00 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:bvrN2NET34W(1.19):bd11/28/2019:svnLENOVO:pn20QQS1JE00:pvrThinkPadP53:rvnLENOVO:rn20QQS1JE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS1JE00 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1866326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866326] Re: Login freezes when using Nvidia drivers 435 and 440
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866326 Title: Login freezes when using Nvidia drivers 435 and 440 Status in xorg package in Ubuntu: New Bug description: I have a Lenovo P53 which has hybrid graphics (Intel and Nvidia). I have chosen to use "discrete graphics" which means that I am using the Nvidia card. Until a recent update everything was working fine. After the automatic update and the upgrade from kernel 5.3.0-28 to 5.3.0-40 (and possibly an upgrade of the Nvidia drivers) the opearing system hands after I enter the login credentials. I have tried to get some output from the startup screen by removing the "quite splash" from the grub file but it does not give any error information. It just hangs. I am using Nouveau to login to the computer, but with Nouveau I the HDMI port is not working I can try to add more debugging information if one helps me to collect it I am using Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 11:39:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: I don't know GpuHangStarted: I don't know GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2297] NVIDIA Corporation Device [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2297] InstallationDate: Installed on 2020-02-29 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20QQS1JE00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET34W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS1JE00 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:bvrN2NET34W(1.19):bd11/28/2019:svnLENOVO:pn20QQS1JE00:pvrThinkPadP53:rvnLENOVO:rn20QQS1JE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS1JE00 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866326] [NEW] Login freezes when using Nvidia drivers 435 and 440
You have been subscribed to a public bug: I have a Lenovo P53 which has hybrid graphics (Intel and Nvidia). I have chosen to use "discrete graphics" which means that I am using the Nvidia card. Until a recent update everything was working fine. After the automatic update and the upgrade from kernel 5.3.0-28 to 5.3.0-40 (and possibly an upgrade of the Nvidia drivers) the opearing system hands after I enter the login credentials. I have tried to get some output from the startup screen by removing the "quite splash" from the grub file but it does not give any error information. It just hangs. I am using Nouveau to login to the computer, but with Nouveau I the HDMI port is not working I can try to add more debugging information if one helps me to collect it I am using Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 11:39:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: I don't know GpuHangStarted: I don't know GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2297] NVIDIA Corporation Device [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2297] InstallationDate: Installed on 2020-02-29 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20QQS1JE00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET34W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS1JE00 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:bvrN2NET34W(1.19):bd11/28/2019:svnLENOVO:pn20QQS1JE00:pvrThinkPadP53:rvnLENOVO:rn20QQS1JE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS1JE00 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- Login freezes when using Nvidia drivers 435 and 440 https://bugs.launchpad.net/bugs/1866326 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Also encountered this: $ uname -a Linux kaltop 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan mar 06 12:44:09 kaltop /usr/lib/gdm3/gdm-x-session[2575]: i965: Failed to submit batchbuffer: Bad address mar 06 12:44:09 kaltop gnome-shell[2782]: X IO Error mar 06 12:44:09 kaltop pulseaudio[2557]: X connection to :0 broken (explicit kill or server shutdown). mar 06 12:44:09 kaltop WebKitWebProces[18049]: WebKitWebProcess: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. mar 06 12:44:09 kaltop gnome-shell[2782]: Gdk-Message: 12:44:09.213: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in Mesa: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Unknown Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1794033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode
I've just upgraded my 20.04 to check if the bug is still present, and it is. Can I expect it to be fixed in the 20.04 release version? Thank you in advance. (The gnome guys say it's already fixed, however I'm not sure if they are right) -- 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/1804568 Title: click position is flipped to cursor position when in tent mode Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1950 F pulseaudio /dev/snd/controlC1: imi1950 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.60 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1333 F pulseaudio /dev/snd/controlC1: imi1333 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-10-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/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360
[Desktop-packages] [Bug 1866329] [NEW] nm-connection-editor lacks option for metered connections
Public bug reported: Hi, unfortunately, snapd insists to refresh snaps, thus possibly causing several GB of traffic per day, blocking the network and ruining the owner if the connection is slow and/or metered. There is no option to turn this permanently off, only methods to schedule, delay, or to hold refreshing if a metered connection is detected. It is, therefore, important to be able to tell Network Manager, that a connection is metered in order to keep snapd from ruining the user. While I've seen screenshots showing this option in the mainstream ubuntu's desktop settings, I do not see such an option in nm-connection- editor, which is used e.g. by Lubuntu. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 6 12:12:05 2020 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown InstallationDate: Installed on 2018-04-30 (676 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.103.254 dev enp2s0 proto dhcp metric 100 192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.101.143 metric 100 192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1 metric 425 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1866329 Title: nm-connection-editor lacks option for metered connections Status in network-manager-applet package in Ubuntu: New Bug description: Hi, unfortunately, snapd insists to refresh snaps, thus possibly causing several GB of traffic per day, blocking the network and ruining the owner if the connection is slow and/or metered. There is no option to turn this permanently off, only methods to schedule, delay, or to hold refreshing if a metered connection is detected. It is, therefore, important to be able to tell Network Manager, that a connection is metered in order to keep snapd from ruining the user. While I've seen screenshots showing this option in the mainstream ubuntu's desktop settings, I do not see such an option in nm- connection-editor, which is used e.g. by Lubuntu. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 6 12:12:05 2020 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown InstallationDate: Installed on 2018-04-30 (676 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.103.254 dev enp2s0 proto dhcp metric 100 192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.101.143 metric 100 192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1 metric 425 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1866329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
Got pulseaudio to stop auto-reloading with "autospawn = no" in
/etc/pulseaudio/client.conf.
Attached is the output from "pulseaudio -vv". the PLAYBACK stream is
recognized, but not the CAPTURE stream.
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Zoom.us meeting links (zoomus://) are not launching the app anymore. This reduces drastically the productivity, since I have to manually copy the meeting ID into the Zoom app. Multiply that with about 10 meetings a day and it results in moving to Firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
** Attachment added: "pulseaudio-vv"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+attachment/5334265/+files/pulseaudio-vv
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
Updating __just__ `mutter` to 3.34.3-1ubuntu1~19.10.1 did not work; I had to update `libmutter-5-0` too. If you're using the instructions given in the link in comment https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1845281/comments/10 to disable automatic updates to proposed packages, then this will attempt to remove a couple of essential core libraries such as `gdm3`, so you will have to NOT pin them and then go: `sudo apt-get install libmutter-5-0/eoan-proposed mutter/eoan-proposed` -- 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/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Committed Bug description: [ Description ] Intellij and other java apps can cause GNOME shell to crash [ Test case ] 1) Run this test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/956 2) Windows should appear and close correctly while Gnome shell must not crash [ Regression potential ] Parent-child relationship on some windows might be broken. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 581778] Re: No internal mic / line-in on Intel HDA G45 DEVIBX / Realtek ALC 275
I'm really sorry this bug went untouched for so long. I take it this is
no longer an issue then. Closing. Again, apologies :/
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
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/581778
Title:
No internal mic / line-in on Intel HDA G45 DEVIBX / Realtek ALC 275
Status in alsa-driver package in Ubuntu:
Invalid
Bug description:
OS Specifications: Ubuntu 10.04 LTS Lucid Kernell 2.6.32-22-generic
Hardware: Sony VPCS11X9E laptop
Alsa-driver:
$cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on May 16 2010 for kernel 2.6.32-22-generic (SMP).
Alsa-driver-module: (from ppa:ubuntu-audio-dev)
Package: linux-alsa-driver-modules-2.6.32-22-generic
Architecture: amd64
Version: 2.6.32-22.201005160600
Filename:
pool/main/l/linux-alsa-driver-modules-2.6.32/linux-alsa-driver-modules-2.6.32-22-generic_2.6.32-22.201005160600_amd64.deb
Result of http://www.alsa-project.org/alsa-info.sh can be found here:
http://www.alsa-project.org/db/?f=55c16c183a185f2a45a1b8dd15c15317bf77759d
This bug has been around for a long time now, hope there will be a fix
soon as many modern laptops use the same sound card/chipset.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on May 16 2010 for kernel 2.6.32-22-generic (SMP).
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC275 Analog [ALC275 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb40 irq 37'
Mixer name : 'Intel G45 DEVIBX'
Components : 'HDA:10ec0275,104d4100,0015
HDA:80862804,104d4100,0010'
Controls : 19
Simple ctrls : 9
Date: Mon May 17 16:40:08 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: alsa-driver
dmi.bios.date: 01/07/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: R0280Q3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnINSYDE:bvrR0280Q3:bd01/07/2010:svnSonyCorporation:pnVPCS11X9E:pvrC103ZXDX:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCS11X9E
dmi.product.version: C103ZXDX
dmi.sys.vendor: Sony Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/581778/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 581778] Re: No internal mic / line-in on Intel HDA G45 DEVIBX / Realtek ALC 275
Thanks for closing this bug after a decade Marcus ;)
On Fri, Mar 6, 2020 at 1:13 AM Marcus Tomlinson <
marcus.tomlin...@canonical.com> wrote:
> This release of Ubuntu is no longer receiving maintenance updates. If
> this is still an issue on a maintained version of Ubuntu please let us
> know.
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/581778
>
> Title:
> No internal mic / line-in on Intel HDA G45 DEVIBX / Realtek ALC 275
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/581778/+subscriptions
>
--
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/581778
Title:
No internal mic / line-in on Intel HDA G45 DEVIBX / Realtek ALC 275
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
OS Specifications: Ubuntu 10.04 LTS Lucid Kernell 2.6.32-22-generic
Hardware: Sony VPCS11X9E laptop
Alsa-driver:
$cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on May 16 2010 for kernel 2.6.32-22-generic (SMP).
Alsa-driver-module: (from ppa:ubuntu-audio-dev)
Package: linux-alsa-driver-modules-2.6.32-22-generic
Architecture: amd64
Version: 2.6.32-22.201005160600
Filename:
pool/main/l/linux-alsa-driver-modules-2.6.32/linux-alsa-driver-modules-2.6.32-22-generic_2.6.32-22.201005160600_amd64.deb
Result of http://www.alsa-project.org/alsa-info.sh can be found here:
http://www.alsa-project.org/db/?f=55c16c183a185f2a45a1b8dd15c15317bf77759d
This bug has been around for a long time now, hope there will be a fix
soon as many modern laptops use the same sound card/chipset.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on May 16 2010 for kernel 2.6.32-22-generic (SMP).
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC275 Analog [ALC275 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb40 irq 37'
Mixer name : 'Intel G45 DEVIBX'
Components : 'HDA:10ec0275,104d4100,0015
HDA:80862804,104d4100,0010'
Controls : 19
Simple ctrls : 9
Date: Mon May 17 16:40:08 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: alsa-driver
dmi.bios.date: 01/07/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: R0280Q3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnINSYDE:bvrR0280Q3:bd01/07/2010:svnSonyCorporation:pnVPCS11X9E:pvrC103ZXDX:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCS11X9E
dmi.product.version: C103ZXDX
dmi.sys.vendor: Sony Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/581778/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
I installed a fresh Ubuntu 18.04.3 and updated nearly every package one
by one (to name a few, pulseaudio, libasound, systemd, kernel (4.15,
later HWE 5.3) - all to no avail, up to a full upgrade of all packages
so now the system is 18.04.4. The problem is not reproducable with a
fresh and clean installation.
But we have a new case, the colleague got the auto security updates on
2020-03-02 and did a manual package update on 2020-03-04. After the
updates on 2020-03-04 the system was rebooted by the user, and now has
the same bug.
This affects both wired (USB) and wireless (bluetooth) headsets. As soon
as the headset is connected and re-connected it's not recognized.
Running "pkill -U $USER pulseaudio" solves this problem in 8/10 cases.
The other 2/10 are full system reboots.
Attached is the dpkg.log with the updates from 2020-03-02 and
2020-03-04. I couldn't determine anything that would point near the/a
problematic package.
I still need to find a way to restart pulseaudio with a higher debug
level to check if anything pops up with pulse.
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
** Attachment added: "dpkg_200305.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+attachment/5334241/+files/dpkg_200305.log
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310692] Re: [Q501LA, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound
Forgot all about this bug. The issue seems to be resolved and has been for a while. Feel free to close it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1310692 Title: [Q501LA, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: Issue apeared sometime between beta 2 and the final release. Seems to affect programs that run directly through alsa more than those that use pulse. There are also times when recording will drop causing missed words or sounds. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-lowlatency 3.13.9 Uname: Linux 3.13.0-24-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: benjamin 2174 F pulseaudio /dev/snd/pcmC1D0c: benjamin 2174 F...m pulseaudio /dev/snd/pcmC1D0p: benjamin 2174 F...m pulseaudio /dev/snd/controlC0: benjamin 2174 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 21 11:03:33 2014 InstallationDate: Installed on 2014-03-18 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Q501LA, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to trusty on 2014-03-18 (33 days ago) dmi.bios.date: 05/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q501LA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q501LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ501LA.205:bd05/10/2013:svnASUSTeKCOMPUTERINC.:pnQ501LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ501LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: Q501LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-19T10:10:51.473145 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 998259] Re: [ID47H, Conexant CX20588, Black Headphone Out, Right] No sound at all through any output
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
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/998259
Title:
[ID47H, Conexant CX20588, Black Headphone Out, Right] No sound at all
through any output
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
happend in both 12.04 and 11.10
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: triggernesss 3100 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xd1c0 irq 50'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:14f1506c,10250571,0010
HDA:80862805,80860101,0010'
Controls : 29
Simple ctrls : 13
Date: Fri May 11 16:12:21 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse: 3100/dev/snd/controlC0: triggernesss F pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: No sound at all
Title: [ID47H, Conexant CX20588, Black Headphone Out, Right] No sound at all
UpgradeStatus: Upgraded to precise on 2012-05-10 (1 days ago)
dmi.bios.date: 05/06/2011
dmi.bios.vendor: Gateway
dmi.bios.version: V1.04
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJM40_HR
dmi.board.vendor: Gateway
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: V1.04
dmi.modalias:
dmi:bvnGateway:bvrV1.04:bd05/06/2011:svnGateway:pnID47H:pvrV1.04:rvnGateway:rnSJM40_HR:rvrBaseBoardVersion:cvnGateway:ct10:cvrV1.04:
dmi.product.name: ID47H
dmi.product.version: V1.04
dmi.sys.vendor: Gateway
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/998259/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 948443] Re: [Extensa 5220, Realtek ALC268, Speaker, Internal] No sound at all
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
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/948443
Title:
[Extensa 5220, Realtek ALC268, Speaker, Internal] No sound at all
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
rhythmbox dont play a listen.pls on gnome classic session
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thomas 1639 F pulseaudio
/dev/snd/pcmC0D0p: thomas 1639 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc30 irq 46'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1025011f,0013
HDA:14f12c06,10250093,0010'
Controls : 22
Simple ctrls : 13
CurrentDmesg:
[ 3504.834776] gnome-panel[3205]: segfault at 8 ip 0043561b sp
7fff7cc8d610 error 4 in gnome-panel[40+8b000]
[ 3942.391102] rhythmbox-metad[4347]: segfault at 9 ip 004081a5 sp
7fff754116b0 error 4 in rhythmbox-metadata[40+12000]
Date: Tue Mar 6 22:15:13 2012
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta amd64 (20120228)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=de:en
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Eingebautes Audio - HDA Intel
Symptom_DevicesInUse:
1639 1639 thomasF pulseaudio
/dev/snd/pcmC0D0p: thomasF...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Extensa 5220, Realtek ALC268, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/03/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.35
dmi.board.name: Columbia
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5220
dmi.product.version: 0100
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/948443/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1019859] Re: [Macmini1, 1, SigmaTel STAC9221 A1, White Headphone Out, Rear] Clipping on left headphone channel and internal speaker
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1019859 Title: [Macmini1,1, SigmaTel STAC9221 A1, White Headphone Out, Rear] Clipping on left headphone channel and internal speaker Status in alsa-driver package in Ubuntu: Incomplete Bug description: After every boot there is distinct clipping/distortion on the left headphone channel. If nothing is plugged into the headphone socket, there is clipping/distortion on the internal speaker. The problem goes away if the machine is rebooted, possibly several times in a row. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrzej1566 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x9044 irq 43' Mixer name : 'SigmaTel STAC9221 A1' Components : 'HDA:83847680,106b0800,00103401' Controls : 21 Simple ctrls : 10 CurrentDmesg: [ 19.664968] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 30.288021] eth0: no IPv6 routers present Date: Sun Jul 1 20:21:34 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: White Headphone Out, Rear Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [Macmini1,1, SigmaTel STAC9221 A1, White Headphone Out, Rear] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/06 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MM11.88Z.0055.B08.0610121326 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208EC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 4 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208EC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMM11.88Z.0055.B08.0610121326:bd10/12/06:svnAppleComputer,Inc.:pnMacmini1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208EC8:rvrPVT:cvnAppleComputer,Inc.:ct4:cvrMac-F4208EC8: dmi.product.name: Macmini1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1019859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1006089] Re: Acer Aspire 1810TZ inverted internal microphone
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- 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/1006089 Title: Acer Aspire 1810TZ inverted internal microphone Status in alsa-driver package in Ubuntu: Incomplete Bug description: The internal microphone of the Acer Aspire 1810TZ is affected by bug 1002978. It can be solved by unlocking the input channels with pavucontrol and setting one of them to zero. Alsa info has already been reported here: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946232/+attachment/3156604/+files/Acer-Aspire-1810TZ__alsa-info.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1006089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174551] Re: [F5R, Realtek ALC660-VD, Mic, Internal] No autoswitch
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1174551 Title: [F5R, Realtek ALC660-VD, Mic, Internal] No autoswitch Status in alsa-driver package in Ubuntu: Incomplete Bug description: no sound when I plug my mic in the laptop. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: boetero1892 F pulseaudio boetero 14960 F audacity Date: Mon Apr 29 23:39:47 2013 InstallationDate: Installed on 2013-04-27 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Intern geluid - HDA ATI SB Symptom_Jack: Mic, Internal Symptom_Type: No auto-switch between inputs Title: [F5R, Realtek ALC660-VD, Mic, Internal] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F5R 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.:bvr403:bd05/09/2007:svnASUSTeKComputerInc.:pnF5R:pvr1.0:rvnASUSTeKComputerInc.:rnF5R:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F5R 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/1174551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1068427] Re: [8215D7J, Analog Devices AD1981, Green Line Out, Rear] No sound at all
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
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/1068427
Title:
[8215D7J, Analog Devices AD1981, Green Line Out, Rear] No sound at all
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
NO audio at all with movie player, but with vlc player it is working
with audio
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
Uname: Linux 3.2.0-32-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu14
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lemya 1655 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd01c irq 43'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,101402f9,00100200'
Controls : 33
Simple ctrls : 19
Date: Fri Oct 19 06:57:08 2012
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386
(20120817.3)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
1655 lemya F pulseaudio
PID ACCESS COMMAND
Symptom_Jack: Green Line Out, Rear
Symptom_Type: No sound at all
Title: [8215D7J, Analog Devices AD1981, Green Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2006
dmi.bios.vendor: IBM
dmi.bios.version: 2EKT34AUS
dmi.board.name: IBM
dmi.board.vendor: IBM
dmi.chassis.asset.tag: �
dmi.chassis.type: 4
dmi.chassis.vendor: IBM
dmi.modalias:
dmi:bvnIBM:bvr2EKT34AUS:bd02/27/2006:svnIBM:pn8215D7J:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
dmi.product.name: 8215D7J
dmi.product.version: ThinkCentre M52
dmi.sys.vendor: IBM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1068427/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1360803] Re: [Satellite P300, Conexant CX20561 (Hermosa), Black SPDIF Out, Front, Docking station] No sound at all
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- 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/1360803 Title: [Satellite P300, Conexant CX20561 (Hermosa), Black SPDIF Out, Front, Docking station] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: sounds fails regulary. And i can't seems to install Citrix Reciever correctly on Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 2071 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 24 13:05:39 2014 InstallationDate: Installed on 2014-07-11 (43 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=nl_NL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Intern geluid - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 2071 F pulseaudio Symptom_Jack: Black SPDIF Out, Front, Docking station Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Satellite P300, Conexant CX20561 (Hermosa), Black SPDIF Out, Front, Docking station] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.20 dmi.board.name: Satellite P300 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.20:bd01/05/2009:svnTOSHIBA:pnSatelliteP300:pvrPSPC0E-008005DU:rvnTOSHIBA:rnSatelliteP300:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite P300 dmi.product.version: PSPC0E-008005DU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1360803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866103] Re: gnome-shell-extensions disabled after logout.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866103 Title: gnome-shell-extensions disabled after logout. Status in gnome-shell package in Ubuntu: Confirmed Bug description: I have to enable gnome-shell extensions at startup every time. 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 wl ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 19:38:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1866103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866317] Re: Ubuntu 19.10 - Extensions are disabled after every system start
*** This bug is a duplicate of bug 1866103 *** https://bugs.launchpad.net/bugs/1866103 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 1866103, 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. ** Tags added: eoan ** This bug has been marked a duplicate of bug 1866103 gnome-shell-extensions disabled after logout. -- 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/1866317 Title: Ubuntu 19.10 - Extensions are disabled after every system start Status in gnome-shell package in Ubuntu: New Bug description: Extension are disabled every time I start the system, I'm on Ubuntu 19.10 with Gnome Shell 3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1168206] Re: UnicodeDecodeError raised from attach_hardware()
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1168206 Title: UnicodeDecodeError raised from attach_hardware() Status in apport package in Ubuntu: Incomplete Status in xdiagnose package in Ubuntu: Fix Released Bug description: As seen on bugs #1164623 and #1162151: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_xserver-xorg-video-intel.py", line 660, in add_info attach_hardware(report) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 246, in attach_hardware attach_dmi(report) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 201, in attach_dmi value = fd.read().strip() File "/usr/lib/python3.3/codecs.py", line 300, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte attach_dmi() is an apport call. The dmi info's sometimes useful but not crucial to have in X bug reports, so if it's erroring we can safely skip its inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1168206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1345963] Re: [TravelMate P243, Realtek ALC271X, Green Headphone Out, Left] Playback problem
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
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/1345963
Title:
[TravelMate P243, Realtek ALC271X, Green Headphone Out, Left] Playback
problem
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
The laptop speakers work fine but the headphone gives no sound at all.
The headphone uses to work not long before. It also works normally in
Windows 7 which is on this hardware system.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-67.101-generic-pae 3.2.60
Uname: Linux 3.2.0-67-generic-pae i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC271X Analog [ALC271X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: wijit 2788 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9071 irq 45'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10250721,00100100
HDA:80862806,10250721,0010'
Controls : 27
Simple ctrls : 13
Date: Mon Jul 21 12:09:38 2014
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386
(20120423)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Left
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [TravelMate P243, Realtek ALC271X, Green Headphone Out, Left] Playback
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA40_HC
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.01:bd04/20/2012:svnAcer:pnTravelMateP243:pvrV1.01:rvnAcer:rnBA40_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: TravelMate P243
dmi.product.version: V1.01
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1345963/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1131707] Re: No sound with Sound Blaster Z
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- 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/1131707 Title: No sound with Sound Blaster Z Status in alsa-driver package in Ubuntu: Incomplete Bug description: I get no sound with this card in both Ubuntu 12.10 and 13.04. The card is detected but no sound output. --- ApportVersion: 2.8-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: paulo 1748 F pulseaudio /dev/snd/controlC1: paulo 1748 F pulseaudio /dev/snd/controlC0: paulo 1748 F pulseaudio DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2012-12-17 (67 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True NonfreeKernelModules: nvidia Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Tags: raring running-unity Uname: Linux 3.8.0-7-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-02-21 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video dmi.bios.date: 11/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd11/01/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67EVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ApportVersion: 2.8-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: paulo 1748 F pulseaudio /dev/snd/controlC1: paulo 1748 F pulseaudio /dev/snd/controlC0: paulo 1748 F pulseaudio DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2012-12-17 (67 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True NonfreeKernelModules: nvidia Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Tags: raring running-unity Uname: Linux 3.8.0-7-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-02-21 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video dmi.bios.date: 11/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd11/01/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67EVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1131707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly
** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1847712 Title: Desktop icons vanishing when in Activities Overview is jarring and looks ugly Status in gnome-shell-extension-desktop-icons: New Status in Ubuntu UX: New Status in gnome-shell package in Ubuntu: In Progress Bug description: Desktop icons vanishing and reappearing when in Activities Overview is jarring and looks ugly. Suggestions: * Don't hide them in AO, because they will be well shaded anyway; or * Fade them out and in smoothly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 11 14:24:42 2019 InstallationDate: Installed on 2019-05-02 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1847712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866228] Re: Gnome shell extensions are badly broken
I think this is a single issue (updating gnome shell without updating the dependent, packaged extensions) it's just breaks a lot of things. I provided the list so others can check and find that they suffer from the same issue. -- 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/1866228 Title: Gnome shell extensions are badly broken Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, After an upgrade this morning, the following things are not working: - Earlier the Application key brought up something called "Activities", which happens now via ApplicationA or SuperA, the microsoft key - I can not find and search for extensions in the "Software" application. There are just a few addons/extensions, gstreamer ones, fonts and some input - any attempt at removing an installed extension results in a "you have no permission" error, without asking for a password. Apparently gnome-shell is crashing in the background, i'll attach logs if the tool does not. - The Tweak app shows a warning triangle next to the "Dash to panel" extension, by clicking on it the "Extension" thing starts up which shows nothing. - If I install the dash-to-panel extension from a package the top bar does not appears properly, the icons, workplace switcher etc all crumpled into the top left corne,r overlapping each other, thus being mostly unusable. I think that the extensions are not yet upgraded to gnome-shell 3.35, but I have no way to check it. I also have no trivial way to downgrade gnome shell to 3.34. Please advise. Thanks, tg 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 19:59:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-19 (46 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-26 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866317] [NEW] Ubuntu 19.10 - Extensions are disabled after every system start
Public bug reported: Extension are disabled every time I start the system, I'm on Ubuntu 19.10 with Gnome Shell 3.34 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: 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/1866317 Title: Ubuntu 19.10 - Extensions are disabled after every system start Status in gnome-shell package in Ubuntu: New Bug description: Extension are disabled every time I start the system, I'm on Ubuntu 19.10 with Gnome Shell 3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
Could some one please test it and confirm? Just disable animation and then lock the screen. That might be my local issue. -- 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/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in gnome-shell package in Ubuntu: New Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2320 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2320 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2320 Importance: Unknown Status: Unknown -- 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/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 Gnome Shell crashes and restarts when I try to open a dialog window. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-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-0ubuntu17 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 21:15:33 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-02-04 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2020-02-22 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
