[Desktop-packages] [Bug 2018160] [NEW] gnome-shell crashes when top right panel touched on touchscreen
Public bug reported: Version: ubuntu 23.04 Package: gnome-shell: Installed: 44.0-2ubuntu3 Candidate: 44.0-2ubuntu3 Version table: *** 44.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status What I expected: I expected the wifi/bluetooth/dark... menu (in the upper right hand corner) to popup when I touched it on my touchscreen (clicking with a mouse or touchpad works fine, touchscreen press does not). This works as intended on Ubuntu 22.04.2 LTS. What happened: The menu popped up as intended, but 2 seconds later it disappeared, along with the top gnome shell panel (presumably it crashed). A few seconds later the gnome panel restores but without the menu. Running applications (such as firefox) don't seem to be affected. Running on an Asus Vivobook 14 (touchscreen). Tried using both safe mode and proprietary graphic mode with same result. Earlier versions of gnome seem to work fine. Same problem happens in Fedora too. Willing to do additional testing. Really wanna get this working. Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.480 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 18:06:49 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:13d2] LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP470EA_TP470EA ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset layerfs-path=minimal.standard.live.squashfs --- quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP470EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP470EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP470EA.311:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP470EA_TP470EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP470EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP470EA_TP470EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash lunar ubuntu ** Attachment added: "The panel when opened properly" https://bugs.launchpad.net/bugs/2018160/+attachment/5669663/+files/Screenshot%20from%202023-04-29%2018-31-58.png -- 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/2018160 Title: gnome-shell crashes when top right panel touched on touchscreen Status in xorg package in Ubuntu: New Bug description: Version: ubuntu 23.04 Package: gnome-shell: Installed: 44.0-2ubuntu3 Candidate: 44.0-2ubuntu3 Version table: *** 44.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status What I expected: I expected the wifi/bluetooth/dark... menu (in the upper right hand corner) to popup when I touched it on my touchscreen (clicking with a mouse or touchpad works fine, touchscreen press does not). This works as intended on Ubuntu 22.04.2 LTS. What happened: The menu popped up as intended, but 2 seconds later it disappeared, along with the top gnome shell panel (presumably it crashed). A few seconds later the gnome panel restores but without the menu.
[Desktop-packages] [Bug 1944581] [NEW] Session preference not respected; Wayland session started despite Xorg being selected
Public bug reported:
Session preference, in this case, is ignored in two scenarios:
* Cold boot, first log in: Even when Xorg session is picked through the cog
menu in the bottom right, Wayland session is started. Only when explicitly
re-selecting Xorg from this session picker, despite being selected and
displaying as selected already, the Xorg session is registered as the preferred
one.
* Gnome session crash ("Oh no! Something has gone wrong" error). After
restoring session, Wayland starts by default, despite initially choosing Xorg
session.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gdm3 41~rc-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 22 17:03:27 2021
InstallationDate: Installed on 2020-06-25 (453 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gdm3
UpgradeStatus: Upgraded to impish on 2021-09-17 (4 days ago)
modified.conffile..etc.gdm3.custom.conf: [modified]
mtime.conffile..etc.gdm3.custom.conf: 2020-12-10T18:16:25.985567
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug impish third-party-packages
--
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/1944581
Title:
Session preference not respected; Wayland session started despite Xorg
being selected
Status in gdm3 package in Ubuntu:
New
Bug description:
Session preference, in this case, is ignored in two scenarios:
* Cold boot, first log in: Even when Xorg session is picked through the cog
menu in the bottom right, Wayland session is started. Only when explicitly
re-selecting Xorg from this session picker, despite being selected and
displaying as selected already, the Xorg session is registered as the preferred
one.
* Gnome session crash ("Oh no! Something has gone wrong" error). After
restoring session, Wayland starts by default, despite initially choosing Xorg
session.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gdm3 41~rc-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 22 17:03:27 2021
InstallationDate: Installed on 2020-06-25 (453 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gdm3
UpgradeStatus: Upgraded to impish on 2021-09-17 (4 days ago)
modified.conffile..etc.gdm3.custom.conf: [modified]
mtime.conffile..etc.gdm3.custom.conf: 2020-12-10T18:16:25.985567
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1944581/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@61, yes. I had tried it and it works. It also has mSBC support - https://github.com/Arkq/bluez-alsa/issues/29, but the author himself admits that mSBC support is buggy and is not being developed. I could get it to work, but the audio was very choppy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@63 - your headset likely doesn't support mSBC (16 KHz), only CVSD (8KHz) in HFP/HSP mode. If that is the case, any fix - using a USB soundcard as you did, or a software fix (which this page is tracking) isn't gonna help. If it does support mSBC, 1Mii B10, and Avantree Leaf, Creative BT-W3 should be able to give decent quality audio. The definition of 'decent' varies of course. Most people in this age and time wouldn't be happy with 8 KHz (else, this page wouldn't exist), but mSBC is decent enough for most people, at least for typical voice calls. You can check the sampling frequency used very easily using Audacity > Record a few seconds using the mic in question > Analyze > Plot Spectrum. Note that Audacity plots in log scale for freq by default. If the highest freq component is just below 4 KHz, it is using CVSD @ 8 KHz sampling, and your headset is the likely culprit. If the highest component is 8 KHz, it is using mSBC @ 16 KHz. If you think that is not good enough, your options are limited. You can use FastStream (FS) which is supported only by a limited number of headsets, as well as by dongles such as Leaf, 1Mii B10, Creative BT-W2. No OS afaik supports it, so you can't use the dongle. Many devices have buggy implementations of FS. AptX LL also supposedly has bidirectional audio support, but the voiceback part is not supported by any device that I know of. ** Bug watch added: github.com/Arkq/bluez-alsa/issues #29 https://github.com/Arkq/bluez-alsa/issues/29 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~de
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@ gyhor, I am pretty sure you got a faulty 1Mii B10. It doesnt get past enumeration, so it is not a compatibility issue. You also mention that it was tried on different systems and didn't work. Time to get it replaced. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@ #47 Creative Labs BT-W3 supports mSBC (https://sg.creative.com/p/speakers/creative-bt-w3). I had checked with them before buying one. Tried pairing it with Jabra Talk 15, as well as Avantree Clipper Pro, and I can confirm that it works. Tried plotting the spectrum of the recorded audio using Audacity to confirm. Affirmative. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725803] Re: Double-click to expand a super wide column (process name) ruins your day
** Attachment removed: "process-name-column.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1725803/+attachment/4983258/+files/process-name-column.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1725803 Title: Double-click to expand a super wide column (process name) ruins your day Status in gnome-system-monitor package in Ubuntu: New Bug description: Google Chrome has long process names. By long I mean hundreds and hundreds of characters wide (see picture). Without knowing this I unsuspectingly double-clicked the process name column edge in the processes tab, and ended up with a column that stretched far, far to the right. The only way to get back to normal was to scroll to the far right and tediously grab the column and shrink it manually over and over until it got back to normal. Before doing that I tried double-clicking again to try and make it shrink to its smallest size -- that didn't work. I generally tend to expect the reverse operation to work when working with UI. Open-Close, Expand-Collapse, Show-Hide, etc. After doing that I -- unfortunately -- tried to disable the process name column in the column context menu (right click). That made everything worse. Another column took over the super wide column that previously held process names, and pretty much every other existing column seemingly disappeared from the table. After some head- scratching I figured out that all other columns had collapsed into zero width. I tried restarting the application -- didn't work; it had saved my column setup. Adjusting some column widths went from a simple task to becoming a real chore. Expectations: I expected to be able to collapse the column the same way I expanded it. I also expected all other columns to keep their own sizes when disabling/hiding a column. In hindsight I now also expect column expansion to have some kind of sanity check. Note: I was positive that I had included the scroll bars in the screenshots, but apparently they timed out and disappeared, so the pictures kind of fail to illustrate the extent of the column width. Description: Ubuntu 17.10 Release: 17.10 gnome-system-monitor: Installed: 3.26.0-1 Candidate: 3.26.0-1 Version table: *** 3.26.0-1 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1725803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574243] Re: Unable to adjust screen backlight on login screen on Macbook Pro (early 2015)
** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645251/+files/CurrentDmesg.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645265/+files/XorgLog.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645266/+files/XorgLogOld.txt -- 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/1574243 Title: Unable to adjust screen backlight on login screen on Macbook Pro (early 2015) Status in xorg package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Fresh install of 16.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Don't know. The guide to identify the package told me all login screen issues were "LightDM". ubuntu-bug told me that package was not installed. 3) What you expected to happen To be able to adjust screen backlight brightness with the dedicated hardware buttons on the login screen, in order to be able log in. This works as expected whenever I'm logged in. 4) What happened instead I had to log in from an almost black login screen with no backlight. I believe this bug was present in 15.10 as well. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 24 13:58:00 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:013f] InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=dd7fd213-44e3-45de-afe3-efd8c5825c1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B16.1602111810 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B16.1602111810:bd02/11/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 24 02:40:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41002 vendor APP xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890202] Re: Xorg freeze
... Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down... Starting System Logging Service... Starting Secure Boot updates for DB and DBX... Starting Snap Daemon... Starting Switcheroo Control Proxy service... Starting Login Service... Starting Thermal Daemon Service... Starting Disk Manager... Starting WPA supplicant... [ OK ] Finished Detect the available GPUs and deal with any system changes. [ OK ] Finished Restore /etc/resolv.conf if the system crashed before the ppp link was shut down. [ OK ] Finished GRUB failed boot detection. [ OK ] Started System Logging Service. [ OK ] Finished Secure Boot updates for DB and DBX. [ OK ] Finished Remove Stale Online ext4 Metadata Check Snapshots. [ OK ] Started Bluetooth service. [ OK ] Reached target Bluetooth. [ OK ] Started Avahi mDNS/DNS-SD Stack. [ OK ] Started Make remote CUPS printers available locally. [ OK ] Started WPA supplicant. [ OK ] Started Network Manager. [ OK ] Reached target Network. Starting Network Manager Wait Online... Starting OpenVPN service... Starting Permit User Sessions... [ OK ] Started Thermal Daemon Service. [ OK ] Finished OpenVPN service. [ OK ] Finished Permit User Sessions. [ OK ] Started Switcheroo Control Proxy service. Starting Save/Restore Sound Card State... Starting GNOME Display Manager... Starting Hold until boot process finishes up... [ OK ] Started IIO Sensor Proxy service. Starting Hostname Service... [ OK ] Finished Save/Restore Sound Card State. [ OK ] Reached target Sound Card. [ OK ] Started GNOME Display Manager. [ OK ] Started Authorization Manager. Starting Modem Manager... [ OK ] Started Accounts Service. [ OK ] Started Dispatcher daemon for systemd-networkd. [ OK ] Started Disk Manager. [ OK ] Started Modem Manager. [ OK ] Started Snap Daemon. Starting Wait until snapd is fully seeded... [ OK ] Started Hostname Service. Starting Network Manager Script Dispatcher Service... [ OK ] Started Network Manager Script Dispatcher Service. [ OK ] Started Login Service. [ OK ] Started Unattended Upgrades Shutdown. [ OK ] Started LSB: automatic crash report generation. [ OK ] Started LSB: Record successful boot for GRUB. [ OK ] Created slice User Slice of UID 125. Starting User Runtime Directory /run/user/125... [ OK ] Finished User Runtime Directory /run/user/125. Starting User Manager for UID 125... [ OK ] Started User Manager for UID 125. [ OK ] Started Session c1 of user gdm. Starting Daemon for power management... Starting RealtimeKit Scheduling Policy Service... [ OK ] Started RealtimeKit Scheduling Policy Service. [ OK ] Started Daemon for power management. Starting Locale Service... [ OK ] Started Locale Service. Starting Location Lookup Service... Starting PackageKit Daemon... [ OK ] Started Location Lookup Service. [ OK ] Started PackageKit Daemon. Starting Fingerprint Authentication Daemon... Mounting Mount unit for snapd, revision 7264... [ OK ] Started Fingerprint Authentication Daemon. [ OK ] Mounted Mount unit for snapd, revision 7264. Starting Manage, Install and Generate Color Profiles... [ OK ] Stopped Snap Daemon. Starting Snap Daemon... [ OK ] Started Snap Daemon. Mounting Mount unit for core18, revision 1705... [ OK ] Mounted Mount unit for core18, revision 1705. Mounting Mount unit for gnome-3-34-1804, revision 24... [ OK ] Mounted Mount unit for gnome-3-34-1804, revision 24. Mounting Mount unit for gtk-common-themes, revision 1506... [ OK ] Mounted Mount unit for gtk-common-themes, revision 1506. Mounting Mount unit for snap-store, revision 433... [ OK ] Mounted Mount unit for snap-store, revision 433. [ OK ] Finished Wait until snapd is fully seeded. [ OK ] Reached target Sleep. Starting Suspend... [ OK ] Finished Suspend. [ OK ] Stopped target Sleep. [ OK ] Reached target Suspend. [ OK ] Stopped target Suspend. Starting Network Manager Script Dispatcher Service... [ OK ] Started Network Manager Script Dispatcher Service. [ OK ] Reached target Sleep. Starting Suspend... Mon Aug 03 17:11:51 EDT 2020 [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Forward Password Requests to Plymouth Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Mounted Mount unit for core18, revision 1705. [ OK ] Mounted Mount unit for gnome-3-34-1804, revision 24. [ OK ] Mounted Mount unit for snap-store, revision 433. [ OK ] Mounted Mount unit for snapd, revision 7264. [ OK ] Mounted Mount unit for gtk-common-themes, revision 1506. [ OK ] Started Journal Service
[Desktop-packages] [Bug 1890202] [NEW] Xorg freeze
Public bug reported: Plymouth never returns from startup. Startup takes intermittently long periods of time. someuser@someuser-l01:~$ systemd-analyze blame | cat 25.226s accounts-daemon.service 25.173s udisks2.service 25.150s gpu-manager.service 25.149s networkd-dispatcher.service 25.129s snapd.service 25.125s systemd-logind.service 25.092s ModemManager.service 25.079s iio-sensor-proxy.service 3.787s plymouth-quit-wait.service 1.856s upower.service 427ms dev-nvme0n1p2.device 356ms dev-loop1.device 350ms dev-loop2.device 313ms dev-loop3.device 312ms dev-loop4.device 229ms systemd-resolved.service 207ms systemd-rfkill.service 168ms rtkit-daemon.service 132ms snap-snap\x2dstore-433.mount 131ms snap-snapd-7264.mount 130ms snap-gtk\x2dcommon\x2dthemes-1506.mount 115ms systemd-timesyncd.service 114ms avahi-daemon.service 96ms polkit.service 94ms snap-core18-1705.mount 93ms snap-gnome\x2d3\x2d34\x2d1804-24.mount 92ms apport.service 92ms systemd-udev-trigger.service 90ms e2scrub_reap.service 84ms dev-loop0.device 75ms systemd-journald.service 73ms switcheroo-control.service 71ms user@1000.service 70ms swapfile.swap 69ms keyboard-setup.service 68ms thermald.service 68ms grub-common.service 67ms wpa_supplicant.service 63ms user@125.service 57ms systemd-udevd.service 46ms kerneloops.service 43ms apparmor.service 41ms grub-initrd-fallback.service 41ms alsa-restore.service 41ms rsyslog.service 37ms secureboot-db.service 35ms systemd-journal-flush.service 35ms systemd-fsck@dev-disk-by\x2duuid-9979\x2d84D8.service 33ms openvpn.service 33ms snapd.seeded.service 32ms systemd-backlight@backlight:intel_backlight.service 32ms systemd-backlight@leds:dell::kbd_backlight.service 31ms systemd-update-utmp-runlevel.service 30ms bluetooth.service 30ms systemd-user-sessions.service 29ms gdm.service 29ms snapd.apparmor.service 28ms packagekit.service 27ms plymouth-start.service 25ms pppd-dns.service 25ms systemd-tmpfiles-setup.service 20ms systemd-modules-load.service 20ms NetworkManager.service 15ms colord.service 12ms plymouth-read-write.service 10ms modprobe@drm.service 10ms dev-hugepages.mount 9ms setvtrgb.service 9ms systemd-sysctl.service 9ms dev-mqueue.mount 9ms systemd-random-seed.service 9ms systemd-sysusers.service 9ms systemd-tmpfiles-setup-dev.service 9ms sys-kernel-debug.mount 8ms boot-efi.mount 8ms sys-kernel-tracing.mount 8ms user-runtime-dir@1000.service 8ms systemd-remount-fs.service 8ms systemd-update-utmp.service 7ms user-runtime-dir@125.service 6ms kmod-static-nodes.service 6ms console-setup.service 3ms sys-fs-fuse-connections.mount 3ms sys-kernel-config.mount 2ms ufw.service 1ms snapd.socket Only able to boot if I interrupt plymouth, and manually wait out systemd targets. When booted with multiple screens, constant graphical corruption and distortion is seen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 17:28:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:080d] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XL [Radeon RX Vega M GL] [1002:694e] InstallationDate: Installed on 2020-08-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9575 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ea1ef229-ef86-4657-909b-498914de360e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 vers
[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10
@seb128 Sebastien, are you referring to this page? https://bugs.launchpad.net/ubuntu/+source/gnome-shell The specific issue is that the "dock" is exposed and it doesn't feel fullscreen. System info: Intel Integrated Graphics 530 (NO GPU, just processor) I've tried default 19.10 input device modesetting as well as specifying with an intel-20 xorg config to use Device driver "intel" (rather than modesetting) Sebastien this is what I'm trying to launch, it uses OpenGL and is coded in C. It always worked fine launching in fullscreen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849787 Title: The dock is shown in front of full screen windows since 19.10 Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10
What do I need to do to have this looked at more closely? I can send a screenshot of the game in question. The input lag is so absurdly high with 19.10 and this bug among other things makes 19.10 feel like a huge regression for me. I am using 19.04 now and everything runs faster and I don't get this bug where the dock is infront of the the fullscreen application. I tried wayland, with modesetting, without modesetting - nothing works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849787 Title: The dock is shown in front of full screen windows since 19.10 Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10
Also just want to note: it feels like since the Dock is showing in fullscreen (it isn't really fullscreen). There is a huge amount of CPU usage + input lag. Switching back to 19.04 was like night and day. OpenGL 64-bit game runs fast and good on old release. On new one- 19.10 the dock is not possible to hide and it doesn't feel like true fullscreen (huge input lag with 144 Hz monitor). (Apologies if this is in the wrong place to report bugs pertaining to dock showing in full in other applications - OpenGL games etc), it's my first bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849787 Title: The dock is shown in front of full screen windows since 19.10 Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10
I have the same issue. It forced me to revert back to 19.04 from latest ver. of 19.10. It was already a problem since week prior to release of 19.10 (when I first tried). 19.10 latest ver on Intel Graphics 530. This bug is impacting on: modesetting driver xorg as well as intel driver xorg. I also tried Wayland to same result. This is impacting a fullscreen video game I'm playing in OpenGL. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849787 Title: The dock is shown in front of full screen windows since 19.10 Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Have the same issue in Ubuntu 18.04.2 LTS. In pavucontrol or in blueman-applet: If select A2DP sound works; If select HSP/HFP sound/mic do not work. bluetoothctl output: Name: Jabra Elite 65t Alias: Jabra Elite 65t Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) UUID: Serial Port (1101--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: bluetooth:v0067p247Ed020E -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps
EOG also applies fullscreen profiles to image! Notice most of preinstalled color profiles in Settings->Devices->Color does not support whole screen correction (they are marked with bulb icon). So this is normal application behavior to apply system-wide color profile to image. But when fullscreen profile selected, it used firstly in EOG for certain image and secondly by the system for final correction. In my case screen has noticeable bluish cast, so ICC does significant color shift to compensate it. But when applied twice, it makes images yellowish in EOG. While Gimp and Shotwell display colors correctly. -- 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/938751 Title: Images are washed out or colors are skewed in some apps Status in Eye of GNOME: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825762] [NEW] package install-info:i386 6.1.0.dfsg.1-5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127
Public bug reported: Crossgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: install-info:i386 6.1.0.dfsg.1-5 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 21 18:02:49 2019 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2015-03-04 (1509 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: texinfo Title: package install-info:i386 6.1.0.dfsg.1-5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1825762 Title: package install-info:i386 6.1.0.dfsg.1-5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 Status in texinfo package in Ubuntu: New Bug description: Crossgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: install-info:i386 6.1.0.dfsg.1-5 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 21 18:02:49 2019 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2015-03-04 (1509 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: texinfo Title: package install-info:i386 6.1.0.dfsg.1-5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1825762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812057] Re: Upgrade Lost Firefox ESR
No, of course not. If it had, I wouldn't have upgraded. This is typical Ubuntu methods; no concern for the user. I'll not make that mistake again. -- 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/1812057 Title: Upgrade Lost Firefox ESR Status in firefox package in Ubuntu: Invalid Bug description: System was upgraded from Xubuntu 14 to 16 by DVD. It wiped out many things, including the installation of Firefox ESR. ESR was manually reinstalled, but there appears to be no integration with the former profiles. While they still exist, both Firefox Quantum and Firefox ESR see the exact same profiles. There appears to be no way to remedy the problem. No crash is involved. If -profilemanager is used in Firefox, the same choices appear in both versions. This was not the case prior to the upgrade. Description: Ubuntu 16.04.5 LTS Release: 16.04 firefox-esr: Installed: 52.9.0esr-1~16.04.york0 Candidate: 52.9.0esr-1~16.04.york0 Version table: *** 52.9.0esr-1~16.04.york0 500 500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status firefox: Installed: 64.0+build3-0ubuntu0.16.04.1 Candidate: 64.0+build3-0ubuntu0.16.04.1 Version table: *** 64.0+build3-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 45.0.2+build1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1812057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812057] Re: Upgrade Lost Firefox ESR
Obviously this has nothing to do with PPAs. This has to do with the system wiping out all the installed programs and forcing manual re- installations. In this specific case, Ubuntu also damaged the linkages between programs and their data. This is most bizarre because one would have thought that the upgrade process would do no such thing and the strong promotion to do the upgrade would imply to most people that their productivity would be protected. -- 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/1812057 Title: Upgrade Lost Firefox ESR Status in firefox package in Ubuntu: Invalid Bug description: System was upgraded from Xubuntu 14 to 16 by DVD. It wiped out many things, including the installation of Firefox ESR. ESR was manually reinstalled, but there appears to be no integration with the former profiles. While they still exist, both Firefox Quantum and Firefox ESR see the exact same profiles. There appears to be no way to remedy the problem. No crash is involved. If -profilemanager is used in Firefox, the same choices appear in both versions. This was not the case prior to the upgrade. Description: Ubuntu 16.04.5 LTS Release: 16.04 firefox-esr: Installed: 52.9.0esr-1~16.04.york0 Candidate: 52.9.0esr-1~16.04.york0 Version table: *** 52.9.0esr-1~16.04.york0 500 500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status firefox: Installed: 64.0+build3-0ubuntu0.16.04.1 Candidate: 64.0+build3-0ubuntu0.16.04.1 Version table: *** 64.0+build3-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 45.0.2+build1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1812057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812057] Re: Upgrade Lost Firefox ESR
Olivier, I'm afraid that you appear to be laboring under a misunderstanding. Please note that the issue is not what is supported, but rather the stupidity of upgrade design that wipes out existing programs. There is absolutely no reason to not care enough about users to not leave things alone. Of course I recognize that I am assuming that software people should care about others. Just MHO. « Please report bugs with my packages to **me** not to the upstream projects. » I don't know what this means. Please explain. -- 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/1812057 Title: Upgrade Lost Firefox ESR Status in firefox package in Ubuntu: Invalid Bug description: System was upgraded from Xubuntu 14 to 16 by DVD. It wiped out many things, including the installation of Firefox ESR. ESR was manually reinstalled, but there appears to be no integration with the former profiles. While they still exist, both Firefox Quantum and Firefox ESR see the exact same profiles. There appears to be no way to remedy the problem. No crash is involved. If -profilemanager is used in Firefox, the same choices appear in both versions. This was not the case prior to the upgrade. Description: Ubuntu 16.04.5 LTS Release: 16.04 firefox-esr: Installed: 52.9.0esr-1~16.04.york0 Candidate: 52.9.0esr-1~16.04.york0 Version table: *** 52.9.0esr-1~16.04.york0 500 500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status firefox: Installed: 64.0+build3-0ubuntu0.16.04.1 Candidate: 64.0+build3-0ubuntu0.16.04.1 Version table: *** 64.0+build3-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 45.0.2+build1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1812057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812057] Re: Upgrade Lost Firefox ESR
dpkg -S /usr/bin/firefox diversion by firefox-esr from: /usr/bin/firefox diversion by firefox-esr to: /usr/bin/firefox.real firefox-esr, firefox: /usr/bin/firefox ** Package changed: ubuntu => firefox (Ubuntu) -- 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/1812057 Title: Upgrade Lost Firefox ESR Status in firefox package in Ubuntu: New Bug description: System was upgraded from Xubuntu 14 to 16 by DVD. It wiped out many things, including the installation of Firefox ESR. ESR was manually reinstalled, but there appears to be no integration with the former profiles. While they still exist, both Firefox Quantum and Firefox ESR see the exact same profiles. There appears to be no way to remedy the problem. No crash is involved. If -profilemanager is used in Firefox, the same choices appear in both versions. This was not the case prior to the upgrade. Description: Ubuntu 16.04.5 LTS Release: 16.04 firefox-esr: Installed: 52.9.0esr-1~16.04.york0 Candidate: 52.9.0esr-1~16.04.york0 Version table: *** 52.9.0esr-1~16.04.york0 500 500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status firefox: Installed: 64.0+build3-0ubuntu0.16.04.1 Candidate: 64.0+build3-0ubuntu0.16.04.1 Version table: *** 64.0+build3-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 45.0.2+build1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1812057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
I'm amazed that this bug has been opened for over a year and there is no meaningful status update to be found. I'd like to echo the questions and comments posted by another user above at Comment # 197: I am just a user, thus this post may sound naive but perhaps it gives a different perspective: Sane used to work until "something" was changed an now it doesn't work anymore for many people. My naive questions: what was/is the benefit of the change? do the benefits outweigh the created problems? if not is there a way to fall back to the original situation? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2
alsa-info output: http://www.alsa- project.org/db/?f=12cbba27e12cc27ede2a9934df4f3a1ce12ff545 -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2
Have the same issue with Ubuntu 17.10 $ uname -a Linux raiaHPx2 4.13.0-39-generic #44-Ubuntu SMP Thu Apr 5 14:25:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux "aplay -l" gives the following $aplay -l List of PLAYBACK Hardware Devices card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytcrrt5640 [bytcr-rt5640], device 0: Baytrail Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytcrrt5640 [bytcr-rt5640], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 Attempted to solve with following the directions here with dkms https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but did not fix the no sound issue. -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
After upgrading from 17.04 to 17.10 I also had this issue with error: > pulseaudio[6267]: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Fixed like in #4 by commenting load-module module-switch-on-connect out of /etc/pulse/default.pa Have not tried any plug-in-devices to see if this fix affects their usage. -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731674] [NEW] Can't rotate the screen
Public bug reported: I have recently installed Ubuntu 17.10. After I logged in, the screen rotated sideways. I tried "xrandr -o normal", but it didn't work. What should I do? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 11 19:44:03 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-11 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22C7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 90.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096E100800405F0620180:rvnHewlett-Packard:rn22C7:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 096E100800405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- 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/1731674 Title: Can't rotate the screen Status in xorg package in Ubuntu: New Bug description: I have recently installed Ubuntu 17.10. After I logged in, the screen rotated sideways. I tried "xrandr -o normal", but it didn't work. What should I do? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 11 19:44:03 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-11 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22C7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 90.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096E100800405F0620180:rvnHewlett-Packard:rn22C7:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 096E100800405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1731674/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1232606] Re: Nautilus freezes accessing Android via MTP when USB debugging enabled
I'm getting the same error that #4 is getting with a Samsung Galaxy S5 Mini on ubuntu 16.04. Like with OP, disabling USB debugging fixed the issue. libmtp error: could not get object handles. -- 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/1232606 Title: Nautilus freezes accessing Android via MTP when USB debugging enabled Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus started freezing on me when I tried to access certain folders on my Android phone (Sony Xperia P) via MTP, such as the DCIM folder. I would have to kill Nautilus and then unplug and reconnect the phone. Sometimes after this the phone would be in the list of devices, but when I clicked on it no volume would appear. Thunar didn't show the same freezing behaviour, but once the volume stopped appearing in Nautilus it would stop appearing in Thunar too. This behaviour continued even after I did a factory reset on the phone. I could not reproduce the behaviour in Windows 7. Disabling USB debugging on the phone fixed the problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-30.22-lowlatency 3.8.13.6 Uname: Linux 3.8.0-30-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 29 02:14:03 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'848x580+0+24'" InstallationDate: Installed on 2013-08-22 (37 days ago) InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-09-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1232606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
confirm issue on UBUNTU 16.04 with pulseaudio 8.0 Vahid Mardani's script is a valid temporary workaround by running it every time the bug appear -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175608] Re: Thumbnails too small in 'open file' dialog nautilus
This is a basic usability feature that many users have been requesting for years. See, for example, the following discussion threads at various forums: http://askubuntu.com/questions/150839/is-there-some-way-to-get-a-more- usable-file-chooser-dialog https://forum.xfce.org/viewtopic.php?id=10133 https://www.reddit.com/r/linux/comments/1x04fc/want_thumbnails_in_the_gtk_file_picker_the_bug/ https://bugzilla.gnome.org/show_bug.cgi?id=141154 https://github.com/luakit/luakit/issues/232 ** Bug watch added: GNOME Bug Tracker #141154 https://bugzilla.gnome.org/show_bug.cgi?id=141154 ** Bug watch added: github.com/luakit/luakit/issues #232 https://github.com/luakit/luakit/issues/232 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=141154 Importance: Unknown Status: Unknown -- 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/1175608 Title: Thumbnails too small in 'open file' dialog nautilus Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: When trying to upload image files to e.g. websites like marktplaats.nl (kind of ebay) I get very, very small image thumbnails. There seems no way to enlarge these thumbnails. All options only work if Nautilus is used stand alone, but not with the open file dialog that is being used to upload files. I have attached a screen dump just to show what I mean. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1175608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1297849] Re: [SRU] Virtual private network connection fails after distribution upgrade due to outdated Network Manager configuration files
Problem pops up again for me after upgrading from 15.10 to 16.04. This time error message is a bit different: [1468865322.8065] vpn-connection[0x29d15b0,,"XXX",0]: Failed to request VPN secrets #3: No agents were available for this request. Ubuntu 16.04 dpkg --list |grep openconnect ii libopenconnect5:amd64 7.06-2build2 amd64open client for Cisco AnyConnect VPN - shared library ii network-manager-openconnect1.2.0-0ubuntu0.16.04.1 amd64network management framework (OpenConnect plugin) ii network-manager-openconnect-gnome 1.2.0-0ubuntu0.16.04.1 amd64network management framework (OpenConnect plugin GNOME GUI) ii openconnect7.06-2build2 amd64open client for Cisco AnyConnect VPN Connection from command line is working. I tried to recreate connection and reinstalling. What else can I try? -- 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/1297849 Title: [SRU] Virtual private network connection fails after distribution upgrade due to outdated Network Manager configuration files Status in One Hundred Papercuts: Confirmed Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in network-manager-openvpn package in Ubuntu: Triaged Status in network-manager-vpnc package in Ubuntu: Triaged Status in network-manager-applet source package in Trusty: Fix Released Status in network-manager-openconnect source package in Trusty: Confirmed Status in network-manager-openvpn source package in Trusty: Confirmed Status in network-manager-vpnc source package in Trusty: Confirmed Status in network-manager-openconnect source package in Xenial: Fix Released Status in network-manager-openvpn source package in Xenial: Confirmed Status in network-manager-vpnc source package in Xenial: Confirmed Bug description: [Impact] * People who are using VPN services (of any kind, using vpnc, openvpn, pptp, etc. [Test Case] HOW TO REPRODUCE 1. Upgrade to a newer Ubuntu release. 2. Using the Network Manager application, try to start a virtual private network connection. EXPECTED BEHAVIOUR - The connection to complete successfully. ACTUAL BEHAVIOUR - The current configuration files, created by a previous network manager installation in the gconf user home folder, makes the application to misbehave; returning a log like this: [Regression Potential] May cause Gnome-Shell detection to give up prematurely. [PPA with a Possible Solution] Please see the https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1297849/comments/107 on information how to try the PPA with a solution to the bug that has the patch https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1297849/+attachment/4253965/+files/network-manager-applet-1297849.patch applied. [Additional information] Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: Starting VPN service 'vpnc'... Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 24419 Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: VPN service 'vpnc' appeared; activating connections Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: [1395840211.74057] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: Policy set 'blizzard' (wlan0) as default for IPv4 routing and DNS. Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: [1395840211.74406] [nm-system.c:1266] nm_system_replace_default_ip6_route(): (wlan0): failed to set IPv6 default route: -7 Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: Policy set 'blizzard' (wlan0) as default for IPv6 routing and DNS. Mar 26 13:23:36 hprem-rmbp NetworkManager[855]: VPN service 'vpnc' disappeared ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-vpnc 0.9.8.6-1ubuntu2 Uname: Linux 3.13.0-031300-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 26 13:26:42 2014 InstallationDate: Installed on 2014-01-17 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140115) SourcePackage: network-manager-vpnc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1297849/+subscriptions -- Mailing list: https://launchpad.net/~d
[Desktop-packages] [Bug 1547374] Re: "Monospace Regular 8" became wider
I believe this is the same problem: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1589046 For me disable font hinting did not make font looks same as in 15.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1547374 Title: "Monospace Regular 8" became wider Status in fontconfig package in Ubuntu: Confirmed Bug description: I've been using gnome-terminal with "Monospace Regular 8" for years, which always had a 6x13 px font size (the same size as xterm, just nicer antialiasing). With yesterday's update in Xenial, it became wider: 7x13 px each cell (and less pleasing to my eyes). The neighbor sizes "Monospace Regular 7" is 5px wide, "Monospace Regular 9" is 7px wide just as "Monospace Regular 8", only taller. So it doesn't make sense for me for "Monospace Regular 8" to be 7px wide instead of 6px in between the two neighboring sizes as it used to be. (No clue which package is the culprit, sorry.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 19 09:11:41 2016 InstallationDate: Installed on 2012-05-30 (1359 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: fontconfig UpgradeStatus: Upgraded to xenial on 2016-02-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1547374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540088] Re: NetworkManager crashes after upgrade, preventing nm-applet to show
great, i confirm that workaround worked for me, thanks -- 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/1540088 Title: NetworkManager crashes after upgrade, preventing nm-applet to show Status in network-manager package in Ubuntu: Confirmed Bug description: After the last upgrade of Ubuntu 14.04.3 LTS , NetworkManager keeps crashing. after `sudo service network-manager start` I get the following output in dmesg: [2016-01-31 14:28:47] traps: NetworkManager[11040] general protection ip:469fee sp:7ffc6879aa00 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11040) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11049] general protection ip:469fee sp:7ffecca7d9d0 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11049) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11062] general protection ip:469fee sp:7ffc218a9f50 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11062) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11076] general protection ip:469fee sp:7fff7f128270 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11076) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11088] general protection ip:469fee sp:7fff66528f90 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11088) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11092] general protection ip:469fee sp:7fffab819070 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11092) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11096] general protection ip:469fee sp:7ffe7aa91c20 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11096) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11100] general protection ip:469fee sp:7ffedfe81460 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11100) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11104] general protection ip:469fee sp:7ffdc475f140 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11104) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11108] general protection ip:469fee sp:7ffdeb437010 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11108) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] init: network-manager main process (2) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager respawning too fast, stopped This problem prevents me to see nm-applet, and makes me unable to connect to WiFi network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540088] Re: NetworkManager crashes after upgrade, preventing nm-applet to show
yes, manually like in 2004... i'm having a bad time explaining this to my little daughter -- 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/1540088 Title: NetworkManager crashes after upgrade, preventing nm-applet to show Status in network-manager package in Ubuntu: Confirmed Bug description: After the last upgrade of Ubuntu 14.04.3 LTS , NetworkManager keeps crashing. after `sudo service network-manager start` I get the following output in dmesg: [2016-01-31 14:28:47] traps: NetworkManager[11040] general protection ip:469fee sp:7ffc6879aa00 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11040) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11049] general protection ip:469fee sp:7ffecca7d9d0 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11049) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11062] general protection ip:469fee sp:7ffc218a9f50 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11062) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11076] general protection ip:469fee sp:7fff7f128270 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11076) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11088] general protection ip:469fee sp:7fff66528f90 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11088) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11092] general protection ip:469fee sp:7fffab819070 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11092) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11096] general protection ip:469fee sp:7ffe7aa91c20 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11096) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11100] general protection ip:469fee sp:7ffedfe81460 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11100) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11104] general protection ip:469fee sp:7ffdc475f140 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11104) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11108] general protection ip:469fee sp:7ffdeb437010 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11108) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] init: network-manager main process (2) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager respawning too fast, stopped This problem prevents me to see nm-applet, and makes me unable to connect to WiFi network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
Upgraded to Kubuntu 15.04 and with that came nvidia 346.59 ( 346.59-0ubuntu1 ) $ uname -a Linux redacted 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --list | grep 346.59 ii libcuda1-346 346.59-0ubuntu1 amd64NVIDIA CUDA runtime library ii libxnvctrl0 346.59-0ubuntu1 amd64NV-CONTROL X extension (runtime library) ii nvidia-346346.59-0ubuntu1 amd64NVIDIA binary driver - version 346.59 ii nvidia-opencl-icd-346 346.59-0ubuntu1 amd64NVIDIA OpenCL ICD ii nvidia-settings 346.59-0ubuntu1 amd64Tool for configuring the NVIDIA graphics driver You can specify which GPU to use with the program nvidia-settings. Using: the GPU PRIME Profiles set for Intel (Power Saving Mode) which sets: $cat /proc/acpi/bbswitch :01:00.0 OFF After a few days of this setting I can report that the issue of the dimming screen and random lock-ups seems to have disappeared. I've just now run nvidia-settings to change back to use the GPU that's labeled NVIDIA (Performance Mode) and will update in later if this also no-longer has the issue. Tentatively reporting as fixed pending further testing . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA Status in nvidia-graphics-drivers-331 package in Ubuntu: Expired Bug description: Ubuntu 14.10 has random freezes and lock ups while using NVIDIA 331.113. WORKAROUND: Use nouveau. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afan 9511 F pulseaudio /dev/snd/controlC0: afan 9511 F pulseaudio CurrentDesktop: KDE Date: Wed Dec 24 16:49:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-23 (1 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=31ffafeb-d84a-4173-81a4-99a3bde628f3 ro quiet splash rcutree.rcu_idle_gp_delay=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.21 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.53 dmi.chassis.asset.tag: USH446L1YV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.21:bd08/13/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.53:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1405489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405489] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA
Christopher, I tried. Running the program from http://www.nvidia.com/Download/driverResults.aspx/82252/en-us as sudo ./NVIDIA-Linux-x86_64-346.47.run results in the following: nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Wed Mar 4 14:44:37 2015 installer version: 346.47 PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin nvidia-installer command line: ./nvidia-installer Using: nvidia-installer ncurses user interface - Detected 8 CPUs online; setting concurrency level to 8. WARNING: You do not appear to have an NVIDIA GPU supported by the 346.47 NVIDIA Linux graphics driver installed in this system. For further details, please see the appendix SUPPORTED NVIDIA GRAPHICS CHIPS in the README available on the Linux driver download page at www.nvidia.com. - I find the statement odd as my card is listed by lspci as $ lspci | grep -i nvid 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev ff) 01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev ff) which is on the list. It then asks me if I want to continue with the installation. Continue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1405489 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.10 random freeze and lock up with NVIDIA Status in nvidia-graphics-drivers-331 package in Ubuntu: Incomplete Bug description: Ubuntu 14.10 has random freezes and lock ups while using NVIDIA 331.113. WORKAROUND: Use nouveau. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-28-generic 3.16.0-28.38 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afan 9511 F pulseaudio /dev/snd/controlC0: afan 9511 F pulseaudio CurrentDesktop: KDE Date: Wed Dec 24 16:49:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-23 (1 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=31ffafeb-d84a-4173-81a4-99a3bde628f3 ro quiet splash rcutree.rcu_idle_gp_delay=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.21 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.53 dmi.chassis.asset.tag: USH446L1YV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.21:bd08/13/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.53:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1405489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420430] Re: Disconnect menu item in network-manager taskbar tool is inactive when connected to network
@marek-wrzosek: Just downgrading network-manager alone did it for me. thank you! -- 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/1420430 Title: Disconnect menu item in network-manager taskbar tool is inactive when connected to network Status in network-manager-applet package in Ubuntu: Confirmed Bug description: When connected to a network (via ethernet), I am not able to disconnect using the network menu in the top taskbar. The Disconnect menu item is not highlighted. The Connection Name is highlighted, but I don't need to click it because I'm already connected to it. If I click the Connection Name, it connects again, but still does not highlight the Disconnect option. So to disconnect, I have to go to System Settings - Network, and click on the toggle. That does work. It's just the taskbar connection manager that is malfunctioning. I have tried restarting, and the problem persists. This happened after I updated software this morning using Update Manager. I installed the updated Unity Greeter that puts network status on the login screen and updates wifi and mobile. I am running 12.04 LTS and Unity2d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1420430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420430] Re: Disconnect menu item in network-manager taskbar tool is inactive when connected to network
.. on Ubuntu 12.04.5 using gnome-session-fallback -- 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/1420430 Title: Disconnect menu item in network-manager taskbar tool is inactive when connected to network Status in network-manager-applet package in Ubuntu: Confirmed Bug description: When connected to a network (via ethernet), I am not able to disconnect using the network menu in the top taskbar. The Disconnect menu item is not highlighted. The Connection Name is highlighted, but I don't need to click it because I'm already connected to it. If I click the Connection Name, it connects again, but still does not highlight the Disconnect option. So to disconnect, I have to go to System Settings - Network, and click on the toggle. That does work. It's just the taskbar connection manager that is malfunctioning. I have tried restarting, and the problem persists. This happened after I updated software this morning using Update Manager. I installed the updated Unity Greeter that puts network status on the login screen and updates wifi and mobile. I am running 12.04 LTS and Unity2d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1420430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363798] Re: Evolution-EWS 3.12 causes Evolution to hang Utopic
I'd posted this issue to another thread which then pointed me back here. I applied the debian ews and things worked. Just did an update and a new evolution got installed. The hang returned. Removed the debian version of ews and reinstalled the ubuntu version. Still hangs. If I run from the command line I get the message about registering the CamelEWSStore. here is the output: ** (evolution:4243): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Ib3KI5k2aG: Connection refused (evolution:4243): GLib-GObject-WARNING **: The property GtkSettings:gtk- button-images is deprecated and shouldn't be used anymore. It will be removed in a future version. (evolution:4243): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (evolution-alarm-notify:4265): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Ib3KI5k2aG: Connection refused (evolution:4243): camel-WARNING **: Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8126 (evolution:4243): GLib-GObject-WARNING **: The property GtkSettings:gtk- menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version. (evolution:4243): GLib-GObject-WARNING **: cannot register existing type 'CamelEwsStore' (evolution:4243): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed (evolution:4243): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed (evolution:4243): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed (evolution:4243): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1363798 Title: Evolution-EWS 3.12 causes Evolution to hang Utopic Status in “evolution” package in Ubuntu: Confirmed Bug description: Fresh install, add a mail account and nothing happens after. Calendars will show up in Gnome but evolution just sits there with no UI ever popping up. Can wait hours, will not crash or do anything. If you try to open another instance you get a pop up saying it's already running. Fresh install of UbuntuGnome both with updates turned on and off. Both times, same results. Evolution-EWS is what causes it, if you remove it it opens just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1363798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363798] Re: Evolution-EWS 3.12 causes Evolution to hang Utopic
small update. reinstall debian version and it works again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1363798 Title: Evolution-EWS 3.12 causes Evolution to hang Utopic Status in “evolution” package in Ubuntu: Confirmed Bug description: Fresh install, add a mail account and nothing happens after. Calendars will show up in Gnome but evolution just sits there with no UI ever popping up. Can wait hours, will not crash or do anything. If you try to open another instance you get a pop up saying it's already running. Fresh install of UbuntuGnome both with updates turned on and off. Both times, same results. Evolution-EWS is what causes it, if you remove it it opens just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1363798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1284826] Re: LightDM fails to start randomly
After upgrading to Ubuntu 14.04 update-manager asked me if I wanted to keep my old lightdm.conf or replace it with a new one, and becuase I did had issues with lightDM, I did choose to replace it, since then this issue hasen't appeared anymore and LightDM seems to work fine. :-) So it appears that the bug / issue is FIXED in Ubuntu 14.04 So if anyone else is affected by this issue an upgrade to Thrusty seems to solve it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1284826 Title: LightDM fails to start randomly Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: New Status in “unity-greeter” package in Ubuntu: New Bug description: Sometimes, then I boot up my computer LightDM fails to start, and I just get a a black screen. I then have to press CTRL+ALT+F1 to get to a TTY (terminal) and run sudo service lightdm restart then lightdm starts up just fine, this happens quite rarely. I have had lots of people looking at my logfiles on the official #ubuntu channel on IRC, but none have been able to give me a working solution I also posted my issue on Ubuntuforums, no one seems a to have any ideas. I have tried the following without any result: * Tried to reconfigure LightDM and unity-greeter with sudo dpkg-reconfigure lightdm and sudo dpkg-reconfigure unity-greeter. *Updating my Nvidia drivers with this ppa: http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu *Asked on #Ubuntu (offiicial Ubuntu channel of course) and got the advices above. * Tried Googing around a bit, and searched this forum as well of course. I uploaded my logfiles here: Lightdm.log http://paste.ubuntu.com/6803029/ x-0.log http://paste.ubuntu.com/6803033/ x-0-greeter.log http://paste.ubuntu.com/6803040/ Xorg.0.log http://paste.ubuntu.com/6803176/y vi Here is some older logfiles as well. lightdm.log.old http://paste.ubuntu.com/6803030/ x-0.log.old http://paste.ubuntu.com/6803035/ x-0-greeter.log.old http://paste.ubuntu.com/6803040/ Xorg.0.log.old http://paste.ubuntu.com/6803185/ Just tell me if you need more logfiles :-) I'm using Ubuntu 13.10 (upgraded version) This issue was also present on Ubuntu 12.10 (fresh install). Link to the Ubuntu thread: http://ubuntuforums.org/showthread.php?t=2201247 Kind regards Free User To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1284826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287472] Re: compiz unnecessarily shrinks new windows
Hrmpf, it didn't link to the other bugs... Likely related bugs: bug #1204307, bug #1217286 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1287472 Title: compiz unnecessarily shrinks new windows Status in Compiz: In Progress Status in “compiz” package in Ubuntu: In Progress Bug description: Ubuntu 14.04 Trusty, compiz 1:0.9.11+14.04.20140303-0ubuntu1. The fix for bug 1282304, just released, has introduced the following regression. Problem: All new non-fullscreen windows are now shrunk by the decoration size. This produces gnome-terminals of 79 columns by 22 rows, and applications that remember their window size when closed shrink further each time. Expected behaviour: Windows should not be resized unless they exceed the viewport size. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1287472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287472] Re: compiz unnecessarily shrinks new windows
I believe this bug affects me as well, with XFCE4.10 as the DE on Ubuntu 13.10. Whenever I minimize to tray/iconify a window and then restore from tray, the size of the window will shrink by the size of its decoration and title bar. Somehow sounds to me like exactly what's happening in this bug report. I frequently minimize-to-tray windows such as messengers or mail clients and calendars which makes this issue very annoying. Likely related are the bugs #1204307 and #1217286 where windows grow by the size of their decoration upon compiz restart. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1287472 Title: compiz unnecessarily shrinks new windows Status in Compiz: In Progress Status in “compiz” package in Ubuntu: In Progress Bug description: Ubuntu 14.04 Trusty, compiz 1:0.9.11+14.04.20140303-0ubuntu1. The fix for bug 1282304, just released, has introduced the following regression. Problem: All new non-fullscreen windows are now shrunk by the decoration size. This produces gnome-terminals of 79 columns by 22 rows, and applications that remember their window size when closed shrink further each time. Expected behaviour: Windows should not be resized unless they exceed the viewport size. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1287472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282305] Re: Repeatedly undecorating and redecorating a window shrinks it vertically
Adam, are you sure that the window only gets shrunk vertically? Could it be that it gets shrunk horizontally, as well, but only to a rather small degree (as the window borders left, right and bottom are only a few or in some themes even 0 pixels)? It could have to do with the size of the window decoration, as you noted in your linked bug report. Then of course it would be way more prominent in regards to changes to the vertical window size with a usual title bar size of 24 or so pixels. In that case, several other bugs might be related to this issue, as well: bug #1204307, bug #1287472 and others -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1282305 Title: Repeatedly undecorating and redecorating a window shrinks it vertically Status in Compiz: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Bug description: When you repeatedly undecorate and redecorate a window with the new compiz, it shrinks vertically on each iteration by a title-bar's height. Reproducible in totem or mplayer by loading a movie and hitting f repeatedly to swap fullscreen and window mode over and over. You'll see it shrink veritcally each time until all you have left is a title bar in mplayer's case, or some minimum window size is reached, in totem's case. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1282305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259423] Re: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
Christopher M. Penalver, Thank you for your response. I believe I have already done what you asked when I ran the command ubuntu-bug xorg and uploaded the file here https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/+attachment/3926455/+files/apport.xorg.u992bm.apport as seen in comment #1 ( https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/comments/1 ) Let me know if I have mis-understood your comment. When running this command I can only do so in text mode ans so saved the file and attached it to this bug report. -- 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/1259423 Title: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 Status in “xorg” package in Ubuntu: Incomplete Bug description: As requested by Christopher M. Penalver, opening a separate bug for this hardware configuration as a possible duplicate of Bug #1069199 Description: After installing ATI proprietary drivers for my Radeon video card, Unity or GNOME ( I tried both) don't start anymore. LightDM shows up, and I'm able to log in, but after logging in the screen goes black, pauses and then I'm presented with the lightDM login screen again. Xserver logs indicate that the driver fglrx does not load. To duplicate: 1) Download http://www2.ati.com/drivers/legacy/amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.zip Note: Catalyst 13.1 is the version AMD recommends for Mobility Radeon HD 3650 2) sudo sh ./amd-driver-installer-catalyst-13.1-legacy- linux-x86.x86_64.run --buildpkg Ubuntu/saucy 3) sudo dpkg -i *.deb 4) sudo aticonfig --initial -f (have also tried various combinations of this including --xinerama=[on|off] ) 5) reboot and then try to login Reverting to the opensource version gets things working again E.g. To get back to things working I have to run $sudo dpkg --purge fglrx fglrx-amdcccle fglrx-dev sudo apt-get install xserver-xorg-video-ati xserver-xorg-video-radeon ProblemType: Bug ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: fglrx, 8.970: added XorgLog: [63.002] X.Org X Server 1.14.3 Release Date: 2013-09-12 [63.002] X Protocol Version 11, Revision 0 [63.002] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu [63.002] Current Operating System: Linux aodius 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 [63.002] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 [63.002] Build Date: 15 October 2013 09:23:37AM [63.002] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) ... [63.010] (II) LoadModule: fglrx [63.010] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [63.025] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [63.025] (II) UnloadModule: fglrx [63.025] (II) Unloading fglrx [63.025] (EE) Failed to load module fglrx (loader failed, 7) ... [63.025] (II) LoadModule: fglrx [63.026] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [63.040] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [63.040] (II) UnloadModule: fglrx [63.040] (II) Unloading fglrx [63.040] (EE) Failed to load module fglrx (loader failed, 7) ... xserver.errors: Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension Failed to load module fglrx (loader failed, 7) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension Failed to load module fglrx (loader failed, 7) open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. GLX error: Can not get required
[Desktop-packages] [Bug 1259709] [NEW] Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
Public bug reported: This is a duplicate of bug #1259423. It was created automatically as part of the would you like to report this problem question hopefully answering request https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/comments/2 ProblemType: Package DistroRelease: Ubuntu 13.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSBuildLog: DKMS make.log for fglrx-8.970 for kernel 3.11.0-14-generic (x86_64) Mon Dec 9 23:28:30 CST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.11.0-14-generic/build/include not found or incomplete file: /lib/modules/3.11.0-14-generic/build/include/linux/version.h DKMSKernelVersion: 3.11.0-14-generic Date: Mon Dec 9 23:28:34 2013 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3604] InstallationDate: Installed on 2013-02-18 (295 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8530w MarkForUpload: True PackageVersion: (not installed) PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx (not installed): fglrx kernel module failed to build UpgradeStatus: Upgraded to saucy on 2013-10-18 (53 days ago) dmi.bios.date: 12/08/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDV Ver. F.20 dmi.board.name: 30E7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.27 dmi.chassis.asset.tag: USH91201DK dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.20:bd12/08/2011:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.20:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8530w dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Dec 10 15:34:26 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 xserver.video_driver: radeon ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1259709 Title: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 Status in “fglrx-installer” package in Ubuntu: New Bug description: This is a duplicate of bug #1259423. It was created automatically as part of the would you like to report this problem question hopefully answering request https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1259423/comments/2 ProblemType: Package DistroRelease: Ubuntu 13.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSBuildLog: DKMS make.log for fglrx-8.970 for kernel 3.11.0-14-generic (x86_64) Mon Dec 9 23:28:30 CST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.11.0-14-generic/build/include not found or incomplete file: /lib/modules/3.11.0-14-generic/build/include/linux/version.h DKMSKernelVersion: 3.11.0-14-generic Date: Mon Dec 9 23:28:34 2013 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu
[Desktop-packages] [Bug 1259423] Re: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
Hi, I restored back to opensource drivers and on login it asked me to report a bug with fglrx. I did so and it created this bug #1259709 https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1259709 My apologies in advance, if this was done in error. -- 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/1259423 Title: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 Status in “xorg” package in Ubuntu: Incomplete Bug description: As requested by Christopher M. Penalver, opening a separate bug for this hardware configuration as a possible duplicate of Bug #1069199 Description: After installing ATI proprietary drivers for my Radeon video card, Unity or GNOME ( I tried both) don't start anymore. LightDM shows up, and I'm able to log in, but after logging in the screen goes black, pauses and then I'm presented with the lightDM login screen again. Xserver logs indicate that the driver fglrx does not load. To duplicate: 1) Download http://www2.ati.com/drivers/legacy/amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.zip Note: Catalyst 13.1 is the version AMD recommends for Mobility Radeon HD 3650 2) sudo sh ./amd-driver-installer-catalyst-13.1-legacy- linux-x86.x86_64.run --buildpkg Ubuntu/saucy 3) sudo dpkg -i *.deb 4) sudo aticonfig --initial -f (have also tried various combinations of this including --xinerama=[on|off] ) 5) reboot and then try to login Reverting to the opensource version gets things working again E.g. To get back to things working I have to run $sudo dpkg --purge fglrx fglrx-amdcccle fglrx-dev sudo apt-get install xserver-xorg-video-ati xserver-xorg-video-radeon ProblemType: Bug ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: fglrx, 8.970: added XorgLog: [63.002] X.Org X Server 1.14.3 Release Date: 2013-09-12 [63.002] X Protocol Version 11, Revision 0 [63.002] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu [63.002] Current Operating System: Linux aodius 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 [63.002] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 [63.002] Build Date: 15 October 2013 09:23:37AM [63.002] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) ... [63.010] (II) LoadModule: fglrx [63.010] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [63.025] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [63.025] (II) UnloadModule: fglrx [63.025] (II) Unloading fglrx [63.025] (EE) Failed to load module fglrx (loader failed, 7) ... [63.025] (II) LoadModule: fglrx [63.026] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [63.040] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [63.040] (II) UnloadModule: fglrx [63.040] (II) Unloading fglrx [63.040] (EE) Failed to load module fglrx (loader failed, 7) ... xserver.errors: Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension Failed to load module fglrx (loader failed, 7) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension Failed to load module fglrx (loader failed, 7) open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. GLX error: Can not get required symbols. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: display edid version 1.3 display manufacturer AUO display model 197b display serial no. 0 product id
[Desktop-packages] [Bug 1259423] [NEW] Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
Public bug reported: As requested by Christopher M. Penalver, opening a separate bug for this hardware configuration as a possible duplicate of Bug #1069199 Description: After installing ATI proprietary drivers for my Radeon video card, Unity or GNOME ( I tried both) don't start anymore. LightDM shows up, and I'm able to log in, but after logging in the screen goes black, pauses and then I'm presented with the lightDM login screen again. Xserver logs indicate that the driver fglrx does not load. Reverting to the opensource version gets things working again E.g. To get back to things working I have to run $sudo dpkg --purge fglrx fglrx-amdcccle fglrx-dev sudo apt-get install xserver-xorg-video-ati xserver-xorg-video-radeon ProblemType: Bug ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: fglrx, 8.970: added XorgLog: [63.002] X.Org X Server 1.14.3 Release Date: 2013-09-12 [63.002] X Protocol Version 11, Revision 0 [63.002] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu [63.002] Current Operating System: Linux aodius 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 [63.002] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 [63.002] Build Date: 15 October 2013 09:23:37AM [63.002] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) ... [63.010] (II) LoadModule: fglrx [63.010] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [63.025] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [63.025] (II) UnloadModule: fglrx [63.025] (II) Unloading fglrx [63.025] (EE) Failed to load module fglrx (loader failed, 7) ... [63.025] (II) LoadModule: fglrx [63.026] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [63.040] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [63.040] (II) UnloadModule: fglrx [63.040] (II) Unloading fglrx [63.040] (EE) Failed to load module fglrx (loader failed, 7) ... xserver.errors: Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension Failed to load module fglrx (loader failed, 7) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension Failed to load module fglrx (loader failed, 7) open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. GLX error: Can not get required symbols. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: display edid version 1.3 display manufacturer AUO display model 197b display serial no. 0 product id6523 size horizontal 331 mm size max horizontal33 cm size max vertical21 cm size vertical 207 mm vendor AUO xserver.version: 2:1.14.3-3ubuntu2 ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Attachment added: Apport Report https://bugs.launchpad.net/bugs/1259423/+attachment/3926455/+files/apport.xorg.u992bm.apport ** Summary changed: - Unity does not start after installing fglrx x64 drivers Mobility Radeon Mobile HD 3650 + Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1259423 Title: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650 Status in “fglrx-installer-updates” package in Ubuntu: New Bug description: As requested by Christopher M. Penalver, opening a separate bug for this
[Desktop-packages] [Bug 1259423] Re: Unity does not start after installing fglrx x64 drivers Mobility Radeon HD 3650
** Description changed: As requested by Christopher M. Penalver, opening a separate bug for this hardware configuration as a possible duplicate of Bug #1069199 Description: - After installing ATI proprietary drivers for my Radeon video card, Unity or GNOME ( I tried both) don't start anymore. LightDM shows up, and I'm able to log in, but after logging in the screen goes black, pauses and then I'm presented with the lightDM login screen again. + After installing ATI proprietary drivers for my Radeon video card, Unity or GNOME ( I tried both) don't start anymore. LightDM shows up, and I'm able to log in, but after logging in the screen goes black, pauses and then I'm presented with the lightDM login screen again. Xserver logs indicate that the driver fglrx does not load. + + To duplicate: + 1) Download http://www2.ati.com/drivers/legacy/amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.zip + + Note: Catalyst 13.1 is the version AMD recommends for Mobility Radeon HD + 3650 + + 2) sudo sh ./amd-driver-installer-catalyst-13.1-legacy- + linux-x86.x86_64.run --buildpkg Ubuntu/saucy + + 3) sudo dpkg -i *.deb + + 4) reboot and then try to login + Reverting to the opensource version gets things working again E.g. To get back to things working I have to run $sudo dpkg --purge fglrx fglrx-amdcccle fglrx-dev sudo apt-get install xserver-xorg-video-ati xserver-xorg-video-radeon ProblemType: Bug ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-18 08:24:06,128 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: fglrx, 8.970: added XorgLog: - [63.002] - X.Org X Server 1.14.3 - Release Date: 2013-09-12 - [63.002] X Protocol Version 11, Revision 0 - [63.002] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu - [63.002] Current Operating System: Linux aodius 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 - [63.002] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 - [63.002] Build Date: 15 October 2013 09:23:37AM - [63.002] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) + [63.002] + X.Org X Server 1.14.3 + Release Date: 2013-09-12 + [63.002] X Protocol Version 11, Revision 0 + [63.002] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu + [63.002] Current Operating System: Linux aodius 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 + [63.002] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=a153e9f7-6ba9-4e43-85ae-951f1d3b7e38 ro quiet splash vt.handoff=7 + [63.002] Build Date: 15 October 2013 09:23:37AM + [63.002] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) ... - [63.010] (II) LoadModule: fglrx - [63.010] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so - [63.025] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn + [63.010] (II) LoadModule: fglrx + [63.010] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so + [63.025] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension - [63.025] (II) UnloadModule: fglrx - [63.025] (II) Unloading fglrx - [63.025] (EE) Failed to load module fglrx (loader failed, 7) + [63.025] (II) UnloadModule: fglrx + [63.025] (II) Unloading fglrx + [63.025] (EE) Failed to load module fglrx (loader failed, 7) ... - [63.025] (II) LoadModule: fglrx - [63.026] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so - [63.040] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn + [63.025] (II) LoadModule: fglrx + [63.026] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so + [63.040] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gn u/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension - [63.040] (II) UnloadModule: fglrx - [63.040] (II) Unloading fglrx - [63.040] (EE) Failed to load module fglrx (loader failed, 7) +
[Desktop-packages] [Bug 1069199] Re: 1002:682f Unity does not start after installing fglrx-updates Radeon HD 7700M Series
*** This bug is a duplicate of bug 1068404 *** https://bugs.launchpad.net/bugs/1068404 I think the duplicate status is wrong. I think this is NOT a duplicate of bug #1068404 because **this** bug has the error: [ 593.127] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra- modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg- tmp/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension or in other words it can't load the fglrx driver while bug #1068404 does NOT have that issue. So to be clear - this bug relates to the module fglrx driver is NOT loading which results in X crashing. The other bug looks like it loads the module fglrx but X crashes for other reasons. Seems like a completely different root cause therefore should be a different bug. I am also affected by this bug #1069199 and am running DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION=Ubuntu 13.10 I downloaded and built sudo sh ./amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run --buildpkg Ubuntu/saucy After doing the install and rebooting I get EXACTLY the same results and have the same error messages as the original bug reporter for this bug when I install the fglrx proprietary drivers. I was hoping to load the AMD drivers because I wanted to get sound out of the HDMI port. I'm running with the following hardware on an HP 8530w. The opensource versions run perfectly for video with both the VGA and HDMI ports, but I can't get sound out of the HDMI port too and read that the only solution is to upgrade to the proprietary fglrx drivers. $ lspci | grep -i Radeon 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV635 HDMI Audio [Radeon HD 3600 Series] Symptons: 1) lightdm prompt appears 2) Login succeeds 3) screen goes blank and then login screen appears again. The following (I think relevant) error messages appear in Xorg.0.log and mark this as different than the other bug. [ 699.570] (II) LoadModule: fglrx [ 699.570] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so [ 699.585] (EE) Failed to load /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension [ 699.585] (II) UnloadModule: fglrx [ 699.585] (II) Unloading fglrx [ 699.585] (EE) Failed to load module fglrx (loader failed, 7) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1069199 Title: 1002:682f Unity does not start after installing fglrx-updates Radeon HD 7700M Series Status in AMD fglrx video driver: Confirmed Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Bug description: After installing ATI proprietary drivers for my Radeon video card, Unity doesn't start anymore. LightDM shows up, and I'm able to log in, but Unity doesn't load. Obs: The same occurs when installing fglrx package (if I choose it, instead of fglrx-updates). Potential duplicate of bug https://bugs.launchpad.net/ubuntu/+source /xserver-xorg-video-intel/+bug/1068404 . WORKAROUND: Removing the package fixes the problem, getting back to the opensource driver (ati). WORKAROUND: https://launchpad.net/~andrikos/+archive/ppa/+packages?field.name_filter=field.status_filter=publishedfield.series_filter=quantal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fglrx-updates 2:9.000-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sat Oct 20 17:13:10 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: fglrx-installer-updates UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emarquezani 2523 F pulseaudio /dev/snd/pcmC0D0p: emarquezani 2523 F...m pulseaudio DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=ea9a06e8-a07c-4fa4-aad5-00b0c111023e InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 7520 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=638c2b77-1853-48c0-8200-e446faedec13 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux
[Desktop-packages] [Bug 1233432] Re: session-startup-script not passed any environment
*** This bug is a duplicate of bug 1245957 *** https://bugs.launchpad.net/bugs/1245957 ** This bug has been marked a duplicate of bug 1245957 session-setup-script doesn't know the username -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1233432 Title: session-startup-script not passed any environment Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: New Bug description: In raring, lightdm successfully passed environment variables (specifically $USER and $HOME) relating to the user logging in to a session-startup-script specified in /etc/lightdm/lightdm.conf. In saucy, the session-startup-script gets a very cut down environment, with $HOME = / and $USER blank. This means you can't do things like mounting home directories on login, or anything that depends on knowing which user is logging in. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.17-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Sep 30 23:51:56 2013 InstallationDate: Installed on 2013-09-24 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1233432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043621] Re: [M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
I followed the instructions on the page selecting the quantal-all deb
and attempted to install. This was the result at the end of the process
...
depmod
DKMS: install completed.
Building initial module for 3.6.0-030600-generic
Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch. This indicates that it should not be built.
dpkg: error processing oem-audio-hda-daily-dkms (--configure):
subprocess installed post-installation script returned error exit status 9
Errors were encountered while processing:
oem-audio-hda-daily-dkms
On the page it lists that it was only built for i386, I tried to
installed ia32-libs and it spits back the same message. Are there any
other steps I can do to to fix this?
--
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/1043621
Title:
[M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
Originally there was no sound, I modified the file /etc/modprobe.d
/alsa-base.conf adding the following: snd-hda-intel index=0
model=intel and now I have sound (maybe that model is not the best
option), but when I plug the headphones there is sound from the
speakers and the headphones. I installed gnome alsa mixer but it
doesn't open. thanks
using ubuntu 12.04.1 LTS
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gerardo1836 F pulseaudio
/dev/snd/pcmC0D0p: gerardo1836 F...m pulseaudio
Card0.Amixer.info:
Error: command ['amixer', '-c', '0', 'info'] failed with exit code 1:
amixer: Mixer load hw:0 error: Invalid argument
Card hw:0 'PCH'/'HDA Intel PCH at 0xd271 irq 48'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:11020011,1028057b,00100918
HDA:80862806,1028057b,0010'
Controls : 27
Card0.Amixer.values: Error: command ['amixer', '-c', '0'] failed with exit
code 1: amixer: Mixer hw:0 load error: Invalid argument
Date: Wed Aug 29 21:42:38 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No auto-mute between outputs
Symptom_amixerStderr: a m i x e r : M i x e r h w : P C H l o a d e r
r o r : I n v a l i d a r g u m e n t
Title: [M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Alienware
dmi.bios.version: A02
dmi.board.name: M17xR4
dmi.board.vendor: Alienware
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A02
dmi.modalias:
dmi:bvnAlienware:bvrA02:bd02/08/2012:svnAlienware:pnM17xR4:pvrA02:rvnAlienware:rnM17xR4:rvrA02:cvnAlienware:ct8:cvrA02:
dmi.product.name: M17xR4
dmi.product.version: A02
dmi.sys.vendor: Alienware
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-24T17:11:29.363163
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1043621/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043621] Re: [M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
Ok I saved the patch file to the location /sound/pci/hda/ based on the
page that I see. Do I need to recompile the kernel/alsa for it to be
used? And if so, what are the commands/ switches I need to use?
--
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/1043621
Title:
[M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
Originally there was no sound, I modified the file /etc/modprobe.d
/alsa-base.conf adding the following: snd-hda-intel index=0
model=intel and now I have sound (maybe that model is not the best
option), but when I plug the headphones there is sound from the
speakers and the headphones. I installed gnome alsa mixer but it
doesn't open. thanks
using ubuntu 12.04.1 LTS
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gerardo1836 F pulseaudio
/dev/snd/pcmC0D0p: gerardo1836 F...m pulseaudio
Card0.Amixer.info:
Error: command ['amixer', '-c', '0', 'info'] failed with exit code 1:
amixer: Mixer load hw:0 error: Invalid argument
Card hw:0 'PCH'/'HDA Intel PCH at 0xd271 irq 48'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:11020011,1028057b,00100918
HDA:80862806,1028057b,0010'
Controls : 27
Card0.Amixer.values: Error: command ['amixer', '-c', '0'] failed with exit
code 1: amixer: Mixer hw:0 load error: Invalid argument
Date: Wed Aug 29 21:42:38 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No auto-mute between outputs
Symptom_amixerStderr: a m i x e r : M i x e r h w : P C H l o a d e r
r o r : I n v a l i d a r g u m e n t
Title: [M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Alienware
dmi.bios.version: A02
dmi.board.name: M17xR4
dmi.board.vendor: Alienware
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A02
dmi.modalias:
dmi:bvnAlienware:bvrA02:bd02/08/2012:svnAlienware:pnM17xR4:pvrA02:rvnAlienware:rnM17xR4:rvrA02:cvnAlienware:ct8:cvrA02:
dmi.product.name: M17xR4
dmi.product.version: A02
dmi.sys.vendor: Alienware
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-24T17:11:29.363163
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1043621/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043621] Re: [M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
Hi, I'm running into the same issue, first on 13.04 now 12.10. I'm
making this a dual boot with win7 and this is my nth attempt to get
ubuntu working. Very similar, if not same machine. I'm not sure what
the link is for, is that a replacement for the driver. If there are any
commands I need to run, let me know. I know in the alsamixer it's
possible to mute the speaker, but when I unplug and replug my
headphones, alsamixer shows it's still muted but sound comes out of both
speakers and headphones.
I've tried adding this line to alsa-base.conf
options snd-hda-intel model=auto probe_mask=1
and also following this set of instructions
http://askubuntu.com/questions/276170/speakers-and-headphones-at-the-same-time-when-using-a-dv6-2170
Can you give me any pointers on how to fix it without muting the
speakers each time?
--
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/1043621
Title:
[M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
Originally there was no sound, I modified the file /etc/modprobe.d
/alsa-base.conf adding the following: snd-hda-intel index=0
model=intel and now I have sound (maybe that model is not the best
option), but when I plug the headphones there is sound from the
speakers and the headphones. I installed gnome alsa mixer but it
doesn't open. thanks
using ubuntu 12.04.1 LTS
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gerardo1836 F pulseaudio
/dev/snd/pcmC0D0p: gerardo1836 F...m pulseaudio
Card0.Amixer.info:
Error: command ['amixer', '-c', '0', 'info'] failed with exit code 1:
amixer: Mixer load hw:0 error: Invalid argument
Card hw:0 'PCH'/'HDA Intel PCH at 0xd271 irq 48'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:11020011,1028057b,00100918
HDA:80862806,1028057b,0010'
Controls : 27
Card0.Amixer.values: Error: command ['amixer', '-c', '0'] failed with exit
code 1: amixer: Mixer hw:0 load error: Invalid argument
Date: Wed Aug 29 21:42:38 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No auto-mute between outputs
Symptom_amixerStderr: a m i x e r : M i x e r h w : P C H l o a d e r
r o r : I n v a l i d a r g u m e n t
Title: [M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Alienware
dmi.bios.version: A02
dmi.board.name: M17xR4
dmi.board.vendor: Alienware
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A02
dmi.modalias:
dmi:bvnAlienware:bvrA02:bd02/08/2012:svnAlienware:pnM17xR4:pvrA02:rvnAlienware:rnM17xR4:rvrA02:cvnAlienware:ct8:cvrA02:
dmi.product.name: M17xR4
dmi.product.version: A02
dmi.sys.vendor: Alienware
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-24T17:11:29.363163
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1043621/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097096] Re: can't scan more after scan all from document feeder
I can confirm that this fixed the issue for me. Seems like the application is faster too. Nice work. Now running: simple-scan 3.4.3-0ubuntu1. Still running Ubuntu 12.04 LTS. I do not see where I can change the tag from from verification-needed to verification-done. Perhaps I do not have rights to add/change tags on launchpad.net? But I can confirm that it fixed the issue on my system. ** Tags added: verification-done ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1097096 Title: can't scan more after scan all from document feeder Status in Simple Scan: Fix Released Status in “simple-scan” package in Ubuntu: Fix Released Status in “simple-scan” source package in Precise: Fix Committed Bug description: Steps to reproduce: * scan a single page * scan another page * scan all from feeder * scan another single page * scan all from feeder again Expected results: * all pages are scanned in correctly Current results: * can't scan anything more after scanning from the document feeder Attached please find a debug log (stripped from extraneous sane_read - GOOD lines). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: simple-scan 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Tue Jan 8 01:51:18 2013 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.12.6-3ubuntu4 hpoj N/A MachineType: Dell Inc. Latitude E6420 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic root=/dev/mapper/username--laptop-ubuntu--root ro rootflags=subvol=@ splash quiet vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.04 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.13.3-1 hpoj N/A MachineType: Dell Inc. Latitude E6420 MarkForUpload: True NonfreeKernelModules: wl nvidia Package: simple-scan 3.6.0-2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-7-generic root=/dev/mapper/username--laptop-ubuntu--root ro rootflags=subvol=@ splash quiet ProcVersionSignature: Ubuntu 3.8.0-7.16-generic 3.8.0 Tags: raring Uname: Linux 3.8.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sbuild sudo vboxusers dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.04 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.13.3-1 hpoj N/A MachineType: Dell Inc. Latitude E6420 MarkForUpload: True NonfreeKernelModules: wl nvidia Package: simple-scan 3.6.0-2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-7-generic root=/dev/mapper/username--laptop-ubuntu--root ro rootflags=subvol=@ splash quiet ProcVersionSignature: Ubuntu 3.8.0-7.16-generic 3.8.0 Tags: raring Uname: Linux 3.8.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sbuild sudo vboxusers dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1097096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097096] Re: can't scan more after scan all from document feeder
I think I found how to change the tag from from verification-needed to verification-done and did so. If I did it in error - my apologies in advance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1097096 Title: can't scan more after scan all from document feeder Status in Simple Scan: Fix Released Status in “simple-scan” package in Ubuntu: Fix Released Status in “simple-scan” source package in Precise: Fix Committed Bug description: Steps to reproduce: * scan a single page * scan another page * scan all from feeder * scan another single page * scan all from feeder again Expected results: * all pages are scanned in correctly Current results: * can't scan anything more after scanning from the document feeder Attached please find a debug log (stripped from extraneous sane_read - GOOD lines). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: simple-scan 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Tue Jan 8 01:51:18 2013 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.12.6-3ubuntu4 hpoj N/A MachineType: Dell Inc. Latitude E6420 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic root=/dev/mapper/username--laptop-ubuntu--root ro rootflags=subvol=@ splash quiet vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.04 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.13.3-1 hpoj N/A MachineType: Dell Inc. Latitude E6420 MarkForUpload: True NonfreeKernelModules: wl nvidia Package: simple-scan 3.6.0-2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-7-generic root=/dev/mapper/username--laptop-ubuntu--root ro rootflags=subvol=@ splash quiet ProcVersionSignature: Ubuntu 3.8.0-7.16-generic 3.8.0 Tags: raring Uname: Linux 3.8.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sbuild sudo vboxusers dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.04 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.13.3-1 hpoj N/A MachineType: Dell Inc. Latitude E6420 MarkForUpload: True NonfreeKernelModules: wl nvidia Package: simple-scan 3.6.0-2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-7-generic root=/dev/mapper/username--laptop-ubuntu--root ro rootflags=subvol=@ splash quiet ProcVersionSignature: Ubuntu 3.8.0-7.16-generic 3.8.0 Tags: raring Uname: Linux 3.8.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sbuild sudo vboxusers dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1097096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097096] Re: can't scan more after scan all from document feeder
Just to note: the version I'm now running is simple-scan 3.4.1-0ubuntu1.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1097096 Title: can't scan more after scan all from document feeder Status in “simple-scan” package in Ubuntu: Incomplete Bug description: Steps to reproduce: * scan a single page * scan another page * scan all from feeder * scan another single page * scan all from feeder again Expected results: * all pages are scanned in correctly Current results: * can't scan anything more after scanning from the document feeder Attached please find a debug log (stripped from extraneous sane_read - GOOD lines). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: simple-scan 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Tue Jan 8 01:51:18 2013 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.12.6-3ubuntu4 hpoj N/A MachineType: Dell Inc. Latitude E6420 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic root=/dev/mapper/username--laptop-ubuntu--root ro rootflags=subvol=@ splash quiet vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1097096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097096] Re: can't scan more after scan all from document feeder
After some apt-get upgrade to Ubuntu 12.04-LTS I now get this exact same problem with a Brother MFC-8660DN. I don't know which upgrade caused the problem or when it started, but with the original Ubuntu 12.04-LTS I was able to make multiple runs. It never had this problem before. I have to quit from simple scan and restart in order to scan more pages. The last lines of simple-scan.log are: [+53.78s] DEBUG: scanner.vala:818: sane_get_option_descriptor (12) [+53.78s] DEBUG: scanner.vala:480: sane_control_option (4, SANE_ACTION_SET_VALUE, Automatic Document Feeder) - (SANE_STATUS_GOOD, Automatic Document Feeder) [+53.78s] DEBUG: scanner.vala:480: sane_control_option (2, SANE_ACTION_SET_VALUE, True Gray) - (SANE_STATUS_GOOD, True Gray) [+53.78s] DEBUG: scanner.vala:422: sane_control_option (3, SANE_ACTION_SET_VALUE, 150) - (SANE_STATUS_GOOD, 150) [+53.78s] DEBUG: scanner.vala:462: sane_control_option (10, SANE_ACTION_SET_VALUE, 215.84) - (SANE_STATUS_GOOD, 215.880234) [+53.78s] DEBUG: scanner.vala:462: sane_control_option (11, SANE_ACTION_SET_VALUE, 355.51) - (SANE_STATUS_GOOD, 355.567444) [+53.78s] DEBUG: scanner.vala:1124: sane_start (page=0, pass=0) - SANE_STATUS_NO_DOCS As you can see the last line says SANE_STATUS_NO_DOCS so it's saying that there are no documents even though there are. Quitting and restarting simple-scan allows you to use the scanner again, but this defeats the goal of being able to scan several times (e.g. front and back of pages) and combining them into one saved document. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1097096 Title: can't scan more after scan all from document feeder Status in “simple-scan” package in Ubuntu: Incomplete Bug description: Steps to reproduce: * scan a single page * scan another page * scan all from feeder * scan another single page * scan all from feeder again Expected results: * all pages are scanned in correctly Current results: * can't scan anything more after scanning from the document feeder Attached please find a debug log (stripped from extraneous sane_read - GOOD lines). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: simple-scan 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Tue Jan 8 01:51:18 2013 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.12.6-3ubuntu4 hpoj N/A MachineType: Dell Inc. Latitude E6420 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic root=/dev/mapper/username--laptop-ubuntu--root ro rootflags=subvol=@ splash quiet vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1097096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 541472] Re: Menu icons should not be 16x16 px
I'm not 100% sure on this, but this might not be very easy to patch. If I remember correctly, icon sizes are read just once and never again. I think simply changing the constant would work for *new* icons, but wouldn't auto-resize the ones already rendered. It's worth mentioning that the GNOME HIG itself hardcodes icon sizes: http://developer.gnome.org/hig-book/3.5/icons-types.html.en so I wouldn't be surprised if implementing auto-resizing is not very easy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/541472 Title: Menu icons should not be 16x16 px Status in DBus Menu: Confirmed Status in Sound Menu: Confirmed Status in Libindicator: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: The messaging menu and system menu currently use GTK_ICON_SIZE_MENU for the size of their icons. Unfortunately, GTK_ICON_SIZE_MENU does not change when the system font size changes, and is apparently hard- coded inside GTK. There should be a signal when the font size changes, gnome-settings- daemon should update gtk-icon-sizes to reflect the new size, and menus should be redrawn automatically. http://developer.gnome.org/gtk3/stable/GtkSettings.html#GtkSettings --gtk-icon-sizes To manage notifications about this bug go to: https://bugs.launchpad.net/dbusmenu/+bug/541472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1015305] Re: lockup on resume after suspend on T420s
For me, this issue seems to have been fixed with NVidia's driver version 304.43. \o/ Still on Ubuntu 10.04.4 LTS x86_64, with Linux kernel version 2.6.38-13-generic, I suspended-to-ram and resumed my machine several times for the last week or so, and all works well. This just in case somebody else was waiting for good news before they tried NVidia's new upgrade. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1015305 Title: lockup on resume after suspend on T420s Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: Description: Ubuntu 12.04 LTS Release: 12.04 The laptop always locks up when trying to resume after suspend when X is running on the proprietary NVIDIA drivers. I installed Precise from scratch on a Thinkpad T420s with NVIDIA Optimus. The BIOS is configured to Discrete graphics, i.e. Optimus is turned off, and the NVIDIA video card is turned on, and it is the only card visible from Linux. After the installation, I added the proprietary NVIDIA drivers and rebooted. This gave me nvidia-current-updates 295.49-0ubuntu0.1 I then suspend the machine, either by closing the lid, hitting Fn+F4, selecting suspend from the system menu, or running pm-suspend. When I then resume the machine, either by hitting Fn or by opening the lid, the LCD backlight comes back on but remains black, and the machine freezes. After a while, the CPU fan hits max. I cannot SSH into the machine. There is a link light on the Ethernet, but no activity light. This problem persists also with other versions of the NVIDIA driver, such as nvidia-current 302.17-0ubuntu1~precise~xup1. The problem disappears if I switch to Integrated Graphics, and use the intel driver. I have found no obvious way to get at the syslog or Xorg log files to get an indication of what or how this locks up. Details on the packages I tried: nvidia-current-updates: Installed: (none) Candidate: 295.49-0ubuntu0.1 Version table: 295.49-0ubuntu0.1 0 500 http://no.archive.ubuntu.com/ubuntu/ precise-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 295.40-0ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ precise/restricted amd64 Packages nvidia-current: Installed: 302.17-0ubuntu1~precise~xup1 Candidate: 302.17-0ubuntu1~precise~xup1 Version table: *** 302.17-0ubuntu1~precise~xup1 0 500 http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 295.40-0ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ precise/restricted amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1015305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 779366]
Same bug on LibreOffice 3.5.0rc3 for Mac OS 10.6.8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/779366 Title: [Upstream] Font Nimbus Sans L squashed in Impress slideshow Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: Binary package hint: libreoffice 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.4.3-3ubuntu2 Candidate: 1:3.4.3-3ubuntu2 Version table: *** 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in Impress via the Terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/779366/+attachment/2119346/+files/fontbug.odp loimpress --nologo fontbug.odp is the text with Nimbus Sans L font looks in edit view as it does in slide show. 4) What happens instead is the font shows differently in slide show https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/779366/+attachment/2119348/+files/fontbug_slideshow.png versus edit mode https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/779366/+attachment/2119347/+files/fontbug_editview.png ORIGINAL REPORTER COMMENTS: Observed in amd64 Natty (LibreOffice); not present in amd64 Maverick (OpenOffice). To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/779366/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 841046] Re: GNOME3 misses an option to change the mouse pointer
So basic standards of Disability Accessibility are listed as Wish List? I note that a valid bug report on the same matter yesterday and listed as High priority has been down graded and linked to this bug report over six months ago! I am - well ..? See bug report https://bugs.launchpad.net/ubuntu/+source/gnome-themes- standard/+bug/964685 -- 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/841046 Title: GNOME3 misses an option to change the mouse pointer Status in GNOME Control Center: New Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: In the previous Ubuntu versions, it was possible to choose a mouse pointer to use with a theme. It also allowed you to set the mouse pointer size. I can no longer find this option in Ubuntu 11.10 (development branch). Version of gnome-control-center: 1:3.1.90-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/841046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 841046] Re: GNOME3 misses an option to change the mouse pointer
Rick - would it be possible to have Accessibility in general removed from The Wishlist? P^) -- 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/841046 Title: GNOME3 misses an option to change the mouse pointer Status in GNOME Control Center: New Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: In the previous Ubuntu versions, it was possible to choose a mouse pointer to use with a theme. It also allowed you to set the mouse pointer size. I can no longer find this option in Ubuntu 11.10 (development branch). Version of gnome-control-center: 1:3.1.90-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/841046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966549] [NEW] gnome-control-centre - missing accessability option to change cursor and cursor size
Public bug reported: Ubuntu Precise Development Branch. 12.04 Further to bug report #964685 - reference Missing Disability Accessibility to change cursors to high viability and change cursor size. basic high contrast cursors from dmz-cursor-theme. These appear to be installed in 12.04 under /usr/share/icons/foo/cursors - yet there is no apparent way to utilze them - or change the size should they be selected. Advised missing access and control is through gnome-control-center. Facility has been accessible in 10.04-11.10 through Desktop Right-click - themes - customise - pointer. Presently there is no access to cursors and or resize - compromising basic disability accessibility - live-CD and installed. Screen print to show expected behaviour-accesability in 10.04-11.11 in bug tracker at https://launchpadlibrarian.net/98503309/AcessibleMouse.png ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: access accessability cursors dmz-cursor-theme gnome-control-center universal -- 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/966549 Title: gnome-control-centre - missing accessability option to change cursor and cursor size Status in “gnome-control-center” package in Ubuntu: New Bug description: Ubuntu Precise Development Branch. 12.04 Further to bug report #964685 - reference Missing Disability Accessibility to change cursors to high viability and change cursor size. basic high contrast cursors from dmz-cursor-theme. These appear to be installed in 12.04 under /usr/share/icons/foo/cursors - yet there is no apparent way to utilze them - or change the size should they be selected. Advised missing access and control is through gnome-control-center. Facility has been accessible in 10.04-11.10 through Desktop Right- click - themes - customise - pointer. Presently there is no access to cursors and or resize - compromising basic disability accessibility - live-CD and installed. Screen print to show expected behaviour-accesability in 10.04-11.11 in bug tracker at https://launchpadlibrarian.net/98503309/AcessibleMouse.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/966549/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966524] Re: control center window is not manually resizeable
Correction to Alan above - I am advised that it affects all system specific and brand related windows from Live-cd start through to a completed installation and it's a compiz matter. I'm no expert - just taking what the experts say and reporting it as advised against the packages identified - not the content of the window affected. ! The Bug has multiple impacts at multiple locations across the OS - and not just one window control center. -- 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/966524 Title: control center window is not manually resizeable Status in “gnome-control-center” package in Ubuntu: New Bug description: Ubuntu Precise Development Branch. 12.04 Further to Bug report #964685 - I am advised that the following behaviour is caused by Compiz. 1. Start live cd - click desktop to change background to suitable colour. Facility to maximise window using Alt F8 has is greyed out - needs to re restored to meet accessibility standards - and should be working in the beta. This accessibility feature is present in 10.04.4 through to 11.10 (verified today) - and should still be present in 12.04. It should not have been removed or deprecated under Gnome shell/3 or Unity - or for testing purposes. Issue visible in screen print - attached. Issue affects multiple windows from Boot of live CD and through Install process and in installed system. Numerous people with visual and neurodiveristy disabilities need the ability to maximise these windows to allow concentration on single task with minimal image/background noise. Window sizes may be presented inline with branding guidelines - but they should retain accessibility feature for those who need it and require it. It is acceptable for maximise option to be greyed out provided alternate Alt F8 is available. Presently basic accessibility standards compromised. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/966524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966524] Re: control center window is not manually resizeable
Ah - so as I thought it is now a single default setting or a system wide setting that needs to be changed - it's multiple windows- apps. It goes right back to design and branding! A Better reason for a Standard System Wide Accessibility Policy I have never seen confirmed so quickly. That policy need to inform all action from design and branding through to coding - so that if there are multiple critical windows - they can be identified, logged, checked and made to comply with accessibility standards. That of course would be the function of the Accessibility Guardian - watch - catch and if necessary bite hard! Ubiquity the installer also probably demands to set it's own dimensions, which is particularly annoying on the map page, but that is two separate issues, one in gnome-control-centre and one in ubiquity. It's not two separate issues - It is two bugs - with one common cause! If accessibility was being taken seriously there would be no cause for the bugs! P^) -- 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/966524 Title: control center window is not manually resizeable Status in “gnome-control-center” package in Ubuntu: New Bug description: Ubuntu Precise Development Branch. 12.04 Further to Bug report #964685 - I am advised that the following behaviour is caused by Compiz. 1. Start live cd - click desktop to change background to suitable colour. Facility to maximise window using Alt F8 has is greyed out - needs to re restored to meet accessibility standards - and should be working in the beta. This accessibility feature is present in 10.04.4 through to 11.10 (verified today) - and should still be present in 12.04. It should not have been removed or deprecated under Gnome shell/3 or Unity - or for testing purposes. Issue visible in screen print - attached. Issue affects multiple windows from Boot of live CD and through Install process and in installed system. Numerous people with visual and neurodiveristy disabilities need the ability to maximise these windows to allow concentration on single task with minimal image/background noise. Window sizes may be presented inline with branding guidelines - but they should retain accessibility feature for those who need it and require it. It is acceptable for maximise option to be greyed out provided alternate Alt F8 is available. Presently basic accessibility standards compromised. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/966524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966656] [NEW] indicator-applet - high contrast icons missing when high contrast themes selected - compromising Accessibility Standards
Public bug reported: Ubuntu Precise Development Branch. 12.04 Ref Bug report #966574 and #964685. indicator-applet fails to display high contrast icons when high contrast theme used. Fails basic Accessibility Standards. Multiple High Contrast and High Contrast Inverse Icons needed to replace default icons which are presently poor and inaccessible. Amusingly - the one high contrast icon that was right in the app indicator is the volume control - but only in High Contrast. Change to high contrast inverse and it vanishes and not even a basic default to replace it. Power button also need to be in high contrast. Issues can be seen in screen print - https://launchpadlibrarian.net/98309253/Screenshot.png ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: a11y accesability access indicator-applet universal -- 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/966656 Title: indicator-applet - high contrast icons missing when high contrast themes selected - compromising Accessibility Standards Status in “gnome-control-center” package in Ubuntu: New Bug description: Ubuntu Precise Development Branch. 12.04 Ref Bug report #966574 and #964685. indicator-applet fails to display high contrast icons when high contrast theme used. Fails basic Accessibility Standards. Multiple High Contrast and High Contrast Inverse Icons needed to replace default icons which are presently poor and inaccessible. Amusingly - the one high contrast icon that was right in the app indicator is the volume control - but only in High Contrast. Change to high contrast inverse and it vanishes and not even a basic default to replace it. Power button also need to be in high contrast. Issues can be seen in screen print - https://launchpadlibrarian.net/98309253/Screenshot.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/966656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 886056] Re: Cannot respond to friendship requests from Empathy
I'm not entirely sure this should be forwarded to upstream. This seems to be caused by NotifyOSD bubbles not supporting actions. Shouldn't NotifyOSD fall back to an alert box in this case? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/886056 Title: Cannot respond to friendship requests from Empathy Status in “empathy” package in Ubuntu: Confirmed Status in “telepathy-indicator” package in Ubuntu: Confirmed Bug description: When I'm using GTalk in Empathy and someone requests to see my status, I get a notification bubble but can't do nothing about it. If I happen to already have the person in my contact list, I can open the list and click on the name to authorize. But most of the time people will *not* already have the person in there. I remember that in previous version of Ubuntu, a request would create an entry in the Messaging Menu, which would then show a dialog box when you clicked on it. Not sure if it was the best solution, but at least it was something. I don't know if this was disabled or broke. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Nov 4 09:16:52 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/886056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 886056] [NEW] Cannot respond to friendship requests from Empathy
Public bug reported: When I'm using GTalk in Empathy and someone requests to see my status, I get a notification bubble but can't do nothing about it. If I happen to already have the person in my contact list, I can open the list and click on the name to authorize. But most of the time people will *not* already have the person in there. I remember that in previous version of Ubuntu, a request would create an entry in the Messaging Menu, which would then show a dialog box when you clicked on it. Not sure if it was the best solution, but at least it was something. I don't know if this was disabled or broke. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Nov 4 09:16:52 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: empathy (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/886056 Title: Cannot respond to friendship requests from Empathy Status in “empathy” package in Ubuntu: Confirmed Bug description: When I'm using GTalk in Empathy and someone requests to see my status, I get a notification bubble but can't do nothing about it. If I happen to already have the person in my contact list, I can open the list and click on the name to authorize. But most of the time people will *not* already have the person in there. I remember that in previous version of Ubuntu, a request would create an entry in the Messaging Menu, which would then show a dialog box when you clicked on it. Not sure if it was the best solution, but at least it was something. I don't know if this was disabled or broke. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Nov 4 09:16:52 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/886056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 886056] Re: Cannot respond to friendship requests from Empathy
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/886056 Title: Cannot respond to friendship requests from Empathy Status in “empathy” package in Ubuntu: Confirmed Bug description: When I'm using GTalk in Empathy and someone requests to see my status, I get a notification bubble but can't do nothing about it. If I happen to already have the person in my contact list, I can open the list and click on the name to authorize. But most of the time people will *not* already have the person in there. I remember that in previous version of Ubuntu, a request would create an entry in the Messaging Menu, which would then show a dialog box when you clicked on it. Not sure if it was the best solution, but at least it was something. I don't know if this was disabled or broke. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Nov 4 09:16:52 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/886056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 882852] Re: Toolbar buttons should have active and highlight visuals that include the arrows
** Attachment added: out.ogv https://bugs.launchpad.net/bugs/882852/+attachment/2576030/+files/out.ogv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/882852 Title: Toolbar buttons should have active and highlight visuals that include the arrows Status in “software-center” package in Ubuntu: New Bug description: The arrows for the All software and Installed buttons do not visually feel like part of the buttons, specially when one of the buttons is active. The current active color should be applied to the arrow too, and there should be a hover color that does the same. Also, it would be better if the separator between the main part of the button and the arrow appeared only on hover. I'm attaching a video that shows how Thunderbird does it. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-center 5.0.2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 27 21:43:14 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/882852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 775080] Re: Thunderbird with Firetray - menu in Unity top bar disappears
The bug is not exclusive to FireTray, I'm also having it with the MinimizeToTray Revived extension: https://tn123.org/mintrayr/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/775080 Title: Thunderbird with Firetray - menu in Unity top bar disappears Status in Unity global menubar extension for Firefox and Thunderbird: Triaged Status in “thunderbird” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Bug description: Binary package hint: thunderbird Running thunderbird with the Firetray plugin. Clicking the close button in thunderbird does not kill thunderbird but sends it to the background, but Unity thinks the app is closed (the little arrow(s) don't show anymore). When opening again from Unity, it recognized the app as running, but the menus (File, Edit, etc) fail to show in the top bar when the mouse is brought up there. The only way to get it back is to kill thunderbird and restart it. Disabling the firetray plugin, which doesn't work with Unity anyway, fixes this problem. However, it would be great to have a tray icon by the session menu. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: thunderbird 3.1.9+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun May 1 14:44:42 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/globalmenu-extension/+bug/775080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
