[Desktop-packages] [Bug 2060354] [NEW] Segfault in 2:21.1.4-2ubuntu1.7-22.04.9
Public bug reported: I just upgraded xserver-xorg-core and xserver-common to 2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate EAP (downloaded from JerBrains website) Xorg server crashes with segfault: X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 #0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr 4 20:28:35 UTC x86_64 Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 6 15:28:18 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" malloc(): unaligned tcache chunk detected (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc] (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7ec01c429d90] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7ec01c429e40] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605] (EE) (EE) Fatal server error: (EE) Caught signal 6 (Aborted). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like security backports were done incorrectly. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Project changed: xserver-xorg-driver-vesa => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfault in 2:21.1.4-2ubuntu1.7-22.04.9 Status in xorg-server package in Ubuntu: New Bug description: I just upgraded xserver-xorg-core and xserver-common to 2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate EAP (downloaded from JerBrains website) Xorg server crashes with segfault: X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 #0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr 4 20:28:35 UTC x86_64 Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 6 15:28:18 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" malloc(): unaligned tcache chunk detected (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6
[Desktop-packages] [Bug 1625773] Re: Segfault when using -w / --window to screenshot current window.
Can't make window screenshot either. Whole screen or part of the screen is fine, but window segfaults. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1625773 Title: Segfault when using -w / --window to screenshot current window. Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: The gnome-screenshot program segfaults every time, when I try to capture the current window with `gnome-screenshot -w`. Taking an area screenshot with `gnome-screenshot -a`, and taking a full desktop screenshot with `gnome-screenshot` works, but taking a current window screenshot with `gnome-screenshot -w` segfaults every time. Adding delay with `-d ` and capturing pointer or not with `-p` has no effect. This may be the same bug as https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/81817 although that one is closed long ago. The relationship is that I'm using gnome-screenshot inside the XMonad window manager, a non- standard window manager. Stack trace: $ gdb gnome-screenshot GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 [...] Reading symbols from gnome-screenshot...(no debugging symbols found)...done. (gdb) core-file core warning: core file may not match specified executable file. [New LWP 25469] [New LWP 25472] [New LWP 25470] [New LWP 25471] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `gnome-screenshot -d 3 -w -p'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0040dbb5 in ?? () [Current thread is 1 (Thread 0x7f3b4c841a40 (LWP 25469))] (gdb) where #0 0x0040dbb5 in ?? () #1 0x0040e1ea in ?? () #2 0x00408bc1 in ?? () #3 0x00408df9 in ?? () #4 0x7f3b4a5afac3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3b4a5af05a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3b4a5af400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f3b4a5af4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f3b4ab76cdd in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #9 0x00408385 in ?? () #10 0x7f3b49a84830 in __libc_start_main (main=0x408320, argc=5, argv=0x7fff78989e68, init=, fini=, rtld_fini=, stack_end=0x7fff78989e58) at ../csu/libc-start.c:291 #11 0x004083c9 in ?? () System information: $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy gnome-screenshot gnome-screenshot: Installed: 3.18.0-1ubuntu2 Candidate: 3.18.0-1ubuntu2 Version table: *** 3.18.0-1ubuntu2 500 500 http://vault.galois.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1625773/+subscriptions -- Mailing list: https://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 1963767] Re: [jammy] Microphone not working after suspend
Did you test he same webcam as I did (Logitech BRIO)? If it happens for me with two laptops from different manufacturers that have different processors (Intel vs AMD), there is certainly something going on. It happened on 21.10 and now happns on 22.04 LTS version of Ubuntu, so the bug report should be valid IMHO. Thankfully I'm not using laptop actively, it is a really bad experience. -- 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/1963767 Title: [jammy] Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Re: [Purism Librem 13 v4] Microphone not working after suspend
I don't think bug title change is correct, this is confirmed to happen on 3 distinct laptops already in this thread. -- 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/1963767 Title: [Purism Librem 13 v4] Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603781/+files/acpidump.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603779/+files/UdevDb.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603780/+files/WifiSyslog.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603778/+files/RfKill.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603777/+files/PulseList.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603776/+files/ProcModules.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603774/+files/ProcCpuinfoMinimal.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603775/+files/ProcInterrupts.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603773/+files/PaInfo.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603771/+files/Lspci-vt.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603772/+files/Lsusb-v.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603770/+files/Lspci.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603769/+files/IwConfig.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603768/+files/Dependencies.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603767/+files/CurrentDmesg.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603766/+files/CRDA.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Re: Microphone not working after suspend
apport information ** Tags added: wayland-session ** Description changed: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nazar-pc 1488 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-02-15 (153 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M + |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M + |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M + MachineType: Purism Librem 13 v4 + Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=uk_UA.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-39-generic N/A + linux-backports-modules-5.15.0-39-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.2 + Tags: jammy wayland-session wayland-session + Uname: Linux 5.15.0-39-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/27/2022 + dmi.bios.release: 4.15 + dmi.bios.vendor: coreboot + dmi.bios.version: 4.15-Purism-3 + dmi.board.name: Librem 13 v4 + dmi.board.vendor: Purism + dmi.board.version: 1.0 + dmi.chassis.type: 9 + dmi.chassis.vendor: Purism + dmi.ec.firmware.release: 0.0 + dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: + dmi.product.family: Librem 13 + dmi.product.name: Librem 13 v4 + dmi.product.version: 1.0 + dmi.sys.vendor: Purism ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5603765/+files/AlsaInfo.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64
[Desktop-packages] [Bug 1963767] Re: Microphone not working after suspend
Actually I have tested it on a different laptop this time: Purism Libre 13 Version 4. So this shouldn't be laptop-specific either. -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Re: Microphone not working after suspend
Just tested the same Logitech BRIO on Ubuntu 22.04 LTS, still the same issue. -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Re: Microphone not working after suspend
Yeah, situation on this laptop is very problematic. It loses microphone audio all of a sudden often on its own (I unmute myself on Google Meet and notice there is no audio from me). -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5566134/+files/ProcEnviron.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5566133/+files/ProcCpuinfoMinimal.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] Re: Microphone not working after suspend
apport information ** Tags added: apport-collected impish ** Description changed: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` - Not sure whose fault it is, likely kernel driver, but the fact that - pulseaudio needs to be restarted is concerning as well. Reproducible - 100% for me. + Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: Custom + DistroRelease: Ubuntu 21.10 + Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 + PackageArchitecture: amd64 + Tags: impish + Uname: Linux 5.16.11-xanmod1 x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1963767/+attachment/5566132/+files/Dependencies.txt -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1963767] [NEW] Microphone not working after suspend
Public bug reported: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. - On Ubuntu 21.10 after suspend (systemctl suspend) webcam's microphone + On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is stil l there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. ** Description changed: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone - stops working (device is stil l there, but audio level is at zero all - the time). + stops working (device is still there, but audio level is at zero all the + time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://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 1753395] Re: Upgrade failure: dependency problems prevent configuration of gnome-session:
Same issue on Bionic proposed. I have very little packages related to gnome-session since I'm running a custom DE. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1753395 Title: Upgrade failure: dependency problems prevent configuration of gnome- session: Status in gnome-session package in Ubuntu: Confirmed Bug description: Terminal output error seen while upgrading: Setting up gnome-session-common (3.27.91-0ubuntu1) ... dpkg: dependency problems prevent configuration of gnome-session: gnome-session depends on gnome-session-bin (>= 3.27.91-0ubuntu1); however: Package gnome-session-bin is not configured yet. gnome-session depends on gnome-session-bin (<< 3.28); however: Package gnome-session-bin is not configured yet. dpkg: error processing package gnome-session (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ubuntu-session: ubuntu-session depends on gnome-session-bin (>= 3.27.91-0ubuntu1); however: Package gnome-session-bin is not configured yet. ubuntu-session depends on gnome-session-bin (<< 3.28); however: Package gnome-session-bin is not configured yet. dpkg: error processing package ubuntu-session (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: gnome-session-bin gnome-session ubuntu-session E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up gnome-session-bin (3.27.91-0ubuntu1) ... update-alternatives: error: alternative path /usr/bin/gnome-session doesn't exist dpkg: error processing package gnome-session-bin (--configure): installed gnome-session-bin package post-installation script subprocess returned error exit status 2 dpkg: dependency problems prevent configuration of gnome-session: gnome-session depends on gnome-session-bin (>= 3.27.91-0ubuntu1); however: Package gnome-session-bin is not configured yet. gnome-session depends on gnome-session-bin (<< 3.28); however: Package gnome-session-bin is not configured yet. dpkg: error processing package gnome-session (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ubuntu-session: ubuntu-session depends on gnome-session-bin (>= 3.27.91-0ubuntu1); however: Package gnome-session-bin is not configured yet. ubuntu-session depends on gnome-session-bin (<< 3.28); however: Package gnome-session-bin is not configured yet. dpkg: error processing package ubuntu-session (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: gnome-session-bin gnome-session ubuntu-session ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.27.91-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Mar 5 09:28:22 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753395/+subscriptions -- Mailing list: https://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 1701747] Re: Remove hard dependencies on libmir* in relevant packages
I just want to keep my system clean. I don't have ubuntu-desktop and lots of standard packages and noticed these Mir-related packages but was unable to remove them. Not a big deal in general, but still a number of packages that will never be used. Also installation ISO contains these packages and everyone downloads something that will not be used in most if not all desktop setups. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1701747 Title: Remove hard dependencies on libmir* in relevant packages Status in gtk+3.0 package in Ubuntu: New Status in mesa package in Ubuntu: Won't Fix Bug description: I think everyone will agree that Mir is not used by majority of users. So I don't understand why many packages have hard dependencies on libmir* packages. I don't want them in my system because I'll never user them. Make them optional, please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions -- Mailing list: https://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 1702037] [NEW] Optional dependency on unrar-free
Public bug reported: file-roller package has optional dependency on (suggests) unrar, but not unrar-free. Can someone add unrar-free to the list of optional dependencies? ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1702037 Title: Optional dependency on unrar-free Status in file-roller package in Ubuntu: New Bug description: file-roller package has optional dependency on (suggests) unrar, but not unrar-free. Can someone add unrar-free to the list of optional dependencies? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1702037/+subscriptions -- Mailing list: https://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 1701747] Re: Remove hard dependencies on libmir* in relevant packages
I have nothing against Mir itself, but why can't those packages be optional dependencies? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1701747 Title: Remove hard dependencies on libmir* in relevant packages Status in gtk+3.0 package in Ubuntu: New Status in mesa package in Ubuntu: Won't Fix Bug description: I think everyone will agree that Mir is not used by majority of users. So I don't understand why many packages have hard dependencies on libmir* packages. I don't want them in my system because I'll never user them. Make them optional, please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions -- Mailing list: https://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 1702001] [NEW] Remove hard dependency on Mir
Public bug reported: Mir is not used in most setups, however, libegl1-mesa depends on libmirclient9 and forces Mir libraries to be present. Make this dependency optional, please. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1702001 Title: Remove hard dependency on Mir Status in mesa package in Ubuntu: New Bug description: Mir is not used in most setups, however, libegl1-mesa depends on libmirclient9 and forces Mir libraries to be present. Make this dependency optional, please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1702001/+subscriptions -- Mailing list: https://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 1702000] [NEW] Remove hard dependency on Mir
Public bug reported: Mir is not used in most setups, however, libgtk-3-0 depends on libmirclient9 and forces Mir libraries to be present. Make this dependency optional, please. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1702000 Title: Remove hard dependency on Mir Status in gtk+3.0 package in Ubuntu: New Bug description: Mir is not used in most setups, however, libgtk-3-0 depends on libmirclient9 and forces Mir libraries to be present. Make this dependency optional, please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1702000/+subscriptions -- Mailing list: https://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 1691549] Re: WIth recent update multiple applications have issues with mic
Here is PulseAudio output when game freezes: I: [alsa-source-USB Audio] alsa-source.c: Decreasing wakeup watermark to 13,38 ms I: [alsa-source-USB Audio] alsa-source.c: Decreasing wakeup watermark to 8,38 ms I: [alsa-source-USB Audio] alsa-source.c: Decreasing wakeup watermark to 4,19 ms I: [alsa-source-USB Audio] alsa-source.c: Decreasing wakeup watermark to 4,00 ms D: [pulseaudio] module-suspend-on-idle.c: Source alsa_input.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00.analog-stereo-input becomes idle, timeout in 5 seconds. D: [alsa-source-USB Audio] alsa-source.c: hwbuf_unused=0 D: [alsa-source-USB Audio] alsa-source.c: setting avail_min=95809 D: [pulseaudio] module-suspend-on-idle.c: Source alsa_input.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00.analog-stereo-input becomes idle, timeout in 5 seconds. I: [pulseaudio] source-output.c: Freeing output 3 "Record Stream" I: [pulseaudio] client.c: Freed 12 "FMOD Record Helper" I: [pulseaudio] protocol-native.c: Connection died. D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00.analog-stereo-output becomes idle, timeout in 5 seconds. D: [alsa-sink-USB Audio] alsa-sink.c: hwbuf_unused=0 D: [alsa-sink-USB Audio] alsa-sink.c: setting avail_min=95119 D: [alsa-sink-USB Audio] alsa-sink.c: Requested volume: front-left: 37985 / 58% / -14,21 dB, front-right: 37985 / 58% / -14,21 dB D: [alsa-sink-USB Audio] alsa-sink.c: Got hardware volume: front-left: 38295 / 58% / -14,00 dB, front-right: 38295 / 58% / -14,00 dB D: [alsa-sink-USB Audio] alsa-sink.c: Calculated software volume: front-left: 65005 / 99% / -0,21 dB, front-right: 65005 / 99% / -0,21 dB (accurate-enough=yes) D: [alsa-sink-USB Audio] sink.c: Volume not changing D: [alsa-sink-USB Audio] alsa-sink.c: Requested to rewind 384000 bytes. D: [alsa-sink-USB Audio] alsa-sink.c: Limited to 5888 bytes. D: [alsa-sink-USB Audio] alsa-sink.c: before: 1472 D: [alsa-sink-USB Audio] alsa-sink.c: after: 1472 D: [alsa-sink-USB Audio] alsa-sink.c: Rewound 5888 bytes. D: [alsa-sink-USB Audio] sink.c: Processing rewind... D: [alsa-sink-USB Audio] sink.c: latency = 8085 D: [alsa-sink-USB Audio] source.c: Processing rewind... D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00.analog-stereo-output becomes idle, timeout in 5 seconds. D: [pulseaudio] core.c: Hmm, no streams around, trying to vacuum. I: [pulseaudio] sink-input.c: Freeing input 1 "Mixer Stream" I: [pulseaudio] protocol-native.c: Connection died. D: [pulseaudio] ratelimit.c: 110 events suppressed D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry) I: [pulseaudio] client.c: Freed 11 "FMOD Ex App" I: [pulseaudio] module-suspend-on-idle.c: Source alsa_input.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00.analog-stereo-input idle for too long, suspending ... D: [pulseaudio] source.c: Suspend cause of source alsa_input.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00.analog-stereo-input is 0x0004, suspending I: [alsa-source-USB Audio] alsa-source.c: Device suspended... D: [pulseaudio] core.c: Hmm, no streams around, trying to vacuum. I: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00.analog-stereo-output idle for too long, suspending ... D: [pulseaudio] sink.c: Suspend cause of sink alsa_output.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00.analog-stereo-output is 0x0004, suspending I: [alsa-sink-USB Audio] alsa-sink.c: Device suspended... D: [pulseaudio] core.c: Hmm, no streams around, trying to vacuum. D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC1 is accessible: yes D: [pulseaudio] module-udev-detect.c: Resuming all sinks and sources of card alsa_card.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X0Q6-00. ** Description changed: After recent update to 1.12 I'm getting issues with microphone: when using microphone in TeamSpeak 3 it only works for
[Desktop-packages] [Bug 1691549] [NEW] WIth recent update multiple applications have issues with mic
Public bug reported: After recent update to 1.12 I'm getting issues with microphone: when using microphone in TeamSpeak 3 it only works for few minutes, afterwards I can only hear, but not talk. Start Conflict game simply freezes at certain places. The only audio-related update I can find in recent days is gstreamer, but I can't yet find any patch for sources to see what was actually changed in recent update. ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: artful ** Tags added: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691549 Title: WIth recent update multiple applications have issues with mic Status in gstreamer1.0 package in Ubuntu: New Bug description: After recent update to 1.12 I'm getting issues with microphone: when using microphone in TeamSpeak 3 it only works for few minutes, afterwards I can only hear, but not talk. Start Conflict game simply freezes at certain places. The only audio-related update I can find in recent days is gstreamer, but I can't yet find any patch for sources to see what was actually changed in recent update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1691549/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
@simosx, I do not care what the hell is going on, I just know that Java- based and some other apps (can't recall the list right now) simply do not work like you say they are. They work on Windows and they work under X11 when I set languages with setxkbmap (for the last few years I use setxkbmap + gxkb for tray information about current layout exactly because of this issue, see https://bugs.launchpad.net/unity/+bug/1226962/comments/221). With setxkbmap everything just works perfectly in ANY APP I ever encounter. Which apparently means g-s-d or u-s-d or whatever will come with the next GNOME release (probably will be moved to Mutter as everything else these days) is the root cause of the issue. And GNOME should be fixed, not every app in this universe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in openjdk-7 source package in Xenial: Incomplete Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
@simosx take any Java app or an app that didn't add workarounds (Gedit was one of the first where it was fixed) and use Ctrl+C on Cyrillic layout (Ukrainian as an example). I wouldn't work even on 17.04. So yes, there are apps (many of them listed in this issue) that kind of fixed it, but the root cause is the GNOME stack and it was not fixed and even not going to be fixed ever (I can't find relevant upstream issue right now, but it was closed as not a bug). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in openjdk-7 source package in Xenial: Incomplete Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
When was it fixed in GNOME? I was using gnome-settings-daemon's keyboard handling till ~3.18 and it didn't work since the moment they break it. I do not want to reconfigure system right now, but I'm pretty sure it wasn't fixed, just various GNOME apps were patched with workarounds, while generally issue is still there and it seems like will never be fixed at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in openjdk-7 source package in Xenial: Incomplete Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
It happened in gnome-settings-daemon first and then appeared in u-s-d, so this is GNOME-specific issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in openjdk-7 source package in Xenial: Incomplete Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
My first language is EN, doens't help. Migration FROM GNOME will help, because GNOME stack is the root cause of this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in openjdk-7 source package in Xenial: Incomplete Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1647159] Re: Steam can't install/update itself or any games (zesty)
This one was actually fixed a while ago, so I'm closing it. ** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- 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/1647159 Title: Steam can't install/update itself or any games (zesty) Status in network-manager package in Ubuntu: Fix Released Bug description: Today I've noticed that Steam can't install/update anything. For instance, when running steam for the first time I'm getting: > Fatal Error: Steam needs to be online to update. Please confirm your network connection and try again. I've seen DNS-related updated recently, they might be a reason for this issue. I don't have any issues in browsers though. Workaround is to change `127.0.0.53` to `8.8.8.8` in `/etc/resolv.conf` manually. I'm connected to the Internet via router using Ethernet cable and I've manually specified DNS servers `8.8.8.8` and `8.8.4.4` in nm-applet's (I believe it is an applet) GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647159/+subscriptions -- Mailing list: https://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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file
@davidak, you might need to build Nvidia module with dkms manually (it fails building automatically for me too more often than not). You can do this like following: sudo dkms install -k 4.10.0-11-generic -m nvidia-378/378.13 Just replace kernel version and Nvidia driver version with what you have currently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1369216 Title: gpu-manager: /etc/modprobe.d is not a file Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Get these lines logged into gpu-manager.log, on that fresh stock installation /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 14 08:42:45 2014 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.default.whoopsie: [modified] modified.conffile..etc.gdm.Init.Default: [modified] mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075 mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1369216/+subscriptions -- Mailing list: https://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 1663227] Re: gnome-settings-daemon not installed
Closing after finding out https://bugs.launchpad.net/ubuntu/+source /gnome-settings-daemon/+bug/1662647 ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Invalid -- 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/1663227 Title: gnome-settings-daemon not installed Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: gnome-settings-daemon package is installed, but binary is not present! This happened around 2 days ago after updating to 3.23.3 on Zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1663227/+subscriptions -- Mailing list: https://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 1663227] Re: gnome-settings-daemon not installed
nazar-pc ~ cat /etc/xdg/autostart/gnome-settings-daemon.desktop [Desktop Entry] Type=Application Name=GNOME Settings Daemon Exec=/usr/lib/gnome-settings-daemon/gnome-settings-daemon-localeexec OnlyShowIn=GNOME; NoDisplay=true X-GNOME-Autostart-Phase=Initialization X-GNOME-Autostart-Notify=true X-GNOME-AutoRestart=true X-Ubuntu-Gettext-Domain=gnome-settings-daemon nazar-pc ~ ls /usr/lib/gnome-settings-daemon/ gsd-a11y-keyboard* gsd-locate-pointer* gsd-smartcard* gsd-a11y-settings* gsd-media-keys* gsd-sound* gsd-backlight-helper* gsd-mouse*gsd-test-input-helper* gsd-clipboard* gsd-orientation* gsd-test-wacom-osd* gsd-color* gsd-power*gsd-wacom* gsd-datetime* gsd-printer* gsd-wacom-led-helper* gsd-dummy* gsd-print-notifications* gsd-wacom-oled-helper* gsd-housekeeping* gsd-rfkill* gsd-xrandr* gsd-keyboard* gsd-screensaver-proxy*gsd-xsettings* gsd-list-wacom*gsd-sharing* nazar-pc ~ apt-cache show gnome-settings-daemon Package: gnome-settings-daemon Priority: extra Section: universe/gnome Installed-Size: 1685 Maintainer: Ubuntu Desktop Team Original-Maintainer: Debian GNOME Maintainers Architecture: amd64 Version: 3.23.3-0ubuntu1 Depends: libaccountsservice0 (>= 0.6.40), libasound2 (>= 1.0.16), libc6 (>= 2.14), libcairo2 (>= 1.10.0), libcanberra-gtk3-0 (>= 0.25), libcanberra0 (>= 0.2), libcolord2 (>= 1.2.0), libcups2 (>= 1.6.0), libfontconfig1 (>= 2.11.94), libgdk-pixbuf2.0-0 (>= 2.22.0), libgeoclue-2-0 (>= 2.4.0), libgeocode-glib0 (>= 0.99.1), libglib2.0-0 (>= 2.43.92), libgnome-desktop-3-12 (>= 3.17.92), libgtk-3-0 (>= 3.16.2), libgudev-1.0-0 (>= 146), libgweather-3-6 (>= 3.10.0), liblcms2-2 (>= 2.2+git20110628), libnm0 (>= 1.0.0), libnotify4 (>= 0.7.3), libnspr4 (>= 2:4.9-2~), libnss3 (>= 2:3.13.4-2~), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 1.14.0), libpolkit-gobject-1-0 (>= 0.99), libpulse-mainloop-glib0 (>= 0.99.1), libpulse0 (>= 0.99.1), librsvg2-2 (>= 2.36.2), libupower-glib3 (>= 0.99.0), libwacom2 (>= 0.7), libwayland-client0 (>= 1.0.2), libx11-6, libxext6, libxi6 (>= 2:1.2.99.4), libxtst6, libpam-systemd, gnome-settings-daemon-schemas (= 3.23.3-0ubuntu1), gsettings-desktop-schemas (>= 3.20), nautilus-data (>= 2.91.3-1) Recommends: pulseaudio, iio-sensor-proxy Breaks: budgie-core (<< 10.2.9-2ubuntu2~), gnome-control-center (<< 1:3.15.4), gnome-session (<< 3.23.2), gnome-shell (<< 3.13.92) Filename: pool/universe/g/gnome-settings-daemon/gnome-settings-daemon_3.23.3-0ubuntu1_amd64.deb Size: 372240 MD5sum: 8616100b68f2640d520cefeaf519ca74 SHA1: fcebf2331a1266646c94bbdd866f6e12b63604be SHA256: e21fe05b7834f0a8173ddb8193da4178039349508edc9d7417586fef3e0cbb18 Description-en_GB: daemon handling the GNOME session settings This package contains the daemon which is responsible for setting the various parameters of a GNOME session and the applications that run under it. It handles the following kinds of settings: . * Keyboard: layout, accessibility options, shortcuts, media keys * Clipboard management * Theming: background, icons, GTK+ applications * Cleanup of unused files * Mouse: cursors, speed, accessibility options * Startup of other daemons: screensaver, sound daemon . It also sets various application settings through X resources and freedesktop.org XSETTINGS. Description-md5: 31f06b20f036e71da14412083d98ad89 Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: edubuntu-desktop-gnome, ubuntu-gnome-desktop, ubuntu-budgie-desktop -- 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/1663227 Title: gnome-settings-daemon not installed Status in gnome-settings-daemon package in Ubuntu: New Bug description: gnome-settings-daemon package is installed, but binary is not present! This happened around 2 days ago after updating to 3.23.3 on Zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1663227/+subscriptions -- Mailing list: https://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 1663227] [NEW] gnome-settings-daemon not installed
Public bug reported: gnome-settings-daemon package is installed, but binary is not present! This happened around 2 days ago after updating to 3.23.3 on Zesty. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: zesty -- 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/1663227 Title: gnome-settings-daemon not installed Status in gnome-settings-daemon package in Ubuntu: New Bug description: gnome-settings-daemon package is installed, but binary is not present! This happened around 2 days ago after updating to 3.23.3 on Zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1663227/+subscriptions -- Mailing list: https://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 1647159] [NEW] Steam can't install/update itself or any games (zesty)
Public bug reported: Today I've noticed that Steam can't install/update anything. For instance, when running steam for the first time I'm getting: > Fatal Error: Steam needs to be online to update. Please confirm your network > connection and try again. I've seen DNS-related updated recently, they might be a reason for this issue. I don't have any issues in browsers though. Workaround is to change `127.0.0.53` to `8.8.8.8` in `/etc/resolv.conf` manually. I'm connected to the Internet via router using Ethernet cable and I've manually specified DNS servers `8.8.8.8` and `8.8.4.4` in nm-applet's (I believe it is an applet) GUI. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: zesty -- 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/1647159 Title: Steam can't install/update itself or any games (zesty) Status in network-manager package in Ubuntu: New Bug description: Today I've noticed that Steam can't install/update anything. For instance, when running steam for the first time I'm getting: > Fatal Error: Steam needs to be online to update. Please confirm your network connection and try again. I've seen DNS-related updated recently, they might be a reason for this issue. I don't have any issues in browsers though. Workaround is to change `127.0.0.53` to `8.8.8.8` in `/etc/resolv.conf` manually. I'm connected to the Internet via router using Ethernet cable and I've manually specified DNS servers `8.8.8.8` and `8.8.4.4` in nm-applet's (I believe it is an applet) GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647159/+subscriptions -- Mailing list: https://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 1616283] Re: gnome-settings-daemon doesn't work properly in Ubuntu under LightDM
All that functionality is now in Mutter, so it is a huge monolith that is not expected to work separately. gnome-fallback-media-keys-helper from Zorin OS ppa work for keyboard, didn't found good replacement for the rest of stuff. ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => Invalid -- 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/1616283 Title: gnome-settings-daemon doesn't work properly in Ubuntu under LightDM Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: When using gnome-settings-daemon instead of unity-settings-daemon (for instance, in custom session) it doesn't work properly, namely, at least following things are broken: * hotkeys (including multimedia keys) * displays management (gnome-control-center says no displays found) * laptop blacklight management (when changing brightness level in gnome-control-center it doesn't have any effect) Those are the first things I've noticed. However, Bluetooth, Wi-Fi and sound settings seems to work. I'm on Xenial right now. xsession: [Desktop Entry] Name=Custom session Comment=Custom session Exec=/usr/lib/gnome-session/run-systemd-session custom-session.target TryExec=compiz Icon= Type=Application DesktopNames=GNOME X-Ubuntu-Gettext-Domain=gnome-session-3.0 gnome-session: [GNOME Session] Name=Custom RequiredComponents=gnome-settings-daemon;compiz;plank;wingpanel; DesktopName=Custom custom-session.target (the same as ubuntu-session.target): [Unit] Description=User systemd services for the Ubuntu graphical session # start/tear down graphical-session.target along with the ubuntu session BindsTo=graphical-session.target # session leader -- if this dies, die along with it BindsTo=gnome-session.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1616283/+subscriptions -- Mailing list: https://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 1622772] Re: gnome-session-properties icons and .desktop file should be moved to gnome-session-bin
My issue is only to keep system clean. There are some components in my system that depend on gnome-session-bin, but not gnome-session-common. And I'm trying to decrease number of manually installed packages to bare minimum. Stuff in gnome-session-common are really tiny and I see no practical benefit in having them separated. Probably, better option might be to add a recommended dependency on gnome-session-common in gnome-session-bin. There is no big technical problems, it just doesn't feel clean enough. Just to mention, for me gnome-session-properties does not feel required in gnome-session-bin either, so perfect solution for me would be to have gnome-session-properties package with everything necessary inside. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1622772 Title: gnome-session-properties icons and .desktop file should be moved to gnome-session-bin Status in gnome-session package in Ubuntu: New Bug description: gnome-session-bin package includes gnome-session-properties binary. However, gnome-session-properties's .desktop file and icons are all in gnome-session-common, which is the only reason I have gnome-session-common installed in my system. So I think those files should be restructured differently, possibly, moved to gnome-session-bin package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1622772/+subscriptions -- Mailing list: https://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 1622772] [NEW] gnome-session-properties icons and .desktop file should be moved to gnome-session-bin
Public bug reported: gnome-session-bin package includes gnome-session-properties binary. However, gnome-session-properties's .desktop file and icons are all in gnome-session-common, which is the only reason I have gnome-session-common installed in my system. So I think those files should be restructured differently, possibly, moved to gnome-session-bin package. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1622772 Title: gnome-session-properties icons and .desktop file should be moved to gnome-session-bin Status in gnome-session package in Ubuntu: New Bug description: gnome-session-bin package includes gnome-session-properties binary. However, gnome-session-properties's .desktop file and icons are all in gnome-session-common, which is the only reason I have gnome-session-common installed in my system. So I think those files should be restructured differently, possibly, moved to gnome-session-bin package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1622772/+subscriptions -- Mailing list: https://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 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
Thanks quequotion, works wonderfully! Do you know something else that can be used as an alternative for gnome-fallback-media-keys-helper? (it is only present for Saucy release in Zorin OS ppa, which is not very reliable in long-term). -- 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/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+subscriptions -- Mailing list: https://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 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
I have similar problem now on Xenial, but literally all hotkeys are not working. I can assign them on gnome-control-center, but can't trigger real actions afterward. I'm only using Compiz (no unity, no gnome-shell). Is there any workaround for this issue? -- 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/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+subscriptions -- Mailing list: https://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 1616283] [NEW] gnome-settings-daemon doesn't work properly in Ubuntu under LightDM
Public bug reported: When using gnome-settings-daemon instead of unity-settings-daemon (for instance, in custom session) it doesn't work properly, namely, at least following things are broken: * hotkeys (including multimedia keys) * displays management (gnome-control-center says no displays found) * laptop blacklight management (when changing brightness level in gnome-control-center it doesn't have any effect) Those are the first things I've noticed. However, Bluetooth, Wi-Fi and sound settings seems to work. I'm on Xenial right now. xsession: [Desktop Entry] Name=Custom session Comment=Custom session Exec=/usr/lib/gnome-session/run-systemd-session custom-session.target TryExec=compiz Icon= Type=Application DesktopNames=GNOME X-Ubuntu-Gettext-Domain=gnome-session-3.0 gnome-session: [GNOME Session] Name=Custom RequiredComponents=gnome-settings-daemon;compiz;plank;wingpanel; DesktopName=Custom custom-session.target (the same as ubuntu-session.target): [Unit] Description=User systemd services for the Ubuntu graphical session # start/tear down graphical-session.target along with the ubuntu session BindsTo=graphical-session.target # session leader -- if this dies, die along with it BindsTo=gnome-session.service ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/1616283 Title: gnome-settings-daemon doesn't work properly in Ubuntu under LightDM Status in gnome-settings-daemon package in Ubuntu: New Bug description: When using gnome-settings-daemon instead of unity-settings-daemon (for instance, in custom session) it doesn't work properly, namely, at least following things are broken: * hotkeys (including multimedia keys) * displays management (gnome-control-center says no displays found) * laptop blacklight management (when changing brightness level in gnome-control-center it doesn't have any effect) Those are the first things I've noticed. However, Bluetooth, Wi-Fi and sound settings seems to work. I'm on Xenial right now. xsession: [Desktop Entry] Name=Custom session Comment=Custom session Exec=/usr/lib/gnome-session/run-systemd-session custom-session.target TryExec=compiz Icon= Type=Application DesktopNames=GNOME X-Ubuntu-Gettext-Domain=gnome-session-3.0 gnome-session: [GNOME Session] Name=Custom RequiredComponents=gnome-settings-daemon;compiz;plank;wingpanel; DesktopName=Custom custom-session.target (the same as ubuntu-session.target): [Unit] Description=User systemd services for the Ubuntu graphical session # start/tear down graphical-session.target along with the ubuntu session BindsTo=graphical-session.target # session leader -- if this dies, die along with it BindsTo=gnome-session.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1616283/+subscriptions -- Mailing list: https://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 981149] Re: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
100% reproducible on Yakkety: 0. I have USB sound card Creative SB Omni Surround 5.1 (works in stereo and 5.1 output modes) 1. Current mode is stereo 2. Play song in Clementine (current exact version is 1.3.1-209-g1f95a23) 3. Decrease system volume slightly 4. Change output mode to 5.1 5. PulseAudio crashes in 100% of cases ** Tags added: yakkety -- 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/981149 Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() Status in pulseaudio package in Ubuntu: Triaged Bug description: When I switch between my headphones and/or my Logitech lap desk N700 speakers the sound will crash. I usually have to restart my laptop to get everything to work again. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 6394 F pulseaudio /dev/snd/controlC0: mark 6394 F pulseaudio /dev/snd/pcmC0D0p: mark 6394 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 49' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1179ff02,0013 HDA:11c11040,11790001,00100200' Controls : 16 Simple ctrls : 9 Card1.Amixer.info: Card hw:1 'N700'/'Logitech Logitech Speaker Lapdesk N700 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:0a1a' Controls : 2 Simple ctrls : 1 Date: Fri Apr 13 16:28:44 2012 ExecutablePath: /usr/bin/pulseaudio InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 pa_sink_input_finish_move () from /usr/lib/libpulsecore-1.1.so pa_sink_move_all_finish () from /usr/lib/libpulsecore-1.1.so ?? () from /usr/lib/pulse-1.1/modules/module-alsa-card.so Title: pulseaudio crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 08/28/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.60 dmi.board.name: ISKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.60:bd08/28/2008:svnTOSHIBA:pn*:pvr*:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: * dmi.product.version: * dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/981149/+subscriptions -- Mailing list: https://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 1348070] Re: unity-control-center crashed with SIGABRT in g_assertion_message()
Crash happened on switching sound card in audio settings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1348070 Title: unity-control-center crashed with SIGABRT in g_assertion_message() Status in unity-control-center package in Ubuntu: Confirmed Bug description: Crashed while trying to re-authenticate my Yahoo! account in Online Account. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-control-center 14.10.0+14.10.20140702.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic i686 ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Jul 24 03:44:02 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-07-17 (7 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140522) ProcCmdline: unity-control-center --overview Signal: 6 SourcePackage: unity-control-center StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/empathy/libempathy-3.8.6.so g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: unity-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1348070/+subscriptions -- Mailing list: https://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 1041551] Re: No interface after updating to mesa 9.0 in Quantal (Mesa 8.0.4 works)
I guess you've installed them using dpkg without upgrading the rest of mesa stack ignoring some possible linux kernel requirements. No surprise that it doesn't work for you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1041551 Title: No interface after updating to mesa 9.0 in Quantal (Mesa 8.0.4 works) Status in mesa package in Ubuntu: Invalid Bug description: Totay after updating from mesa packages of version 8.0.4-1ubuntu1 to 9.0-git20120821.c1114c61-0ubuntu1 and restarting system I observed no titles on windows, no unity panel, dash, even no shortcuts on desktop - only background and windows of automatically started programs without frames. Ctrl+Alt+T command doesn't works too. Looks like compiz doesn't works at all. After manual roll back to version 8.0.4-1ubuntu1 of next packages: libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglu1-mesa libosmesa6 libxatracker1 System again works fine. My video card Radeon HD5450, all packages of the latest versions of Ubuntu 12.10 Quantal. --- ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 12.10 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) Package: linux (not installed) ProcEnviron: LANGUAGE=ru_UA:ru TERM=xterm PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash Tags: quantal running-unity Uname: Linux 3.6.0-rc2-bulldozer-xen-pci x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to quantal on 2012-06-28 (57 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1041551/+subscriptions -- Mailing list: https://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 1041551] Re: No interface after updating to mesa 9.0 in Quantal (Mesa 8.0.4 works)
I do not think anyone will care about packages from Trusty/Xenial not working in Precise. They are not expected to work, so upgrade to newer LTS release if you want newer Mesa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1041551 Title: No interface after updating to mesa 9.0 in Quantal (Mesa 8.0.4 works) Status in mesa package in Ubuntu: Invalid Bug description: Totay after updating from mesa packages of version 8.0.4-1ubuntu1 to 9.0-git20120821.c1114c61-0ubuntu1 and restarting system I observed no titles on windows, no unity panel, dash, even no shortcuts on desktop - only background and windows of automatically started programs without frames. Ctrl+Alt+T command doesn't works too. Looks like compiz doesn't works at all. After manual roll back to version 8.0.4-1ubuntu1 of next packages: libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglu1-mesa libosmesa6 libxatracker1 System again works fine. My video card Radeon HD5450, all packages of the latest versions of Ubuntu 12.10 Quantal. --- ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 12.10 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) Package: linux (not installed) ProcEnviron: LANGUAGE=ru_UA:ru TERM=xterm PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash Tags: quantal running-unity Uname: Linux 3.6.0-rc2-bulldozer-xen-pci x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to quantal on 2012-06-28 (57 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1041551/+subscriptions -- Mailing list: https://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 1539700] Re: gst-base 1.7 update created background buzzing noise with audioconvert
I can confirm, downgraded package to 1.6.3-1ubuntu1 and Clementine now plays fine. -- 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/1539700 Title: gst-base 1.7 update created background buzzing noise with audioconvert Status in gst-plugins-base: Confirmed Status in alsa-driver package in Ubuntu: Invalid Status in goobox package in Ubuntu: Invalid Status in gst-plugins-base1.0 package in Ubuntu: Triaged Bug description: Also affects cdplayer (goobox). Is not seen in audacious or vlc at all (using default audio of pulse Test case: insert audio cd, play in rhymbox or cdplayer What happens: significant background buzzing May be gstreamer issue? Attached is simple recording of what Rb is outputting. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-1.15-generic 4.4.0 Uname: Linux 4.4.0-1-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1652 F pulseaudio /dev/snd/pcmC1D0p: doug 1652 F...m pulseaudio /dev/snd/controlC1: doug 1652 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 12:00:33 2016 InstallationDate: Installed on 2016-01-14 (14 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160114) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20217, Realtek ALC282, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/1539700/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout
Dear Ubuntu developers, FIX THIS ISSUE, please! It is ridiculously stupid that every single application should do something special to support hotkeys, it should just work out of the box as it forked for many years before. I've tired to explain to many people how to get rid of unity-settings-daemon plugin and use setxkbmap instead! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in openjdk-7 source package in Xenial: Incomplete Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: Triaged Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1310489] Re: xorg.conf overwritten by booting system
Looks like one more plymouth update fixed and issue, sorry for bothering. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in Linux Mint: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error --> "AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]" but it changed not the bug of overwriting the xorg.conf. Regards, Uwe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1985 dmi.board.vendor: Hewlett-Packard dmi.board.version: 01.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.ver
[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system
Just noticed that on Ubuntu 16.04 xorg.conf is actually removed on restart, which is why I'm always loaded with Intel driver instead of Nvidia on my laptop. This happened within updated during last 2 days, everything worked fine before. What happens, why file is REMOVED? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in Linux Mint: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error --> "AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]" but it changed not the bug of overwriting the xorg.conf. Regards, Uwe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.boa
[Desktop-packages] [Bug 1500498] Re: PulseAudio 7
PulseAudio 7.1 already available in xenial ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- 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/1500498 Title: PulseAudio 7 Status in pulseaudio package in Ubuntu: Fix Released Bug description: PulseAudio 7 was released a while ago and brings some nice improvements and fixes, would be great to see it in Ubuntu soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1500498/+subscriptions -- Mailing list: https://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 1502717] Re: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
Error happens after wake-up from sleep mode and on reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1502717 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Confirmed Bug description: wpa_supplicant crashed with SIGSEGV when removing kernel module brcmfmac. rsalveti@evapro:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 Codename: wily Linux evapro 4.2.0-14-generic #16-Ubuntu SMP Fri Oct 2 05:14:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux MacBook Pro Retina 13' 12,1 43557 Oct 4 18:02:56 evapro kernel: [ 86.406354] usbcore: deregistering interface driver brcmfmac 43558 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing workstation service for wlp3s0. 43559 Oct 4 18:02:57 evapro NetworkManager[936]: devices removed (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlp3s0, iface: wlp3s0) 43560 Oct 4 18:02:57 evapro NetworkManager[936]: (wlp3s0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36] 43561 Oct 4 18:02:57 evapro NetworkManager[936]: (wlp3s0): failed to disable userspace IPv6LL address handling 43562 Oct 4 18:02:57 evapro gnome-session[2190]: (nm-applet:2346): GLib-CRITICAL **: Source ID 190 was not found when attempting to remove it 43563 Oct 4 18:02:57 evapro NetworkManager[936]: radio killswitch /sys/devices/pci:00/:00:1c.2/:03:00.0/ieee80211/phy0/rfkill0 disappeared 43564 Oct 4 18:02:57 evapro kernel: [ 86.947963] show_signal_msg: 39 callbacks suppressed 43565 Oct 4 18:02:57 evapro kernel: [ 86.947968] wpa_supplicant[1330]: segfault at 0 ip 7f835170fcba sp 7fffc00140c8 error 4 in libc-2.21.so[7f835167+1c] 43566 Oct 4 18:02:57 evapro NetworkManager[936]: wpa_supplicant stopped 43567 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): supplicant interface state: completed -> down 43568 Oct 4 18:02:57 evapro NetworkManager[936]: (NetworkManager:936): GLib-CRITICAL **: Source ID 167 was not found when attempting to remove it 43569 Oct 4 18:02:57 evapro NetworkManager[936]: Failed to GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.30 was not provided by any .service files: remove network. 43570 Oct 4 18:02:57 evapro dbus[969]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' 43571 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): device state change: activated -> unavailable (reason 'supplicant-failed') [100 20 10] 43572 Oct 4 18:02:57 evapro systemd[1]: Started WPA supplicant. 43573 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): canceled DHCP transaction, DHCP client pid 1915 43574 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): DHCPv4 state changed bound -> done 43575 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing address record for 192.168.1.17 on wlx048d38ab601a. 43576 Oct 4 18:02:57 evapro avahi-daemon[950]: Leaving mDNS multicast group on interface wlx048d38ab601a.IPv4 with address 192.168.1.17. 43577 Oct 4 18:02:57 evapro avahi-daemon[950]: Interface wlx048d38ab601a.IPv4 no longer relevant for mDNS. 43578 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing address record for fe80::68d:38ff:feab:601a on wlx048d38ab601a. 43579 Oct 4 18:02:57 evapro avahi-daemon[950]: Leaving mDNS multicast group on interface wlx048d38ab601a.IPv6 with address fe80::68d:38ff:feab:601a. 43580 Oct 4 18:02:57 evapro avahi-daemon[950]: Interface wlx048d38ab601a.IPv6 no longer relevant for mDNS. 43581 Oct 4 18:02:57 evapro NetworkManager[936]: Writing DNS information to /sbin/resolvconf 43582 Oct 4 18:02:57 evapro dnsmasq[1607]: setting upstream servers from DBus 43583 Oct 4 18:02:57 evapro dnsmasq[1607]: using nameserver fe80::e6f4:c6ff:fe0b:5c4d#53 43584 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] Cannot reach: https://daisy.ubuntu.com 43585 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] offline 43586 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] Cannot reach: https://daisy.ubuntu.com 43587 Oct 4 18:02:57 evapro NetworkManager[936]: Writing DNS information to /sbin/resolvconf 43588 Oct 4 18:02:57 evapro dnsmasq[1607]: setting upstream servers from DBus 43589 Oct 4 18:02:57 evapro NetworkManager[936]: NetworkManager state is now CONNECTED_LOCAL 43590 Oct 4 18:02:57 evapro NetworkManager[936]: NetworkManager state is now DISCONNECTED 43591 Oct 4 18:02:57 evapro nm-dispatcher: Dispatching action 'down' for wlx048d38ab601a 43592 Oct 4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Main process exited, code=dumped, status=11/SEGV 43593
[Desktop-packages] [Bug 1500498] Re: PulseAudio 7
Thanks, I've just installed, works good so far. -- 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/1500498 Title: PulseAudio 7 Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio 7 was released a while ago and brings some nice improvements and fixes, would be great to see it in Ubuntu soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1500498/+subscriptions -- Mailing list: https://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 1500498] Re: PulseAudio 7
What about creating ppa for those who want to test it earlier? Unfortunately I have no experience with that myself. -- 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/1500498 Title: PulseAudio 7 Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio 7 was released a while ago and brings some nice improvements and fixes, would be great to see it in Ubuntu soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1500498/+subscriptions -- Mailing list: https://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 1500498] Re: PulseAudio 7
Yes, I saw on mailing list that it was packaged for Debian unstable, but Ubuntu have own set of Ubuntu-specific patches at least. I'm not sure how crucial they are, so I'm not even trying to install Debian packages on my Wily. -- 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/1500498 Title: PulseAudio 7 Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio 7 was released a while ago and brings some nice improvements and fixes, would be great to see it in Ubuntu soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1500498/+subscriptions -- Mailing list: https://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 1500498] [NEW] PulseAudio 7
Public bug reported: PulseAudio 7 was released a while ago and brings some nice improvements and fixes, would be great to see it in Ubuntu soon. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1500498 Title: PulseAudio 7 Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio 7 was released a while ago and brings some nice improvements and fixes, would be great to see it in Ubuntu soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1500498/+subscriptions -- Mailing list: https://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 1492144] Re: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
For me it happens every time after wake up from sleep mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Invalid Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+subscriptions -- Mailing list: https://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 1296114] Re: [desktop] Bluetooth is always enabled after reboot even if it was disabled
Just ping to fix this annoying bug finally, should not be difficult. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1296114 Title: [desktop] Bluetooth is always enabled after reboot even if it was disabled Status in Bluetooth Menu: Invalid Status in indicator-bluetooth package in Ubuntu: Invalid Status in rfkill package in Ubuntu: Incomplete Status in urfkill package in Ubuntu: Triaged Bug description: If bluetooth was disabled using the switcher in the bluetooth indicator, after reboot it becomes enabled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 22 22:34:52 2014 InstallationDate: Installed on 2014-01-27 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: Connecting to session manager To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+subscriptions -- Mailing list: https://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 1425334] [NEW] Crackling when increasing default-sample-rate
Public bug reported: I'm on Ubuntu 15.04 x64. Just bought Creative Sound Blaster Omni Surround 5.1 USB sound card which is capable of 24bit 96kHz. I'm editing sudo gedit /etc/pulse/daemon.conf changing: default-sample-format = s24le default-sample-rate = 96000 When I put first line everything is fine, while I'm putting second, even 192000 - I'm getting random crackling all the time when something is playing. Without second line everything works fine. I've tried many tricks found in Internet, different kernels (stock 3.18, manually compiled 3.19.0 and 4.0-rc1) - the same result everywhere. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1425334 Title: Crackling when increasing default-sample-rate Status in pulseaudio package in Ubuntu: New Bug description: I'm on Ubuntu 15.04 x64. Just bought Creative Sound Blaster Omni Surround 5.1 USB sound card which is capable of 24bit 96kHz. I'm editing sudo gedit /etc/pulse/daemon.conf changing: default-sample-format = s24le default-sample-rate = 96000 When I put first line everything is fine, while I'm putting second, even 192000 - I'm getting random crackling all the time when something is playing. Without second line everything works fine. I've tried many tricks found in Internet, different kernels (stock 3.18, manually compiled 3.19.0 and 4.0-rc1) - the same result everywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425334/+subscriptions -- Mailing list: https://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 1234306] Re: Dark squares of the same time appears at the left side of sceen
No ** Changed in: unity Status: Incomplete => Fix Released ** Changed in: unity (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1234306 Title: Dark squares of the same time appears at the left side of sceen Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Squares are dark, I think I is connected with dark theme I use (Boje Greyscale). Squares appears randomly, but frequently enough, and always near left edge. Attached file shows how it looks like. I'm ready to make some checks to define what is the source of it. One more detail - square disappears on mouse over or (sometimes, not always) at changing of active desktop (I'm using 3D Cube plugin with rotating). I can even record video - just to speed up solving of this annoying bug. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1234306/+subscriptions -- Mailing list: https://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 1397133] Re: unity-settings-daemon killed with ABRT
** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => Fix Released -- 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/1397133 Title: unity-settings-daemon killed with ABRT Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: Just get update of unity-settings-daemon and systemd-related packages on Vivid and unity-settings-daemon crashes every few seconds. ~/.xsession-errors: upstart: Process unity-settings-daemon main (13298) killed with signal ABRT upstart: Process unity-settings-daemon main ended and restarting (two lines translated because my system interface is not English) This also resets my theme to Ambiance and resets look of gnome- terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1397133/+subscriptions -- Mailing list: https://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 1397133] [NEW] unity-settings-daemon killed with ABRT
Public bug reported: Just get update of unity-settings-daemon and systemd-related packages on Vivid and unity-settings-daemon crashes every few seconds. ~/.xsession-errors: upstart: Process unity-settings-daemon main (13298) killed with signal ABRT upstart: Process unity-settings-daemon main ended and restarting (two lines translated because my system interface is not English) This also resets my theme to Ambiance and resets look of gnome-terminal ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: vivid -- 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/1397133 Title: unity-settings-daemon killed with ABRT Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Just get update of unity-settings-daemon and systemd-related packages on Vivid and unity-settings-daemon crashes every few seconds. ~/.xsession-errors: upstart: Process unity-settings-daemon main (13298) killed with signal ABRT upstart: Process unity-settings-daemon main ended and restarting (two lines translated because my system interface is not English) This also resets my theme to Ambiance and resets look of gnome- terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1397133/+subscriptions -- Mailing list: https://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 1131835] Re: compiz crashed with SIGABRT in __libc_message()
Wanted to minimize gedit 3.12.2 on Utopic, and it cashed, redirected me here. -- 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/1131835 Title: compiz crashed with SIGABRT in __libc_message() Status in Compiz: Triaged Status in “compiz” package in Ubuntu: Triaged Bug description: . ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: compiz-core 1:0.9.9~daily13.02.19-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Fri Feb 22 17:37:21 2013 DistUpgraded: 2013-01-19 22:44:58,817 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1252] NVIDIA Corporation GT216 [GeForce GT 325M] [10de:0a35] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1252] InstallationDate: Installed on 2013-01-19 (33 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: ASUSTeK Computer INC. N61Jv MarkForUpload: True ProcCmdline: compiz ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=f31b5c33-9c96-4314-8609-281abe7a54b8 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: compiz StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 Title: compiz crashed with SIGABRT in raise() UpgradeStatus: Upgraded to raring on 2013-01-19 (33 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (gnome-settings-daemon:1927): color-plugin-WARNING **: failed to reset xrandr-HSD160PHW1-1162 gamma tables: gamma size is zero gnome-session[1855]: WARNING: Application 'compiz.desktop' killed by signal 6 gnome-session[1855]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[1855]: CRITICAL: We failed, but the fail whale is dead. Sorry dmi.bios.date: 01/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N61Jv dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr208:bd01/28/2010:svnASUSTeKComputerINC.:pnN61Jv:pvr1.0:rvnASUSTeKComputerINC.:rnN61Jv:rvr1.0:cvnASUSTeKComputerINC.:ct10:cvr1.0: dmi.product.name: N61Jv dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 xserver.bootTime: Fri Feb 22 17:29:37 2013 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1131835/+subscriptions -- Mailing list: https://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 231385] Re: EOG opens images with 99% zoom (blurry) instead of 100%
Posted bug on their bugzilla, please, add your vote there https://bugzilla.gnome.org/show_bug.cgi?id=733290 ** Bug watch added: GNOME Bug Tracker #733290 https://bugzilla.gnome.org/show_bug.cgi?id=733290 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/231385 Title: EOG opens images with 99% zoom (blurry) instead of 100% Status in Eye of GNOME: Fix Released Status in “eog” package in Ubuntu: Fix Released Bug description: the images which can fit the eog window with 100% zoom will be opened with 99% zoom - seem blurry, the eog windows must be resized each time. To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/231385/+subscriptions -- Mailing list: https://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 1296487] Re: Initial zoom level is slightly under 100%
Posted bug on their bugzilla, please, add your vote there https://bugzilla.gnome.org/show_bug.cgi?id=733290 ** Bug watch added: GNOME Bug Tracker #733290 https://bugzilla.gnome.org/show_bug.cgi?id=733290 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in “eog” package in Ubuntu: Confirmed Bug description: When opening an image, the zoom level is displayed as 100%, but the image is visibly blurry from being slightly zoomed out. There are a few pixels of black bar on the right and left edges of the image. Expanding the window vertically lets the image display at 1:1 zoom. This occurs with images that should be small enough to be displayed at 100% zoom. For example: a 960x540 image on a 1920x1080 display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 18:06:29 2014 InstallationDate: Installed on 2014-02-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1296487/+subscriptions -- Mailing list: https://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 231385] Re: EOG opens images with 99% zoom (blurry) instead of 100%
Still not fixed! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/231385 Title: EOG opens images with 99% zoom (blurry) instead of 100% Status in Eye of GNOME: Fix Released Status in “eog” package in Ubuntu: Fix Released Bug description: the images which can fit the eog window with 100% zoom will be opened with 99% zoom - seem blurry, the eog windows must be resized each time. To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/231385/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
I think it works only under X, that is why the name setxkbmap from X keyboard. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “openjdk-7” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1325251] Re: Lock file exists after closing
I'm on Ubuntu 14.10 now and gksu version is 2.0.2-6ubuntu2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gksu in Ubuntu. https://bugs.launchpad.net/bugs/1325251 Title: Lock file exists after closing Status in “gksu” package in Ubuntu: New Bug description: When I run gksu executed first time - everything fine. After first run .gksu.lock appeared in home directory. And until I remove .gksu.lock file it doesn't work anymore, after removing this file it works exactly one more time, and stop working again. Ubuntu 14.10 right now, but as I remember was the same on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1325251/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
Actually they live in parallel realities, so switching of layout and indicator are in sync only if you use the same layout in all windows (I don't). As for gXneur: 1) Run gXneur with gxneur -E AppIndicator Then go to settings and press "Save" to make this icon rendering engine permanent - should work fine 2) Enable manual switching on first tab of settings 3) Troubleshooting -> Tracking input -> Monitor the input Uncheck this too to avoid duplication of printed symbols and similar bugs. gXneur do not work properly, but as layout indicator it works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in Aptana Studio Installer: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “openjdk-7” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
Awesome news! I found fix for this. 1) Disable of gnome control over keyboard: gsettings set org.gnome.settings-daemon.plugins.keyboard active false 2) Set desired settings for xkb: setxkbmap -option grp:rctrl_toggle,lv3:menu_switch us,ru,ua You can add this to autostart Here I switch layout with Right Control, Menu key is used for third level of keys and I use three layouts: English, Russian and Ukrainian. One notice: keyboard indicator on panel lives in parallel reality in such setup, so I'm using gXneur to indicate current layout (only this, and disabled input monitoring, looks like gXneur is broken in Ubuntu 13.10-14.04 with GNOME and Unity) and disabled original one in keyboard settings. As the result - I have all possible shortcuts working on any layout, switching layout with one key - right ctrl (not possible otherwise in GNOME) and separate layouts per windows and keyboard indicator with gXneur. Yes, such ugly but perfectly working hacks because of "smart" decisions of GNOME developers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in Aptana Studio Installer: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “openjdk-7” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
As I see here - bug is going to be fixed for every separate application which is completely wrong approach. THIS IS THE MOST CRITICAL BUG since 13.10, and should be fixed for all apps in one place. Users do not care how it works internally, we only know that regular Ctrl+C do not work with any non-latin layout. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in Aptana Studio Installer: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “openjdk-7” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://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 964270] Re: Ubuntu forgets keyboard shortcuts after a restart
The same issue for me. Not only shortcuts - some other settings resets to default after restart, for example automatic windows raising with mouse over. Also I like to move windows with Super+Mouse instead of default Alt+Mouse, but compiz forgets these changes every time. -- 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/964270 Title: Ubuntu forgets keyboard shortcuts after a restart Status in “compiz” package in Ubuntu: Confirmed Bug description: NOTE: This bug is for Ubuntu 12.04 (precise) only. If you experience something similar on 12.10 (quantal) or later then please refer to bug 1063617 instead. The two releases use completely different settings libraries so should be treated as separate bugs. Note also that if you just have trouble with screen edges, that is bug 858845. ORIGINAL DESCRIPTION: I use Dell XPS 1640. I'm using the latest ubuntu 12 and updated everything as of today. I assign some shortcuts for music to ubuntu keyboard shortcuts such as when i press ALT + X the music plays/pauses. However, after I restart the system, ubuntu forgets them and I have to reconfigure it everytime. I am new to Ubuntu but willing to help on debugging if it is simple and not technical. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.92-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Sun Mar 25 09:15:46 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/964270/+subscriptions -- Mailing list: https://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 1321704] Re: fcntl error with gksu
Got such error by running: nazar-pc@nazar-pc:~$ sudo synaptic fcntl error fcntl error ** Package changed: gksu (Ubuntu) => sudo (Ubuntu) ** Changed in: sudo (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gksu in Ubuntu. https://bugs.launchpad.net/bugs/1321704 Title: fcntl error with gksu Status in “sudo” package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.10 dev with gksu 2.0.2-6ubuntu2 and after making today a dist-upgrade I'm getting the following error if I want to start gksu: sworddragon@ubuntu:~$ gksu pcmanfm ** (gksu:1849): CRITICAL **: fcntl error ** (gksu:1849): WARNING **: Lock taken by pid: -1. Exiting. Edit: Downgrading linux-image-generic from version 3.15.0.1.2 0 to version 3.13.0.24.29 0 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1321704/+subscriptions -- Mailing list: https://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 1325251] Re: Lock file exists after closing
** Summary changed: - Bug with second opening + Lock file exists after closing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gksu in Ubuntu. https://bugs.launchpad.net/bugs/1325251 Title: Lock file exists after closing Status in “gksu” package in Ubuntu: New Bug description: When I run gksu executed first time - everything fine. After first run .gksu.lock appeared in home directory. And until I remove .gksu.lock file it doesn't work anymore, after removing this file it works exactly one more time, and stop working again. Ubuntu 14.10 right now, but as I remember was the same on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1325251/+subscriptions -- Mailing list: https://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 1325251] [NEW] Lock file exists after closing
Public bug reported: When I run gksu executed first time - everything fine. After first run .gksu.lock appeared in home directory. And until I remove .gksu.lock file it doesn't work anymore, after removing this file it works exactly one more time, and stop working again. Ubuntu 14.10 right now, but as I remember was the same on 14.04 ** Affects: gksu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gksu in Ubuntu. https://bugs.launchpad.net/bugs/1325251 Title: Lock file exists after closing Status in “gksu” package in Ubuntu: New Bug description: When I run gksu executed first time - everything fine. After first run .gksu.lock appeared in home directory. And until I remove .gksu.lock file it doesn't work anymore, after removing this file it works exactly one more time, and stop working again. Ubuntu 14.10 right now, but as I remember was the same on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1325251/+subscriptions -- Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
Please, fix this ASAP, I'm waiting with 256+ people more than half of year. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+subscriptions -- Mailing list: https://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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
How long? I want my Right Ctrl to switch fucking layout! Looks like every mentioned layout receive it's personal exception, not some universal fix. Ubuntu 13.10, 14.04 GNOME 3.10, 3.12 -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - holding left shift, press and release ctrl -> the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t -> gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) * Please add ability to set keyboard shortcuts to unity-control-center launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637) * Unable to rename new fo
[Desktop-packages] [Bug 1181318] Re: Very frequent crash of xorg
Now I have another video card, I'm using Gnome shell, and even migrated to another physical PC. I think, you can close it. But it was very bad behaviour. As I rememder - I gave up and migrated to Gnome shell, which is not very stable too, but much better in comparison. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1181318 Title: Very frequent crash of xorg Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Bug description: I'm observing very frequent crashes of xorg. They starts after transition to new monitor with resolution 2560x1440 on Raring, now on Saucy they are very frequent. Mainly, occurs at usage of Resize Window compiz plugin, opening youtube video to fullscreen and opening video in vlc to fullscreen. Sometimes it resumes to work (like reloading of compiz), sometimes resumes without compiz (impossible to use after this), sometimes xorg crashes at all. Graphics card Radeon HD6570, radeon driver. --- .tmp.unity.support.test.0: ApportVersion: 2.10.1-0ubuntu1 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 DistUpgraded: 2013-05-12 12:26:17,024 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Turks PRO [Radeon HD 6570] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] Advanced Micro Devices [AMD] nee ATI Cape Verde XT [Radeon HD 7770 GHz Edition] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2319] InstallationDate: Installed on 2012-04-27 (384 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: xorg 1:7.7+1ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: placeholder root=UUID=59430d17-e491-4f6f-ab9a-82c92889317c ro max_loop=64 xen-pciback.hide=(04:00.0)(04:00.1)(00:12.0)(00:12.2) quiet splash Tags: third-party-packages saucy ubuntu reproducible compiz-0.9 Uname: Linux 3.10.0-rc1-bulldozer x86_64 UpgradeStatus: Upgraded to saucy on 2013-05-12 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 990FX Extreme3 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.50:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme3:rvr: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.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.1.1-0ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2glamor2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4glamor version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri May 17 19:40:59 2013 xserver.configfile: /etc/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu9 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1181318/+subscriptions -- Mailing list: https://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 1168662] Re: full screen flash not working
The same, sometimes (randomly) can't open fullscreen, it like opens somewhere, but not on the top. Ubuntu 13.10, Gnome-shell 3.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1168662 Title: full screen flash not working Status in “flashplugin-nonfree” package in Ubuntu: Confirmed Bug description: have flash issue...full screen videos are not workin in flash for me...tried everything i ve found in webnothin helped... usin ubuntu 13.04 with gnome-shell, flash version 11.2 when i click to play a video its ok, but when i want to watch same thing in full screen, there is only soundfunny part is, its workin sometimes, like 1 of 20 tries. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: firefox 20.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 BuildID: 20130404201419 Channel: Unavailable Date: Sat Apr 13 14:50:36 2013 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.3 metric 1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=20.0/20130404201419 (In use) RelatedPackageVersions: totem-mozilla 3.6.3-0ubuntu6 rhythmbox-mozilla 2.98-0ubuntu5 gnome-shell 3.8.0.1-0ubuntu1+js17~raring3 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire 7741 dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.09:bd05/03/2010:svnAcer:pnAspire7741:pvrV1.09:rvnAcer:rnAspire7741:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.name: Aspire 7741 dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1168662/+subscriptions -- Mailing list: https://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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Can't use Right Ctrl key. What is interesting, if hold ctrl and press some letter key - layout changes! If just click - returns to English, regardless which layout was before. The same for Caps Lock key, but, weirdly, Right Shift key works perfectly!!! WTF guys? This is not high priority bug, this is EXTREMELY HIGH PRIORITY ANNOYING BUG FOR ALMOST EVERY GNOME SHELL USER! -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space: * Unity greeter (bug 1245137); * Unity session (bug 1245136); * lock screen - gnome-screensaver (bug 1245138, bug 1245256); * ubiquity installer (bug 1242572). Alt+Shift: * Unity greeter (bug 1245258) * Can't set keyboard layout change to Alt+Shift (bug 1245926) Ctrl+Shift: * lock screen - gnome-screensaver (bug 1245270) * Unity greeter (bug 1245268) * Can't set keyboard layout change to Ctrl+Shift (bug 1245991) * If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V are not working in gnome-terminal (bug 1246656) Shift+Shift: * Can't set keyboard layout change to Shift+Shift (bug 1245272) * lock screen - gnome-screensaver (bug 1245278) * Unity greeter (bug 1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (bug 1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (bug 1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (bug 1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (bug 1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (bug 1244548) * [FFe] indicator-keyboard not working under greeter (bug 1228207) * Lost ability to remap Caps Lock to Ctrl (bug 1215826) * gnome-control-center keyboard no longer has way to modify caps lock key behavior (bug 1224575) * Pressing Caps Lock toggles LED even when mapped to another key (bug 1221403) * Switching layout turns off NumLock (bug 1247668) -- Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. "Shift", "CapsLock" keys are just ignored in settings. Also the default shortcut was set to "Super+Space" that is inconveniently, because Dash is opening when you swich your keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignatur
[Desktop-packages] [Bug 958007] Re: First switching of the keyboard layout doesn't update the layout indicator
How long you are planning to save this bug? -- 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/958007 Title: First switching of the keyboard layout doesn't update the layout indicator Status in Indicator keyboard: New Status in Ubuntu network, Bluetooth, keyboard menus: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Good day! I am reporting this bug after this one has been fixed: https://bugs.launchpad.net/ubuntu/oneiric/+source/gnome-settings-daemon/+bug/885730 This is because an issue remained with incorrect keyboard layout displaying by the indicator. The problem is in the first keyboard layout switching right after start of an application. The first switching leads to actual change of the layout but it is not followed by the indicator change. To reproduce: 1) Start any application (say, gedit). The layout is "en" and the indicator shows also "en". 2) Switch the layout to the other. The layout will actually be changed but the indicator will still show "en" which is incorrect. And one more observation. If you do something (press Alt to reveal HUD, switch to another window and then return back) before the first layout change, the indicator will react correctly after that. Also, I can reproduce this within both settings "Use the same layout for all windows" and "Allow different layouts for individual windows". Thank you! P.S. This is my first bug report, so if something is wrong, I give my sincere apology. Please correct me then. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.91-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CasperVersion: 1.311 Date: Sat Mar 17 20:43:56 2012 LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120317) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/958007/+subscriptions -- Mailing list: https://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 1209397] Re: [radeonsi] radeonhd "southern islands" 3d hardware acceleration
Glamor just occured in Saucy repository! Not tested yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1209397 Title: [radeonsi] radeonhd "southern islands" 3d hardware acceleration Status in “mesa” package in Ubuntu: Fix Released Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: Description: radeon hd7850 has no 3d acceleration steps: 1. install phoronix-test-suite sudo apt-get install phoronix-test-suite 2. install openarena phoronix-test-suite install openarena 3. run openarena phoronix-text-suite run openarena expected results: 3d acceleration is used Actual results: no 3d acceleration additional info: robotfuel: Ah, yes. The 7850 is a southern islands card which requires glamor to do 2D acceleration and requires 2D acceleration to do 3D accel, and we don't currently build glamor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-ati 1:7.1.0+git20130801.g2ae6bb1-0ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.12-0ubuntu3 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 CurrentDmesg: [ 11.412407] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 15.388162] do_trap: 129 callbacks suppressed [ 15.388165] traps: install-default[1350] trap int3 ip:7f4182bef179 sp:7fffabc1ffc0 error:0 Date: Wed Aug 7 20:57:54 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2320] InstallationDate: Installed on 2013-08-07 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=61893e71-ac88-4379-a8b1-5699b1f3e749 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904 dmi.board.name: DZ77BH-55K dmi.board.vendor: Intel Corporation dmi.board.version: AAG39008-400 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr: version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu8 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu8 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9 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.1.0+git20130801.g2ae6bb1-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3 xserver.bootTime: Wed Aug 7 19:53:04 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputRaritan D2CIM-DVUSB KEYBOARD, id 8 inputRaritan D2CIM-DVUSB MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2-0ubuntu9 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1209397/+subscriptions -- Mailing list: https://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 1225849] Re: Keyboard shortcuts do not work
I realized, that hotkeys work only on English keyboard layout. After I switch to Russian or Ukrainian - even obvious shortcuts like Ctrl+C and Ctrl+V are not working! Extra important bug! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1225849 Title: Keyboard shortcuts do not work Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: Keyboard shortcuts do not work ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session-flashback 1:3.6.2-0ubuntu15 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Mon Sep 16 07:43:31 2013 GsettingsChanges: InstallationDate: Installed on 2013-08-28 (18 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130828) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1225849/+subscriptions -- Mailing list: https://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 1225849] Re: Keyboard shortcuts do not work
I'm using x64 version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1225849 Title: Keyboard shortcuts do not work Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: Keyboard shortcuts do not work ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session-flashback 1:3.6.2-0ubuntu15 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Mon Sep 16 07:43:31 2013 GsettingsChanges: InstallationDate: Installed on 2013-08-28 (18 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130828) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1225849/+subscriptions -- Mailing list: https://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 1189014] Re: Ubuntu 13.10 doesn't see USB sound card
** Changed in: alsa-utils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1189014 Title: Ubuntu 13.10 doesn't see USB sound card Status in “alsa-utils” package in Ubuntu: Invalid Bug description: I have USB headset "Platronics Gamecom 777". It worked fine in Ubuntu 13.04, but with 13.10 I don't see it in the list of sound devices, however it is listed correctly in lsusb: Bus 003 Device 003: ID 047f:ad01 Plantronics, Inc. GameCom 777 5.1 Headset I'm not sure, what caused this, but now on my desktop only integrated sound works. --- ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-04-27 (406 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MarkForUpload: True Package: alsa-utils 1.0.25-4ubuntu2 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.10.0-rc4-bulldozer x86_64 UpgradeStatus: Upgraded to saucy on 2013-05-12 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1189014/+subscriptions -- Mailing list: https://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 1188947] Re: gnome-session conflicts with cinnamon-session
Removing all cinnamon-related packages helped me, maybe you have something still not uninstalled? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1188947 Title: gnome-session conflicts with cinnamon-session Status in “gnome-session” package in Ubuntu: Confirmed Bug description: I see next message in window without decoration and black background: * Could not acquire name on session bus. * Failed to load session 'Ubuntu' Gnome fallback mode works fine. I think this is CRITICAL bug. Reinstalling/downgrade of some packages did not help me. Compiz in fallback mode works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 Uname: Linux 3.10.0-rc4-bulldozer x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu1 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 Date: Sat Jun 8 16:23:38 2013 DistUpgraded: 2013-05-12 12:26:17,024 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770 GHz Edition] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2319] InstallationDate: Installed on 2012-04-27 (406 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-rc4-bulldozer root=UUID=59430d17-e491-4f6f-ab9a-82c92889317c ro max_loop=64 xen-pciback.hide=(04:00.0)(04:00.1)(00:12.0)(00:12.2) quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-05-12 (27 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 990FX Extreme3 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.50:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme3:rvr: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.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.1.3-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2glamor2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Jun 8 16:09:51 2013 xserver.configfile: /etc/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu10 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1188947/+subscriptions -- Mailing list: https://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 1188947] Re: Unity does not starts after last update
** Package changed: unity (Ubuntu) => gnome-session (Ubuntu) ** Summary changed: - Unity does not starts after last update + gnome-session conflicts with cinnamon-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1188947 Title: gnome-session conflicts with cinnamon-session Status in “gnome-session” package in Ubuntu: Confirmed Bug description: I see next message in window without decoration and black background: * Could not acquire name on session bus. * Failed to load session 'Ubuntu' Gnome fallback mode works fine. I think this is CRITICAL bug. Reinstalling/downgrade of some packages did not help me. Compiz in fallback mode works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 Uname: Linux 3.10.0-rc4-bulldozer x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu1 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 Date: Sat Jun 8 16:23:38 2013 DistUpgraded: 2013-05-12 12:26:17,024 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770 GHz Edition] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2319] InstallationDate: Installed on 2012-04-27 (406 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-rc4-bulldozer root=UUID=59430d17-e491-4f6f-ab9a-82c92889317c ro max_loop=64 xen-pciback.hide=(04:00.0)(04:00.1)(00:12.0)(00:12.2) quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-05-12 (27 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 990FX Extreme3 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.50:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme3:rvr: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.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.1.3-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2glamor2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Jun 8 16:09:51 2013 xserver.configfile: /etc/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu10 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1188947/+subscriptions -- Mailing list: https://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 1189014] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1189014/+attachment/3698262/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1189014 Title: Ubuntu 13.10 doesn't see USB sound card Status in “alsa-utils” package in Ubuntu: New Bug description: I have USB headset "Platronics Gamecom 777". It worked fine in Ubuntu 13.04, but with 13.10 I don't see it in the list of sound devices, however it is listed correctly in lsusb: Bus 003 Device 003: ID 047f:ad01 Plantronics, Inc. GameCom 777 5.1 Headset I'm not sure, what caused this, but now on my desktop only integrated sound works. --- ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-04-27 (406 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MarkForUpload: True Package: alsa-utils 1.0.25-4ubuntu2 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.10.0-rc4-bulldozer x86_64 UpgradeStatus: Upgraded to saucy on 2013-05-12 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1189014/+subscriptions -- Mailing list: https://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 1189014] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1189014/+attachment/3698263/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1189014 Title: Ubuntu 13.10 doesn't see USB sound card Status in “alsa-utils” package in Ubuntu: New Bug description: I have USB headset "Platronics Gamecom 777". It worked fine in Ubuntu 13.04, but with 13.10 I don't see it in the list of sound devices, however it is listed correctly in lsusb: Bus 003 Device 003: ID 047f:ad01 Plantronics, Inc. GameCom 777 5.1 Headset I'm not sure, what caused this, but now on my desktop only integrated sound works. --- ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-04-27 (406 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MarkForUpload: True Package: alsa-utils 1.0.25-4ubuntu2 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.10.0-rc4-bulldozer x86_64 UpgradeStatus: Upgraded to saucy on 2013-05-12 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1189014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp