[Desktop-packages] [Bug 1308719] Re: [Aspire 5715Z, Realtek ALC268, Speaker, Internal] No sound at all
Thanks for the update Salman. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1308719 Title: [Aspire 5715Z, Realtek ALC268, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Invalid Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vendata2387 F pulseaudio Date: Wed Apr 16 23:23:27 2014 InstallationDate: Installed on 2014-02-12 (63 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vendata2387 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Aspire 5715Z, Realtek ALC268, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Acadia dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.45 dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5715Z:pvrV1.45:rvnAcer:rnAcadia:rvrV1.45:cvnAcer:ct1:cvrV1.45: dmi.product.name: Aspire 5715Z dmi.product.version: V1.45 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1308719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1308719] Re: [Aspire 5715Z, Realtek ALC268, Speaker, Internal] No sound at all
No need.. thank you On Thu, 5 Mar 2020 at 5:55 PM Marcus Tomlinson < marcus.tomlin...@canonical.com> wrote: > This release of Ubuntu is no longer receiving maintenance updates. If > this is still an issue on a maintained version of Ubuntu please let us > know. > > ** Changed in: alsa-driver (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1308719 > > Title: > [Aspire 5715Z, Realtek ALC268, Speaker, Internal] No sound at all > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1308719/+subscriptions > -- Kind Regards, M. Salman Masood Khan +92 321 517 0430 skype: msalmanmasood -- 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/1308719 Title: [Aspire 5715Z, Realtek ALC268, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vendata2387 F pulseaudio Date: Wed Apr 16 23:23:27 2014 InstallationDate: Installed on 2014-02-12 (63 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vendata2387 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Aspire 5715Z, Realtek ALC268, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Acadia dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.45 dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5715Z:pvrV1.45:rvnAcer:rnAcadia:rvrV1.45:cvnAcer:ct1:cvrV1.45: dmi.product.name: Aspire 5715Z dmi.product.version: V1.45 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1308719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857939] Re: hook /usr/share/apport/package-hooks/source_firefox.py crashed
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1857939
Title:
hook /usr/share/apport/package-hooks/source_firefox.py crashed
Status in firefox package in Ubuntu:
Expired
Bug description:
Trying to report a firefox bug:
% ubuntu-bug firefox
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
..ERROR: hook
/usr/share/apport/package-hooks/source_firefox.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_firefox.py", line 1351, in
add_info
populate_item("Profiles", profiles.dump_profile_summaries())
File "/usr/share/apport/package-hooks/source_firefox.py", line 1286, in
dump_profile_summaries
running = " (In use)" if profile.running == True else ""
File "/usr/share/apport/package-hooks/source_firefox.py", line 1078, in
running
fd = os.open(os.path.join(self.path, ".parentlock"),
os.O_WRONLY|os.O_CREAT|os.O_TRUNC, 0o666)
FileNotFoundError: [Errno 2] No such file or directory:
'/home/hadmut/.mozilla/firefox/va9ssbru.default/.parentlock'
.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 71.0+build5-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BuildID: 20191205203726
CurrentDesktop: LXQt
Date: Tue Dec 31 00:06:23 2019
InstallationDate: Installed on 2019-11-30 (30 days ago)
InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1857939/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866523] [NEW] Kernel 5.6-rc4 wont compile with nvidia 440.64
Public bug reported: According to Nvidia 440.64 should compile with kernel 5.6 Attempted kernel install with UKUU 19.12.1 make.log attached make[1]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc4-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.8-050508-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-23ubuntu2) ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 7 21:31:57 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.5.8-050508-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU104BM [GeForce RTX 2080 Mobile] [1043:135f] InstallationDate: Installed on 2020-03-03 (4 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. ROG G703GXR_G703GXR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-050508-generic root=UUID=3fc82c83-da27-480b-a875-214d33bc18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G703GXR.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G703GXR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG703GXR.302:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnROGG703GXR_G703GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG703GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: ROG G703GXR_G703GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ubuntu ** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1866523/+attachment/5334630/+files/make.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866523 Title: Kernel 5.6-rc4 wont compile with nvidia 440.64 Status in xorg package in Ubuntu: New Bug description: According to Nvidia 440.64 should compile with kernel 5.6 Attempted kernel install with UKUU 19.12.1 make.log attached make[1]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc4-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.8-050508-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-23ubuntu2) ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied:
[Desktop-packages] [Bug 1865169] Re: volume and light not working in Gnome Shell 3.35
I was simply checking the status and mis-clicked. Can't change it back now (Odd). To make it clear, then the fix has not been released yet. ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1865169 Title: volume and light not working in Gnome Shell 3.35 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: After upgrading to GNOME shell 3.35, the speaker icon in top bar is missing and both volume and light sliders are set to 0. Changing volume and light from keyboard works, but has no effect in gnome shell dropdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-16.19-generic 5.4.22 Uname: Linux 5.4.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 18:57:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (118 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866452] Re: Intel NUC5CPYH - Mouse pointer display on HDMI out does not cover all screen
** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1866452 Title: Intel NUC5CPYH - Mouse pointer display on HDMI out does not cover all screen Status in Ubuntu MATE: New Status in xf86-video-intel: New Status in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Issue Description - Intel NUC5CPYH has two video outputs: - VGA - HDMI On HDMI Output - the visible pointer can't reach the left screen border by couple of pixels (it get stuck in limit position) - the invisible pointer in the background handle normally. On VGA Out - the pointer both visible and invisible behave normally It affects probably all Ubuntu distribution. Tested only on Ubuntu and Ubuntu Mate, it affects also current 20.04 daily builds. Issue first noticed - Issue first appear on Ubuntu Mate 16.04 after performing LTS hardware enabling Stack when first available, and find that is related to xserver-xorg HWE, by reverting it back, wile keeping HWE Kernel. Note This system also has another mouse pointer bug https://bugs.launchpad.net/ubuntu-mate/+bug/1866454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1866452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866454] Re: Intel NUC5CPYH - dual mouse pointer display when booting with two screens
** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1866454 Title: Intel NUC5CPYH - dual mouse pointer display when booting with two screens Status in Ubuntu MATE: New Status in xf86-video-intel: New Status in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Issue Description - - two mouse pointers on screen on booting with on dual monitor setup, One behave normally second is stuck just animate synchronously with first one. - The presence of second mouse pointer results in mouse pointer trailing artifacts and screen artifacts under mouse pointer, rendering desktop unusable. - On Ubuntu Mate the second mouse pointer appear on a screen edge, and on Regular Ubuntu it appear somewhere on one of the two screens. Affected Systems - Tested on Both Ubuntu Mate and regular Ubuntu, both version 19.10 and 20.04 Issue reproduction -- - booting with two monitors connected on affected system, (connecting second monitor after login screen -lightdm greeter ... - will prevent issue appear) Workarounds --- - booting with only one monitor connected, and connect the second one later after log-in screen appear. - on booting with two monitors on Ubuntu Mate: Disabling Marco - Adaptive compositor to "No Compositor" will solve pointer trailing and screen artifacts, (but the second mouse pointer remain outside screen. Note This system also has another mouse pointer bug https://bugs.launchpad.net/ubuntu-mate/+bug/1866452 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1866454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866452] Re: Intel NUC5CPYH - Mouse pointer display on HDMI out does not cover all screen
** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** Package changed: ubuntu => xserver-xorg-video-intel ** Also affects: ubuntu Importance: Undecided Status: New ** Description changed: Issue Description - Intel NUC5CPYH has two video outputs: - VGA - HDMI On HDMI Output - the visible pointer can't reach the left screen border by couple of pixels (it get stuck in limit position) - the invisible pointer in the background handle normally. On VGA Out - the pointer both visible and invisible behave normally It affects probably all Ubuntu distribution. Tested only on Ubuntu and Ubuntu Mate, it affects also current 20.04 daily builds. - Issue age + Issue first noticed - - Issue is quite old, first observed in Ubuntu Mate 16.04 after performing LTS hardware enabling Stack, and find that is related to xserver-xorg upgrade. + Issue first appear on Ubuntu Mate 16.04 after performing LTS hardware enabling Stack when first available, and find that is related to xserver-xorg HWE, by reverting it back, wile keeping HWE Kernel. Note This system also has another mouse pointer bug https://bugs.launchpad.net/ubuntu-mate/+bug/1866454 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1866452 Title: Intel NUC5CPYH - Mouse pointer display on HDMI out does not cover all screen Status in Ubuntu MATE: New Status in xf86-video-intel: New Status in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Issue Description - Intel NUC5CPYH has two video outputs: - VGA - HDMI On HDMI Output - the visible pointer can't reach the left screen border by couple of pixels (it get stuck in limit position) - the invisible pointer in the background handle normally. On VGA Out - the pointer both visible and invisible behave normally It affects probably all Ubuntu distribution. Tested only on Ubuntu and Ubuntu Mate, it affects also current 20.04 daily builds. Issue first noticed - Issue first appear on Ubuntu Mate 16.04 after performing LTS hardware enabling Stack when first available, and find that is related to xserver-xorg HWE, by reverting it back, wile keeping HWE Kernel. Note This system also has another mouse pointer bug https://bugs.launchpad.net/ubuntu-mate/+bug/1866454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1866452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866222] Re: GNOME Shell crashed with signal 11
Here is the backtrace and registers. At first I couldn't reproduce the bug by just moving youtube videos (in firefox) around. But then when I had a document in LibreOffice Writer open (which is the situation I was in over the last few days of crashes), it happened very easily. --- Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. 0x7f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 (gdb) bt #0 0x7f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #1 0x7f65563fe3f9 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #2 0x7f65563ff413 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #3 0x7f6556420110 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #4 0x7f65563dee69 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #5 0x7f6555ff0f6f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #6 0x7f6555ff135a in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #7 0x7f6555fb9094 in gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #8 0x7f6555ff1006 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #9 0x7f6556ef0fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f6556ef1240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f6556ef1533 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f65563bb970 in meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #13 0x560782a19d85 in ?? () #14 0x7f655613d1e3 in __libc_start_main (main=0x560782a19930, argc=1, argv=0x7ffe0362fc48, init=, fini=, rtld_fini=, stack_end=0x7ffe0362fc38) at ../csu/libc-start.c:308 #15 0x560782a19f5e in ?? () (gdb) info registers rax0xffb0 -80 rbx0x56078765c2c0 94590336352960 rcx0x7 7 rdx0x5607850dab40 94590297025344 rsi0x5607857211d0 94590303605200 rdi0x0 0 rbp0x 0x rsp0x7ffe0362f698 0x7ffe0362f698 r8 0x7f650c003300 140071969764096 r9 0x56078a5d8740 94590386145088 r100x560784463018 94590283952152 r110x7ffe0362f538 140728955237688 r120x1 1 r130x7f650c003350 140071969764176 r140x56078765c2c0 94590336352960 r150x560784e680b0 94590294458544 rip0x7f6555da3624 0x7f6555da3624 eflags 0x10202 [ IF RF ] cs 0x3351 ss 0x2b43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has crashed twice on me today. Unfortunately there's nothing in /var/crash. There's nothing in the journalctl log prior to the crash that explains it. I've attached a log of everything between when the crash happened and when I logged back in (though I suspect most of it is not relevant). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 13:04:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (201 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866498] [NEW] [Snap] Libreoffice Snap is not available in Hungarian
Public bug reported: Could you please add Hungarian language to libreoffice snap. I want to change all my deb applications to snaps but this isn'T possible without correct localization. Thanks I know it adds ~ 8mb overhead to the snap but I think it's an acceptable size compared to nowadays HDD sizes ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1866498 Title: [Snap] Libreoffice Snap is not available in Hungarian Status in libreoffice package in Ubuntu: New Bug description: Could you please add Hungarian language to libreoffice snap. I want to change all my deb applications to snaps but this isn'T possible without correct localization. Thanks I know it adds ~ 8mb overhead to the snap but I think it's an acceptable size compared to nowadays HDD sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1866498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863468] Re: Libreoffice Snap is not available in Turkish
@hellsworth Could you please also add Hungarian support to the snap. I want to switch most of my applications from deb to snap but it's not possible without proper language support -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1863468 Title: Libreoffice Snap is not available in Turkish Status in libreoffice package in Ubuntu: Fix Committed Bug description: Libreoffice Snap is not available in Turkish. Although there are many other language packs available, there is no Turkish language support. I am having difficulty using it because I do not speak English. I was able to write this message through Google Translate anyway. I request the addition of Turkish language for the Libreoffice Snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
I have verified the testcase
- on bionic using version 2.56.4-0ubuntu0.18.04.5 of the libglib2.0-*
packages from bionic-proposed and version 1.5.17-3ubuntu5.3 of the ibus
packages from ppa:ubuntu-security-proposed/ppa
- on xenial using version 2.48.2-0ubuntu4.5 of the libglib2.0-* packages
from xenial-proposed and version 1.5.11-1ubuntu2.4 of the ibus packages
from ppa:ubuntu-security-proposed/ppa
As regards the autopkgtest failures, please see comment #29.
Marked the disco bug task as "Won't Fix" since disco is EOL.
** Tags removed: verification-needed-bionic verification-needed-xenial
** Tags added: verification-done-bionic verification-done-xenial
** Changed in: glib2.0 (Ubuntu Disco)
Importance: High => Undecided
** Changed in: glib2.0 (Ubuntu Disco)
Status: Fix Committed => Won't Fix
** Changed in: glib2.0 (Ubuntu Disco)
Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Won't Fix
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866419] Re: gnome-shell displays date incorrectly for nl_NL locale
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866419 Title: gnome-shell displays date incorrectly for nl_NL locale Status in gnome-shell package in Ubuntu: New Bug description: I am running the regular edition of Ubuntu. I have my system set to the nl_NL locale. The clock display on the top bar of gnome-shell is displayed as "vr mrt 6 23:45:01". While the individual parts are translated correctly, the order is not. It should be "vr 6 mrt 23:45:01". Steps to reproduce: - Install in Dutch - Observe that the clock in the top bar shows the month name before the day. Other notes: - Bug is present in at least 18.04, 19.04, 19.10 and the upcoming 20.04 - Adding/removing parts to the date (like weekday, seconds, etc.) using gnome-tweaks does not make any difference: all combinations have this wrong date order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866419] [NEW] gnome-shell displays date incorrectly for nl_NL locale
You have been subscribed to a public bug: I am running the regular edition of Ubuntu. I have my system set to the nl_NL locale. The clock display on the top bar of gnome-shell is displayed as "vr mrt 6 23:45:01". While the individual parts are translated correctly, the order is not. It should be "vr 6 mrt 23:45:01". Steps to reproduce: - Install in Dutch - Observe that the clock in the top bar shows the month name before the day. Other notes: - Bug is present in at least 18.04, 19.04, 19.10 and the upcoming 20.04 - Adding/removing parts to the date (like weekday, seconds, etc.) using gnome-tweaks does not make any difference: all combinations have this wrong date order. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- gnome-shell displays date incorrectly for nl_NL locale https://bugs.launchpad.net/bugs/1866419 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866329] Re: [lubuntu] nm-connection-editor lacks option for metered connections
Well, I'm already having a machine running Lubuntu 19.10, but it doesn't have that option either. In fact, it does not come with a configuration editor at all, but opens a terminal with a very basic curses-based text configuration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1866329 Title: [lubuntu] nm-connection-editor lacks option for metered connections Status in network-manager-applet package in Ubuntu: New Bug description: Hi, unfortunately, snapd insists to refresh snaps, thus possibly causing several GB of traffic per day, blocking the network and ruining the owner if the connection is slow and/or metered. There is no option to turn this permanently off, only methods to schedule, delay, or to hold refreshing if a metered connection is detected. It is, therefore, important to be able to tell Network Manager, that a connection is metered in order to keep snapd from ruining the user. While I've seen screenshots showing this option in the mainstream ubuntu's desktop settings, I do not see such an option in nm- connection-editor, which is used e.g. by Lubuntu. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 6 12:12:05 2020 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown InstallationDate: Installed on 2018-04-30 (676 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.103.254 dev enp2s0 proto dhcp metric 100 192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.101.143 metric 100 192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1 metric 425 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1866329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1018622] Re: [SB Live! Platinum CT4760P] No sound
I'm really sorry this issue went unanswered for so long. The backlog we've accrued here is truly unfortunate. We'd really like to see the situation improve, but with over 3000 open bugs, manually testing each has become virtually impossible. The aim in pinging neglected bugs such as this is to allow those still effected to get their issue back on the radar. I'll leave the bug incomplete in case anyone else happens to know if this is still relative. Again, apologies for the radio silence. -- 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/1018622 Title: [SB Live! Platinum CT4760P] No sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: No further information available. Seems to be a common Ubuntu/Debian problem as few distro's produce sound from this card. Had same problems with Debian 32bit installation. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julian 4547 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! Platinum [CT4760P] (rev.7, serial:0x80401102) at 0xa000, irq 18' Mixer name : 'SigmaTel STAC9721,23' Components : 'AC97a:83847609' Controls : 217 Simple ctrls : 38 Card1.Amixer.info: Card hw:1 'CK804'/'NVidia CK804 with ALC850 at irq 22' Mixer name : 'Realtek ALC850 rev 0' Components : 'AC97a:414c4790' Controls : 42 Simple ctrls : 27 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe Date: Wed Jun 27 23:09:49 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1805 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1805:bd09/29/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1018622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1018622] Re: [SB Live! Platinum CT4760P] No sound
I'm really sorry this issue went unanswered for so long. The backlog we've accrued here is truly unfortunate. We'd really like to see the situation improve, but with nearly 1300 open bugs, manually testing each has become virtually impossible. The aim in pinging neglected bugs such as this is to allow those still effected to get their issue back on the radar. I'll leave the bug incomplete in case anyone else happens to know if this is still relative. Again, apologies for the radio silence. -- 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/1018622 Title: [SB Live! Platinum CT4760P] No sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: No further information available. Seems to be a common Ubuntu/Debian problem as few distro's produce sound from this card. Had same problems with Debian 32bit installation. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julian 4547 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! Platinum [CT4760P] (rev.7, serial:0x80401102) at 0xa000, irq 18' Mixer name : 'SigmaTel STAC9721,23' Components : 'AC97a:83847609' Controls : 217 Simple ctrls : 38 Card1.Amixer.info: Card hw:1 'CK804'/'NVidia CK804 with ALC850 at irq 22' Mixer name : 'Realtek ALC850 rev 0' Components : 'AC97a:414c4790' Controls : 42 Simple ctrls : 27 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe Date: Wed Jun 27 23:09:49 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1805 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1805:bd09/29/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1018622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1018622] Re: [SB Live! Platinum CT4760P] No sound
Oh my word! An outstanding bug from 2012! I don't think I've even turned that PC on for at least 5-6 years. Sorry, no idea whether the bug is still current. -- 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/1018622 Title: [SB Live! Platinum CT4760P] No sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: No further information available. Seems to be a common Ubuntu/Debian problem as few distro's produce sound from this card. Had same problems with Debian 32bit installation. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julian 4547 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! Platinum [CT4760P] (rev.7, serial:0x80401102) at 0xa000, irq 18' Mixer name : 'SigmaTel STAC9721,23' Components : 'AC97a:83847609' Controls : 217 Simple ctrls : 38 Card1.Amixer.info: Card hw:1 'CK804'/'NVidia CK804 with ALC850 at irq 22' Mixer name : 'Realtek ALC850 rev 0' Components : 'AC97a:414c4790' Controls : 42 Simple ctrls : 27 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe Date: Wed Jun 27 23:09:49 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1805 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1805:bd09/29/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1018622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages
seems these are links to browse the profiles online:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.focal/view/head:/debian/usr.bin.firefox.apparmor.14.10
https://git.launchpad.net/apparmor/tree/profiles/apparmor.d/abstractions
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
[Desktop-packages] [Bug 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend
I am also affected by this bug on xubuntu 19.10. One thing I noticed is that there are two xfce4-screensaver-dialog processes when waking up from suspending by closing the lid. When waking up after suspending via other ways there is only one such process and things work properly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1853709 Title: lightdm does not greet or present login prompt when resuming from laptop suspend Status in lightdm package in Ubuntu: Confirmed Bug description: Expected result: when opening laptop lid the lock screen presents itself so I can unlock my session Actual result: the contents of my desktop are visible (windows, etc) and I can move my mouse cursor around but I cannot interact with the desktop session at all. Hovering over UI elements or clicking them has no effect. In order to get the login prompt I have to ctrl+alt+f1, login at the console, and run sudo systemctl restart lightdm, then I can login normally and resume whatever I was doing from before I closed the laptop lid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 23 09:08:32 2019 InstallationDate: Installed on 2019-11-09 (14 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866492] Re: gnome-font-viewer crashed with SIGSEGV in g_main_context_dispatch() when installing fonts
*** This bug is a duplicate of bug 1857568 *** https://bugs.launchpad.net/bugs/1857568 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1857568, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1866492/+attachment/5334543/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1866492/+attachment/5334545/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1866492/+attachment/5334548/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1866492/+attachment/5334549/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1866492/+attachment/5334550/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1866492/+attachment/5334551/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1866492/+attachment/5334552/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1857568 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1866492 Title: gnome-font-viewer crashed with SIGSEGV in g_main_context_dispatch() when installing fonts Status in gnome-font-viewer package in Ubuntu: New Bug description: Steps to reproduce: Downloaded a TTF font. Double clicked the font to open gnome font viewer Clicked on "Install" Application crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-font-viewer 3.34.0-2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 7 09:15:26 2020 ExecutablePath: /usr/bin/gnome-font-viewer InstallationDate: Installed on 2020-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service ProcEnviron: SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x5558bdcae5a3:mov0x8(%rax),%r8d PC (0x5558bdcae5a3) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%r8d" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-font-viewer StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-font-viewer crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1866492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866219] Re: Login screen hangs
@vanvugt I appreciate your help. I did removed all the extensions and disabled the animation. However this did not helped to mitigate the issue. I found a tweak to mitigate the issue on bug#1866256 (@ernstp) by again enabling the animation again which resolved the issue. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866219 Title: Login screen hangs Status in gnome-shell package in Ubuntu: Incomplete Bug description: One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. * lsb_release -rd: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 * Software Center version: 3.35.91 * What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully. * What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps: 1. Let the lockscrren tp display. 2. Click on the icon on the bottom-right corner of the lockscreen. 3. Get the log in window and enter password to log in. 4. User is now logged in and is out of the issue. Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:02:36 2020 DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:39f2] InstallationDate: Installed on 2019-12-14 (82 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80S7 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN31WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 510-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0VCN31WW(V1.15):bd06/19/2018:svnLENOVO:pn80S7:pvrLenovoYOGA510-14ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct31:cvrLenovoYOGA510-14ISK: dmi.product.family: YOGA 510-14ISK dmi.product.name: 80S7 dmi.product.sku: LENOVO_MT_80S7_BU_idea_FM_YOGA 510-14ISK dmi.product.version: Lenovo YOGA 510-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1866473] [NEW] [ZenBook UX431FAC_UX431FA, Realtek ALC294, Speaker, Internal] Playback problem
Public bug reported: Speakers not sound, only headphones work in alsamixer everything seem to be ok speakers has enough gain and turn off when connect minijack. Headphones sound but when i disconect them speaker not sound if i open pauvcontrol is playing sound but cant hear it. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mariajo1534 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 7 16:05:00 2020 InstallationDate: Installed on 2020-03-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [ZenBook UX431FAC_UX431FA, Realtek ALC294, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FAC.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FAC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431FAC.204:bd10/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FAC_UX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FAC_UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1866473 Title: [ZenBook UX431FAC_UX431FA, Realtek ALC294, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Speakers not sound, only headphones work in alsamixer everything seem to be ok speakers has enough gain and turn off when connect minijack. Headphones sound but when i disconect them speaker not sound if i open pauvcontrol is playing sound but cant hear it. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mariajo1534 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 7 16:05:00 2020 InstallationDate: Installed on 2020-03-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [ZenBook UX431FAC_UX431FA, Realtek ALC294, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FAC.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FAC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431FAC.204:bd10/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FAC_UX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FAC_UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
Hi Daniel, I had the time to test the latest 20.04 ISO (today), and I cannot repro the bug so far. Regarding the gnome-shell extensions, I cleared my ~/.local/share/gnome- shell/extensions and rebooted. However, i can still trigger the bug. How can I check the list of installed extensions ? If I go to https://extensions.gnome.org/local/ I can see 3 system installed extensions: - Desktop Icons - Ubuntu AppIndicators - Ubuntu Dock Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I open LibreOffce Writer and decides to resize the Style window on the right of the screen (press F11 to toggle this window), Gnome- Shell completely freezes for a few seconds. I already rebooted and it's 100% reproducible. I initially reported this bug on Gnome-Shell Gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411 You can find more info there (journalctl logs) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-26 (150 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866460] [NEW] UEFI Device Firmware update failing
Public bug reported: The Updates tab on Software Center is currently telling me that I have a Lenofo ThinkPad X1 Carbon 7th / X1 Yoga 4th Embedded Controller Firmware Version 1.5 updae to install. It claims it will upgrade my UEFI Device Firmware from 0.1.14 to 0.1.15. I click the Update button. The update goes away briefly and a pop-up appears telling me I need to reboot. Then the update reappears. I reboot, and nothing happens during the reboot, i.e., I don't see an update being installed during the reboot, and when I open Software Center again after the reboot the update is still listed there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 7 09:01:19 2020 InstallationDate: Installed on 2019-09-12 (176 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1866460 Title: UEFI Device Firmware update failing Status in gnome-software package in Ubuntu: New Bug description: The Updates tab on Software Center is currently telling me that I have a Lenofo ThinkPad X1 Carbon 7th / X1 Yoga 4th Embedded Controller Firmware Version 1.5 updae to install. It claims it will upgrade my UEFI Device Firmware from 0.1.14 to 0.1.15. I click the Update button. The update goes away briefly and a pop-up appears telling me I need to reboot. Then the update reappears. I reboot, and nothing happens during the reboot, i.e., I don't see an update being installed during the reboot, and when I open Software Center again after the reboot the update is still listed there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 7 09:01:19 2020 InstallationDate: Installed on 2019-09-12 (176 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1866460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
This also occurs in Fedora 32 and Xfce 4.14 for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1033141] Re: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound running media players like Clementine, VLC, SMPlayer and Gnome-MPlay
Thanks for the update aramaicus. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1033141 Title: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound running media players like Clementine, VLC, SMPlayer and Gnome-MPlayer Status in alsa-driver package in Ubuntu: Fix Released Bug description: I'm not sure about the package but there's a bug with my sound. A lot of cracks. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: maico 1846 F pulseaudio /dev/snd/controlC2: maico 1846 F pulseaudio /dev/snd/controlC0: maico 1846 F pulseaudio /dev/snd/pcmC0D0p: maico 1846 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfcffc000 irq 43' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1028043e,00100101' Controls : 34 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'DigitalCamera'/'PixArt Imaging Inc. Digital_Camera at usb-:00:1d.1-1, full speed' Mixer name : 'USB Mixer' Components : 'USB093a:2900' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 2 Mono: Capture 0 [0%] [30.00dB] [on] Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xfe97c000 irq 17' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 24 Simple ctrls : 4 Date: Sun Aug 5 03:02:18 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Áudio embutido - HDA Intel Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07N90W dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/17/2010:svnDellInc.:pnVostro230:pvr00:rvnDellInc.:rn07N90W:rvrA02:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Vostro 230 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1033141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1033141] Re: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound running media players like Clementine, VLC, SMPlayer and Gnome-M
This thread can be closed. I don't have any issue anymore. Thank you. On Sat, Mar 7, 2020, 04:39 Marcus Tomlinson wrote: > I'm really sorry this issue went unanswered for so long. The backlog > we've accrued here is truly unfortunate. We'd really like to see the > situation improve, but with over 3000 open bugs, manually testing each > has become virtually impossible. The aim in pinging neglected bugs such > as this is to allow those still effected to get their issue back on the > radar. > > Is this still an issue for you? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1033141 > > Title: > [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, > dropouts or crackling sound running media players like Clementine, > VLC, SMPlayer and Gnome-MPlayer > > Status in alsa-driver package in Ubuntu: > Incomplete > > Bug description: > I'm not sure about the package but there's a bug with my sound. A lot > of cracks. > > ProblemType: Bug > DistroRelease: Ubuntu 12.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu1 > ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 > Uname: Linux 3.2.0-27-generic-pae i686 > NonfreeKernelModules: nvidia > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. > ApportVersion: 2.0.1-0ubuntu11 > Architecture: i386 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: maico 1846 F pulseaudio >/dev/snd/controlC2: maico 1846 F pulseaudio >/dev/snd/controlC0: maico 1846 F pulseaudio >/dev/snd/pcmC0D0p: maico 1846 F...m pulseaudio > Card0.Amixer.info: >Card hw:0 'Intel'/'HDA Intel at 0xfcffc000 irq 43' > Mixer name : 'Realtek ALC662 rev1' > Components : 'HDA:10ec0662,1028043e,00100101' > Controls : 34 > Simple ctrls : 19 > Card1.Amixer.info: >Card hw:1 'DigitalCamera'/'PixArt Imaging Inc. Digital_Camera at > usb-:00:1d.1-1, full speed' > Mixer name : 'USB Mixer' > Components : 'USB093a:2900' > Controls : 2 > Simple ctrls : 1 > Card1.Amixer.values: >Simple mixer control 'Mic',0 > Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum > Capture channels: Mono > Limits: Capture 0 - 2 > Mono: Capture 0 [0%] [30.00dB] [on] > Card2.Amixer.info: >Card hw:2 'NVidia'/'HDA NVidia at 0xfe97c000 irq 17' > Mixer name : 'Nvidia GPU 0b HDMI/DP' > Components : 'HDA:10de000b,10de0101,00100200' > Controls : 24 > Simple ctrls : 4 > Date: Sun Aug 5 03:02:18 2012 > InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 > (20120423) > PackageArchitecture: all > ProcEnviron: >LANGUAGE=pt_BR:pt:en >TERM=xterm >PATH=(custom, no user) >LANG=pt_BR.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel > successful > Symptom_Card: Áudio embutido - HDA Intel > Symptom_Jack: Green Line Out, Rear > Symptom_PulsePlaybackTest: PulseAudio playback test successful > Symptom_Type: Underruns, dropouts, or "crackling" sound > Title: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] > Underruns, dropouts or crackling sound > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/17/2010 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.3.0 > dmi.board.name: 07N90W > dmi.board.vendor: Dell Inc. > dmi.board.version: A02 > dmi.chassis.type: 3 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: Not Specified > dmi.modalias: > dmi:bvnDellInc.:bvr1.3.0:bd11/17/2010:svnDellInc.:pnVostro230:pvr00:rvnDellInc.:rn07N90W:rvrA02:cvnDellInc.:ct3:cvrNotSpecified: > dmi.product.name: Vostro 230 > dmi.product.version: 00 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1033141/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1033141 Title: [Vostro 230, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound running media players like Clementine, VLC, SMPlayer and Gnome-MPlayer Status in alsa-driver package in Ubuntu: Incomplete Bug description: I'm not sure about the package but there's a bug with my sound. A lot of cracks. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND
[Desktop-packages] [Bug 1866457] Re: gnome-shell crashes when I lock my screen
apport doesn't ever successfully upload the full crash dump. It always gets an HTTP 503 at the end, which I figure is the server timing out from the 1 GB core dump upload. I can provide a backtrace, thread dump, or other info from the dump if it would be helpful. ** Summary changed: - gnome-shell crashes when I lock my screen + gnome-shell crashes every time I unlock my screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866457 Title: gnome-shell crashes every time I unlock my screen Status in gnome-shell package in Ubuntu: New Bug description: After a recent "apt upgrade", for about 4 days gnome-shell crashes every time I lock/unlock my screen. Disabling the screen lock lets me run X and Wayland sessions with GNOME indefinitely. Manually locking my screen or letting it lock automatically causes gnome-shell to crash when I try to unlock it. When it crashes, it hangs for a long time without updating the mouse cursor (probably writing the large core dump), then finally dies and the window system restarts and I can log in. I've disabled all GNOME extensions and tried some other configuration changes but I can't find a work-around except to avoid the lock screen. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Sat Mar 7 07:30:22 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2018-02-28 (737 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-13 (84 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866457] [NEW] gnome-shell crashes every time I unlock my screen
Public bug reported: After a recent "apt upgrade", for about 4 days gnome-shell crashes every time I lock/unlock my screen. Disabling the screen lock lets me run X and Wayland sessions with GNOME indefinitely. Manually locking my screen or letting it lock automatically causes gnome-shell to crash when I try to unlock it. When it crashes, it hangs for a long time without updating the mouse cursor (probably writing the large core dump), then finally dies and the window system restarts and I can log in. I've disabled all GNOME extensions and tried some other configuration changes but I can't find a work-around except to avoid the lock screen. Description:Ubuntu Focal Fossa (development branch) Release:20.04 gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Sat Mar 7 07:30:22 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2018-02-28 (737 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-13 (84 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866457 Title: gnome-shell crashes every time I unlock my screen Status in gnome-shell package in Ubuntu: New Bug description: After a recent "apt upgrade", for about 4 days gnome-shell crashes every time I lock/unlock my screen. Disabling the screen lock lets me run X and Wayland sessions with GNOME indefinitely. Manually locking my screen or letting it lock automatically causes gnome-shell to crash when I try to unlock it. When it crashes, it hangs for a long time without updating the mouse cursor (probably writing the large core dump), then finally dies and the window system restarts and I can log in. I've disabled all GNOME extensions and tried some other configuration changes but I can't find a work-around except to avoid the lock screen. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Sat Mar 7 07:30:22 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2018-02-28 (737 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-13 (84 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
It should definitively be visible here... https://errors.ubuntu.com/?release=Ubuntu%2020.04=gnome-shell=week -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
This is still happening to me. Enabling animations again solved it. Could it be related to Yaru GTK theme or Yaru shell theme? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866371] Re: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update
I'm not sure it is exactly the same bug, but some users have a similar problem on Fedora 32, so it might be an upstream problem : https://gitlab.gnome.org/GNOME/mutter/issues/1058 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1058 https://gitlab.gnome.org/GNOME/mutter/issues/1058 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1866371 Title: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update Status in mutter package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu 20.04 (Gnome Shell) development version. Since I made the updates on 5th March, I have no more mouse cursor visible, on the login screen nor on the desktop session. Mouse is OK, as if I move it I can see some items / buttons highlighted, and if I click the mouse, it works well. I tried Yaru and DMZ Black themes, no cursor, it's completely invisible. I started several times, always no cursor. But if I switch to the Xorg (X11) session, mouse cursor is well back and visible. My graphic card : description: VGA compatible controller produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X] fabricant: Advanced Micro Devices, Inc. [AMD/ATI] identifiant matériel: 0 information bus: pci@:01:00.0 version: 00 bits: 64 bits horloge: 33MHz fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list rom configuration : driver=radeon latency=0 Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866329] Re: [lubuntu] nm-connection-editor lacks option for metered connections
ok... sorry for the mess i'm making of this bug report, but Lubuntu has now moved from LXDE to LXQt, so this feature request likely won't be implemented through these channels. I would advise upgrading to either 19.10 or 20.04 (when it's released) checking for an option in LXQt, and, if the feature isn't there then create another bug report.. Hope this helps! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1866329 Title: [lubuntu] nm-connection-editor lacks option for metered connections Status in network-manager-applet package in Ubuntu: New Bug description: Hi, unfortunately, snapd insists to refresh snaps, thus possibly causing several GB of traffic per day, blocking the network and ruining the owner if the connection is slow and/or metered. There is no option to turn this permanently off, only methods to schedule, delay, or to hold refreshing if a metered connection is detected. It is, therefore, important to be able to tell Network Manager, that a connection is metered in order to keep snapd from ruining the user. While I've seen screenshots showing this option in the mainstream ubuntu's desktop settings, I do not see such an option in nm- connection-editor, which is used e.g. by Lubuntu. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 6 12:12:05 2020 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown InstallationDate: Installed on 2018-04-30 (676 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.103.254 dev enp2s0 proto dhcp metric 100 192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.101.143 metric 100 192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1 metric 425 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1866329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866329] Re: [lubuntu] nm-connection-editor lacks option for metered connections
** Tags added: feature ** Package changed: ubuntu => network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1866329 Title: [lubuntu] nm-connection-editor lacks option for metered connections Status in network-manager-applet package in Ubuntu: New Bug description: Hi, unfortunately, snapd insists to refresh snaps, thus possibly causing several GB of traffic per day, blocking the network and ruining the owner if the connection is slow and/or metered. There is no option to turn this permanently off, only methods to schedule, delay, or to hold refreshing if a metered connection is detected. It is, therefore, important to be able to tell Network Manager, that a connection is metered in order to keep snapd from ruining the user. While I've seen screenshots showing this option in the mainstream ubuntu's desktop settings, I do not see such an option in nm- connection-editor, which is used e.g. by Lubuntu. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 6 12:12:05 2020 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown InstallationDate: Installed on 2018-04-30 (676 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.103.254 dev enp2s0 proto dhcp metric 100 192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.101.143 metric 100 192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1 metric 425 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1866329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866329] [NEW] [lubuntu] nm-connection-editor lacks option for metered connections
You have been subscribed to a public bug: Hi, unfortunately, snapd insists to refresh snaps, thus possibly causing several GB of traffic per day, blocking the network and ruining the owner if the connection is slow and/or metered. There is no option to turn this permanently off, only methods to schedule, delay, or to hold refreshing if a metered connection is detected. It is, therefore, important to be able to tell Network Manager, that a connection is metered in order to keep snapd from ruining the user. While I've seen screenshots showing this option in the mainstream ubuntu's desktop settings, I do not see such an option in nm-connection- editor, which is used e.g. by Lubuntu. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 6 12:12:05 2020 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown InstallationDate: Installed on 2018-04-30 (676 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.103.254 dev enp2s0 proto dhcp metric 100 192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.101.143 metric 100 192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1 metric 425 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic feature third-party-packages -- [lubuntu] nm-connection-editor lacks option for metered connections https://bugs.launchpad.net/bugs/1866329 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866329] Re: nm-connection-editor lacks option for metered connections
not a bug per-se, will convert to a support request ** Package changed: network-manager-applet (Ubuntu) => ubuntu ** Summary changed: - nm-connection-editor lacks option for metered connections + [lubuntu] nm-connection-editor lacks option for metered connections -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1866329 Title: [lubuntu] nm-connection-editor lacks option for metered connections Status in Ubuntu: New Bug description: Hi, unfortunately, snapd insists to refresh snaps, thus possibly causing several GB of traffic per day, blocking the network and ruining the owner if the connection is slow and/or metered. There is no option to turn this permanently off, only methods to schedule, delay, or to hold refreshing if a metered connection is detected. It is, therefore, important to be able to tell Network Manager, that a connection is metered in order to keep snapd from ruining the user. While I've seen screenshots showing this option in the mainstream ubuntu's desktop settings, I do not see such an option in nm- connection-editor, which is used e.g. by Lubuntu. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 6 12:12:05 2020 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown InstallationDate: Installed on 2018-04-30 (676 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.103.254 dev enp2s0 proto dhcp metric 100 192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.101.143 metric 100 192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1 metric 425 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1866329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866444] Re: [MacBook2, 1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem
ok - good news - I was able to repair my 32-bit 18.04.4 install on the *same* exact hardware and confirmed I am able to see (1) Microphone and (2) bars moving (see screenshot) NOTE: my Unity desktop is corrupt on my 32-bit instance so what you are seeing is Volume Control from XCFE. again, I want to be clear that this bug report is in regards to my *64-bit* Ubuntu install not listing two inputs (microphone and line in) in Settings. the purpose of this followup is to demonstrate it is not a hardware issue. my 32-bit Ubuntu instance on the same hardware is able to access the internal microphone. ** Attachment added: "Ubuntu 18.04 (32-bit) - Volume Control (xcfe).png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866444/+attachment/533/+files/Ubuntu%2018.04%20%2832-bit%29%20-%20Volume%20Control%20%28xcfe%29.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1866444 Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: What you expected to happen Settings -> Sound -> Input to list internal mic (to test orange bars for recording from internal mic) What actually happened Settings -> Sound -> Input only lists "Digital Input (S/PDIF)" (no bars move because no digital input connected) If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program" 1. Open Settings 2. Select Sound setting 3. Select Input tab -- NOTE: ultimately, I want recording to work in apps such as Chrome, Firefox, Zoom, etc. NOTE 2: mic recording was last working in Ubuntu 18.04.x (32-bit) instance on *same* MacBook hardware (this installation went corrupt so I can't reverify it still works unfortunately - I will add to this issue if I get the cycles to reinstall or at your request) NOTE 3: interestingly enough, while using "ubuntu-bug" it was able to record from the mic on the 1st (of 2 tests the bug collector initiated). -- $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 from "apt list --installed" alsa-base/bionic,bionic,bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installed] alsa-utils/bionic,bionic,now 1.1.3-1ubuntu1 amd64 [installed] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_76_86_generic_63 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1c: chinarut 1724 F...m pulseaudio /dev/snd/controlC0: chinarut 1724 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 22:41:25 2020 InstallationDate: Installed on 2020-01-24 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Intel failed Symptom_Type: Only some of inputs are working Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
