[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Christian, it should only be using msbc when the headset's microphone is in use, otherwise it should automatically fall back to A2DP. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 Ah my apologies, I didn't realise I had already reported this a few months back when updating to jammy here https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2000917 Title: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Every now and then, after boot, I get no sounds at all coming from the speakers. Everything seems normal - the control center reports the output as active, and if I play anything with sound I can see the VU meter going back and forth. I've attached a screenshot showing as much. The internal microphone does not pick up any sounds either when this happens. If I connect my Bose NC700 bluetooth headset, I get sound out of it just fine, and the mike on it also works. Sometimes the internal sound will start working after a few times of switching back and forth internal audio / bluetooth headset. Restarting the systemd pipewire and pipewire-pulse user services doesn't help. Nor does killing & respawning wireplumber. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Tue Jan 3 11:25:23 2023 InstallationDate: Installed on 2023-01-03 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 That does sound like it could be an issue for sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2000917 Title: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Every now and then, after boot, I get no sounds at all coming from the speakers. Everything seems normal - the control center reports the output as active, and if I play anything with sound I can see the VU meter going back and forth. I've attached a screenshot showing as much. The internal microphone does not pick up any sounds either when this happens. If I connect my Bose NC700 bluetooth headset, I get sound out of it just fine, and the mike on it also works. Sometimes the internal sound will start working after a few times of switching back and forth internal audio / bluetooth headset. Restarting the systemd pipewire and pipewire-pulse user services doesn't help. Nor does killing & respawning wireplumber. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Tue Jan 3 11:25:23 2023 InstallationDate: Installed on 2023-01-03 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
Works for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Fix Released Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Invalid Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
Added `gnome-control-center` to affected - GNOME online accounts requires a web browsing session to auth into some services. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in liferea package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
`WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution` works around the issue for me on a Sway wayland session and running evolution in native wayland mode. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in liferea package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965750] [NEW] [jammy regression] No sound from onboard audio (playback / record)
Public bug reported: After updates I applied last friday, my onboard audio has ceased to function. No audio comes out the laptop speakers and no audio goes in the internal microphone (built in audio). If I connect my bluetooth headset (Bose NC700) the audio works, but only ever in mono. I cannot switch to the A2DP sink, it stays on HPF mono. I tried switching from pulseaudio to pipewire and pipewire-pulse, and I kind of made it work - the bluetooth headset works correctly, and the onboard audio works again after switching default inputs and outputs a number of times. I just want to stress my laptop's audio has worked fine for years in all versions of ubuntu including Jammy, but only up until Friday Jan the 18th 2022. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Mon Mar 21 11:48:25 2022 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965750 Title: [jammy regression] No sound from onboard audio (playback / record) Status in alsa-driver package in Ubuntu: New Bug description: After updates I applied last friday, my onboard audio has ceased to function. No audio comes out the laptop speakers and no audio goes in the internal microphone (built in audio). If I connect my bluetooth headset (Bose NC700) the audio works, but only ever in mono. I cannot switch to the A2DP sink, it stays on HPF mono. I tried switching from pulseaudio to pipewire and pipewire-pulse, and I kind of made it work - the bluetooth headset works correctly, and the onboard audio works again after switching default inputs and outputs a number of times. I just want to stress my laptop's audio has worked fine for years in all versions of ubuntu including Jammy, but only up until Friday Jan the 18th 2022. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Mon Mar 21 11:48:25 2022 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
Thank you, I was plagued by this issue on my Bose NC700 cans. In my case bluetoothd isn't crashing btw. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I haven't got any pulseaudio updates on 21.04, to which version of ubuntu was the fix released to? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
That would be for 21.10 at this point yes? I wonder, how close/far is Ubuntu to swap PA for Pipewire? After next lts? I do believe this particular issue is not present on current Pipewire. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
Fix will come with network-manager-gnome 1.20.0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
I managed to get Campbell's patch to hide unmanaged devices upstreamed: https://gitlab.gnome.org/GNOME/network-manager- applet/-/merge_requests/93 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
You can manually select the output to use from gnome-settings until the fix lands. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
Indeed disabling sysrq seems to fix the problem, but this has worked for donkey's ages so what exactly changed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in systemd package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 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: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722708] Re: Crash when setting laptop display resolution
I have the same problem. I can set my laptop display to FHD down from 4K to match my external monitor, but as soon as I click on "scale 100%" button the apply button disappears and I get "Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitor scales must be identical" on the console. A workaround that works in the meantime is to use arandr, arrange your screens, and apply any changes - this will reset scale back to 1 and gnome display control panel works again. Arandr bottom snap can make both displays overlap, bear that in mind if you get the gnome panel repeated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1722708 Title: Crash when setting laptop display resolution Status in xorg package in Ubuntu: Fix Released Bug description: This system has a 4k laptop screen with resolution 3840x2160, and an external HP monitor connected via HDMI, resolution 1920x1200. Windows, fonts etc are not scaled properly on the external monitor (too large, etc), and the only workaround I've found with earlier versions and other distros is to set the laptop display to 1920x1080 mode, so that's what I'm trying here as well. However, when doing that, the X (wayland, not sure if the package is correct here) session crashes and brings me back to login screen. So to summarize: connect the external monitor, go to Settings > Devices > Displays, click primary built in display, observe that it shows Resolution 3840x2160 (16:9) and Scale 200%, change resolution to 1920x1080 (16:9), click Apply --> crash. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 07:49:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2248] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:2248] InstallationDate: Installed on 2017-10-10 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171008) MachineType: LENOVO 20H9004MMX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=182b5236-fa96-4fb5-bea9-f90769b65f3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET35W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20H9004MMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET35W(1.25):bd09/06/2017:svnLENOVO:pn20H9004MMX:pvrThinkPadT570:rvnLENOVO:rn20H9004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T570 dmi.product.name: 20H9004MMX dmi.product.version: ThinkPad T570 dmi.sys.vendor: LENOVO 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.3-1ubuntu7 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/1722708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733557] Re: Login screen showing Authentication Failed Switch to greeter...
I'm seeing this also upon 17.10 upgrade in unity / lightdm / unity greeter. It doesn't happen 100% of the time, typically takes some time time to manifest (I only ever suspend my laptop from monday to friday), but once it starts happening, it always happens until I shut down. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failed Switch to greeter... Status in lightdm package in Ubuntu: Confirmed Bug description: When I lock my machine, the login screen shows my current user with the message: "Authentication Failed" ..and in the position when the password normally exists, the option "Switch to greeter..." ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 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.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 21 10:28:47 2017 InstallationDate: Installed on 2017-04-17 (217 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1733557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
This workaround works for me, but years of muscle memory... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in systemd package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 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: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439440] Re: Laptop does not go to sleep when closing lid with external monitor connected
Did you upgrade from 14.04? This is a systemd issue, which was introduced after 14.04 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1439440 Title: Laptop does not go to sleep when closing lid with external monitor connected Status in xorg package in Ubuntu: Confirmed Bug description: Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on HDMI output, in 15.04 beta 2: when closing the lid of the laptop, the laptop does not go to sleep (suspend to ram) as expected, but instead stays on, with the external monitor still on. I excepted that the laptop goes to sleep and the external monitor was blanked and turned off. This was the behavior on 14.10 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu4 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: Thu Apr 2 01:17:27 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0597] InstallationDate: Installed on 2015-04-01 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed root=UUID=cxxx---- ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06XXX:rvrA02:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Thu Apr 2 00:14:49 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 939 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues
Yes, this version of NM is the current one on 15.10, I was able to download and install the package without any issues from here: https://launchpad.net/ubuntu/+source/network- manager/0.9.10.0-4ubuntu18/+build/7652985 Indeed it fixes this issue. There's however a newer version: https://launchpad.net/ubuntu/wily/amd64/network-manager/1.0.4-0ubuntu2 Haven't tried it. I will remain on 0.9.10.0-4ubuntu18 for the time being. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1436330 Title: Network Manager doesn't set metric for local networks any more, causing connection issues Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Vivid: Triaged Bug description: [Impact] NM changed its method of setting routes on systems, and no longer attaches a metric value specific to the type of device being used. These values were used to prioritize connections, so that for example, when connected to both wired and wireless at the same time, wired can be used in priority over wireless without incurring packet loss. Currently, when connected to both wired and wireless are connected to the same subnet, the user may notice connectivity issues since packets are sent in a round-robin fashion over all default routes on the same subnet with the same metric. [Test Case] 1- Connect to a wireless network. 2- Connect to the same network over Ethernet both connections should come up on the same subnet. 3- Make sure there is no packet loss, and that there are specific metric values for each default route, as displayed by 'ip route'. [Regression Potential] Since handling default routes properly involves correcting the behavior for all device types, VPN behavior may change to pick up the default routes in all cases, over a wired connection. It's also possible that a connection pick up the default route when it is not meant to. --- With Vivid, having two connections to the same network subnet is unstable due to missing metrics for local networks. Example: Being connected to 192.168.1.0/24 via both wired and wireless will cause connectivity issues as sent packets hop between the two interfaces. It used to be that this wasn't an issue. I would go between work and home and plug in and my machine would automatically connect to wireless and it would use the lower metric ethernet interface for all communications, while the wlan interface would remain connected but unused. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 25 09:17:27 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-25 (58 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1436330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues
Any idea if this will be released for Ubuntu 15.04? A month later and latest nm version available is still 0.9.10.0-4ubuntu15.1 Luis Pabón On 15 July 2015 at 00:37, Launchpad Bug Tracker 1436...@bugs.launchpad.net wrote: This bug was fixed in the package network-manager - 0.9.10.0-4ubuntu18 --- network-manager (0.9.10.0-4ubuntu18) wily; urgency=medium * debian/tests/nm, debian/tests/wpa-dhclient: 802.11a appears to no longer have any supported channels for AP mode: mark all four 802.11a tests as expectedFailures while I dig into hostapd/mac80211_hwsim to get them to work again. Expected failure means we'll be notified as soon as they start to succeed again. -- Mathieu Trudel-Lapierre mathieu...@ubuntu.com Tue, 14 Jul 2015 18:11:58 -0400 ** Changed in: network-manager (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are subscribed to a duplicate bug report (1454568). https://bugs.launchpad.net/bugs/1436330 Title: Network Manager doesn't set metric for local networks any more, causing connection issues To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1436330/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1436330 Title: Network Manager doesn't set metric for local networks any more, causing connection issues Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Vivid: Triaged Bug description: [Impact] NM changed its method of setting routes on systems, and no longer attaches a metric value specific to the type of device being used. These values were used to prioritize connections, so that for example, when connected to both wired and wireless at the same time, wired can be used in priority over wireless without incurring packet loss. Currently, when connected to both wired and wireless are connected to the same subnet, the user may notice connectivity issues since packets are sent in a round-robin fashion over all default routes on the same subnet with the same metric. [Test Case] 1- Connect to a wireless network. 2- Connect to the same network over Ethernet both connections should come up on the same subnet. 3- Make sure there is no packet loss, and that there are specific metric values for each default route, as displayed by 'ip route'. [Regression Potential] Since handling default routes properly involves correcting the behavior for all device types, VPN behavior may change to pick up the default routes in all cases, over a wired connection. It's also possible that a connection pick up the default route when it is not meant to. --- With Vivid, having two connections to the same network subnet is unstable due to missing metrics for local networks. Example: Being connected to 192.168.1.0/24 via both wired and wireless will cause connectivity issues as sent packets hop between the two interfaces. It used to be that this wasn't an issue. I would go between work and home and plug in and my machine would automatically connect to wireless and it would use the lower metric ethernet interface for all communications, while the wlan interface would remain connected but unused. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 25 09:17:27 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-25 (58 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1436330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373118] Re: Vertical line of pixels separating the launcher from the rest of the screen
I concur. How's this a feature? What purpose does it serve other than looking out of place? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1373118 Title: Vertical line of pixels separating the launcher from the rest of the screen Status in Unity: Won't Fix Status in unity package in Ubuntu: Won't Fix Bug description: There is a line of pixels from the wallpaper, between the launcher on the left, and the rest of the content. It is especially visible when contrasted with a darker content (e.g. terminal or a black picture) - because the wallpaper is of that color. This is best seen on the attached image. I was also told this could be a Compiz bug, so I'll try to add them as well (I've subscribed compiz packagers - not sure if that was what I was supposed to do). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1-systray-ppa1 [origin: LP-PPA-gurqn-systray-trusty] Uname: Linux 3.17.0-031700rc6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashDB: unity CurrentDesktop: Unity Date: Tue Sep 23 22:26:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon HD 7790/8770 / R9 260 OEM] [1002:665c] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon HD 7790 OC [1462:2930] InstallationDate: Installed on 2014-07-14 (71 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.0-031700rc6-generic root=UUID=6e991daa-60a1-41a6-86b9-099d96d697f2 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56+git1409220630.666788~gd~t version.libgl1-mesa-dri: libgl1-mesa-dri 10.4~git1409231930.4ed23f~gd~t version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4~git1409231930.4ed23f~gd~t version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.99+git1409110730.56c7fb~gd~t version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git1409220730.376037~gd~t version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git1409010731.3cd4c8~gd~t xserver.bootTime: Tue Sep 23 22:21:28 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 8 inputLogitech USB Optical Mouse MOUSE, id 9 inputEee PC WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1373118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1454568] Re: No internet when both Wifi and Ethernet are connected
The IProute info on the previous post does not reflect the network config at the time of the issue being reported - ubuntu-bug just won't work without access to the internet. I'd re-generate that info manually then copypaste it here if I knew how to wrestle Ubuntu into giving it to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1454568 Title: No internet when both Wifi and Ethernet are connected Status in network-manager package in Ubuntu: New Bug description: If I have both Wifi and wired ethernet connected at the same time, I get no access to the internet. Internal virtual networks (Virtualbox) continue working and I can operate on any virtualised instances via ssh though. Doesn't seem to be a DNS issue as pinging IP addresses directly time out. As soon as I manually disconnect (not disable) the wifi connetion, internet starts working the instant after. Maybe some sort of routing confusion? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 09:45:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-01 (11 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/22 dev eth0 proto kernel scope link src 10.0.3.55 192.168.33.0/24 dev vboxnet1 proto kernel scope link src 192.168.33.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1454568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1454568] [NEW] No internet when both Wifi and Ethernet are connected
Public bug reported: If I have both Wifi and wired ethernet connected at the same time, I get no access to the internet. Internal virtual networks (Virtualbox) continue working and I can operate on any virtualised instances via ssh though. Doesn't seem to be a DNS issue as pinging IP addresses directly time out. As soon as I manually disconnect (not disable) the wifi connetion, internet starts working the instant after. Maybe some sort of routing confusion? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 09:45:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-01 (11 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/22 dev eth0 proto kernel scope link src 10.0.3.55 192.168.33.0/24 dev vboxnet1 proto kernel scope link src 192.168.33.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1454568 Title: No internet when both Wifi and Ethernet are connected Status in network-manager package in Ubuntu: New Bug description: If I have both Wifi and wired ethernet connected at the same time, I get no access to the internet. Internal virtual networks (Virtualbox) continue working and I can operate on any virtualised instances via ssh though. Doesn't seem to be a DNS issue as pinging IP addresses directly time out. As soon as I manually disconnect (not disable) the wifi connetion, internet starts working the instant after. Maybe some sort of routing confusion? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 09:45:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-01 (11 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/22 dev eth0 proto kernel scope link src 10.0.3.55 192.168.33.0/24 dev vboxnet1 proto kernel scope link src 192.168.33.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1454568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353951] Re: gnome online accounts require autentication on startup
Still broken on 15.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1353951 Title: gnome online accounts require autentication on startup Status in Evolution Data Server: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in gnome-online-accounts package in Ubuntu: Invalid Status in evolution-data-server source package in Trusty: Fix Released Status in gnome-online-accounts source package in Trusty: Invalid Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] 1) open gnome-online-accounts 2) click + and add a google account 3) enter user name and password 4) confirm permissions for gnome 5) Black window pops up and asks for google password, but does not accept the correct password. Google Contacts are not available in Gnome or Thunderbird [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Gnome online accounts requires autentication on startup, but even typing the correct password in the box, the program says the password is wrong. By the way evolution and other programs work well with online accounts. I'm using Ubuntu-gnome 14.04 LTS 64bit on different machines and have the same behaviour. Just to be clear: online-accounts works well, just at startup it opens an administration window where it requires to insert the password for my google accounts; if I type the correct password it says that the password is wrong, the only way to close the window is to click on discard and then all works well. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1353951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452308] Re: Mysql Workbench repeated menu options when using locally integrated menus
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1452308 Title: Mysql Workbench repeated menu options when using locally integrated menus Status in compiz package in Ubuntu: New Status in mysql-workbench package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: When using locally integrated menus, Mysql workbench becomes a menu- nightmare of titanic proportions. There seems to be two sets of menues being repeated. The options are not the same on the first file menu as on the second. It's just better to look at the screenshot attached, actually. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mysql-workbench 6.2.3+dfsg-7build1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 6 15:50:43 2015 InstallationDate: Installed on 2015-05-01 (5 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: mysql-workbench UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1452308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439440] Re: Laptop does not go to sleep when closing lid with external monitor connected
Same here on Ubuntu 15.05 and intel haswell integrated graphics. Laptop won't go to sleep when closing the lid if an external monitor is connected. Can manually suspend from the power menu, or closing the lid with no external monitor attached. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1439440 Title: Laptop does not go to sleep when closing lid with external monitor connected Status in xorg package in Ubuntu: Confirmed Bug description: Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on HDMI output, in 15.04 beta 2: when closing the lid of the laptop, the laptop does not go to sleep (suspend to ram) as expected, but instead stays on, with the external monitor still on. I excepted that the laptop goes to sleep and the external monitor was blanked and turned off. This was the behavior on 14.10 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu4 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: Thu Apr 2 01:17:27 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0597] InstallationDate: Installed on 2015-04-01 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed root=UUID=cxxx---- ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06XXX:rvrA02:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Thu Apr 2 00:14:49 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 939 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448208] [NEW] Wrong keyboard layout selected on boot
Public bug reported: I have two keyboard layouts configured to choose from, English (UK) (default) and Spanish (Spain) as I constantly switch among those two languages. After upgrade from 14.10 to 15.04, the keyboard layout active after I log into my session is neither of those. I can't identify which one. All I know is the @ symbol is at shift+2 instead of its usual location right of the colon/semicolon. The language selector indicator shows English (UK). If I re-select English (UK), keyboard layout goes back to normal. [development@localhost ~]$ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: apport (Ubuntu) = ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1448208 Title: Wrong keyboard layout selected on boot Status in Ubuntu: New Bug description: I have two keyboard layouts configured to choose from, English (UK) (default) and Spanish (Spain) as I constantly switch among those two languages. After upgrade from 14.10 to 15.04, the keyboard layout active after I log into my session is neither of those. I can't identify which one. All I know is the @ symbol is at shift+2 instead of its usual location right of the colon/semicolon. The language selector indicator shows English (UK). If I re-select English (UK), keyboard layout goes back to normal. [development@localhost ~]$ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
