[Desktop-packages] [Bug 1937916] Re: xrandr --scale 0.5 confines display to native solution on secondary sceen, but mouse moves on the upscaled screen
** Summary changed: - xrandr --scale confines mouse to native solution on secondary sceen + xrandr --scale 0.5 confines display to native solution on secondary sceen, but mouse moves on the upscaled screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1937916 Title: xrandr --scale 0.5 confines display to native solution on secondary sceen, but mouse moves on the upscaled screen Status in xorg-server package in Ubuntu: New Bug description: `--scale 0.5 --filter nearest` works on the internal screen, however not on the external screen (via USB-C with Display-Port) `xrandr --output eDP-1 --primary --mode 1920x1080 --pos 0x0 --scale 0.5 --filter nearest --dpi 141 --output DP-1-3 --mode 3840x2160 --scale .5 --pos 960x0 --filter nearest` results in a display of the solution 1920x1080 (upper left quater), however the mouse uses the whole 3840x2160-space, leading to an offset between mouse and display. However this does not occur on the internal screen. xrandr: xrandr program version 1.5.1 Server reports RandR version 1.6 host: Static hostname: lws84.imws.tuwien.ac.at Icon name: computer-laptop Chassis: laptop Operating System: Fedora 34 (Workstation Edition) CPE OS Name: cpe:/o:fedoraproject:fedora:34 Kernel: Linux 5.13.4-200.fc34.x86_64 Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad P15 Gen 1 Screen: https://www.lg.com/de/monitore/lg-27UK670-B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1937916/+subscriptions -- Mailing list: https://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 1929572] Re: Xorg freeze
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1929572 Title: Xorg freeze Status in xorg-server package in Ubuntu: Expired Bug description: A screen freezing had occurred when I was watching video whose location is on my connected phone(Redmi9 with global miui12). While its appearing, there's completely no response to every input, also, there's no mouse on the screen. That's what I can describe. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 25 22:29:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi Device [1d72:2003] Subsystem: Xiaomi GP107M [GeForce MX350] [1d72:2003] InstallationDate: Installed on 2021-05-03 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: TIMI RedmiBook 16 ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=18c673bc-d09d-4a44-814f-b4f048aa888a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 1.8 dmi.bios.vendor: TIMI dmi.bios.version: RMAIC6B0P0808 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: TM2003 dmi.board.vendor: TIMI dmi.board.version: V34F2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnTIMI:bvrRMAIC6B0P0808:bd12/02/2020:br1.8:efr1.8:svnTIMI:pnRedmiBook16:pvr:rvnTIMI:rnTM2003:rvrV34F2:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 16 dmi.product.sku: TM2003-28977 dmi.sys.vendor: TIMI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/xorg-server/+bug/1929572/+subscriptions -- Mailing list: https://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 1937922] [NEW] gtk4 not built for i386
Public bug reported: I'm trying to enable GTK 4 when building ibus: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages Up to now ibus has been built also on i386, but gtk4 has not been built on that arch, so the i386 build fails due to missing build dependencies. Is it time to stop building ibus on i386? Or can we build gtk4 on i386 (it was successfully built on Debian's i386)? At least some step needs to be taken. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1937922 Title: gtk4 not built for i386 Status in ibus package in Ubuntu: New Bug description: I'm trying to enable GTK 4 when building ibus: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages Up to now ibus has been built also on i386, but gtk4 has not been built on that arch, so the i386 build fails due to missing build dependencies. Is it time to stop building ibus on i386? Or can we build gtk4 on i386 (it was successfully built on Debian's i386)? At least some step needs to be taken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions -- Mailing list: https://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 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513397/+files/syslog ** Description changed: - This is not always reproduceable. + First pulseaudio fails for some reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://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 1937919] [NEW] Fails to start pulseaudio (No card found by this name or index.)
Public bug reported: This is not always reproduceable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: This is not always reproduceable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://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 653132] Re: "Add Printer" dialog requests root password if user is not in Configure Printers group
I got affected by this in Ubuntu 20.04. How come? In the status above it says "Fix released". Am I missing something? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/653132 Title: "Add Printer" dialog requests root password if user is not in Configure Printers group Status in foomatic-db package in Ubuntu: Confirmed Status in gutenprint package in Ubuntu: Confirmed Status in python-cups package in Ubuntu: Fix Released Status in system-config-printer package in Ubuntu: Fix Released Status in python-cups source package in Oneiric: Fix Released Status in system-config-printer source package in Oneiric: Fix Released Bug description: Binary package hint: system-config-printer If you go to System->Administration->Printing and try and add printers without being in the Configure Printers group, the applet asks for the root account and root password. This is obviously not workable on Ubuntu where root has "no" password and the ideal situation is to use [gk]sudo or so to elevate privileges. If the user is not in the Printers group then he should be asked to enter the administration (sudo) password and not try and be root if possible. If root account and permissions are required (i.e. sudo is not enough) then the dialog should notify the user that they should enable it in Users & Groups rather than asking for a password which does not exist by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/653132/+subscriptions -- Mailing list: https://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 1937916] [NEW] xrandr --scale confines mouse to native solution on secondary sceen
Public bug reported: `--scale 0.5 --filter nearest` works on the internal screen, however not on the external screen (via USB-C with Display-Port) `xrandr --output eDP-1 --primary --mode 1920x1080 --pos 0x0 --scale 0.5 --filter nearest --dpi 141 --output DP-1-3 --mode 3840x2160 --scale .5 --pos 960x0 --filter nearest` results in a display of the solution 1920x1080 (upper left quater), however the mouse uses the whole 3840x2160-space, leading to an offset between mouse and display. However this does not occur on the internal screen. xrandr: xrandr program version 1.5.1 Server reports RandR version 1.6 host: Static hostname: lws84.imws.tuwien.ac.at Icon name: computer-laptop Chassis: laptop Operating System: Fedora 34 (Workstation Edition) CPE OS Name: cpe:/o:fedoraproject:fedora:34 Kernel: Linux 5.13.4-200.fc34.x86_64 Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad P15 Gen 1 Screen: https://www.lg.com/de/monitore/lg-27UK670-B ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1937916 Title: xrandr --scale confines mouse to native solution on secondary sceen Status in xorg-server package in Ubuntu: New Bug description: `--scale 0.5 --filter nearest` works on the internal screen, however not on the external screen (via USB-C with Display-Port) `xrandr --output eDP-1 --primary --mode 1920x1080 --pos 0x0 --scale 0.5 --filter nearest --dpi 141 --output DP-1-3 --mode 3840x2160 --scale .5 --pos 960x0 --filter nearest` results in a display of the solution 1920x1080 (upper left quater), however the mouse uses the whole 3840x2160-space, leading to an offset between mouse and display. However this does not occur on the internal screen. xrandr: xrandr program version 1.5.1 Server reports RandR version 1.6 host: Static hostname: lws84.imws.tuwien.ac.at Icon name: computer-laptop Chassis: laptop Operating System: Fedora 34 (Workstation Edition) CPE OS Name: cpe:/o:fedoraproject:fedora:34 Kernel: Linux 5.13.4-200.fc34.x86_64 Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad P15 Gen 1 Screen: https://www.lg.com/de/monitore/lg-27UK670-B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1937916/+subscriptions -- Mailing list: https://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 1922548] Re: The admin backend is broken
Problem is fixed by Latest upstream version 1.48.1. but in Ubuntu I still have 1.47.91-1ubuntu1 see https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/122 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1922548 Title: The admin backend is broken Status in PolicyKit: Unknown Status in gvfs package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Invalid Bug description: On my PC I have some different users. If from one user I try to access the Home directory of a different user I enter the password and then I have a crash. Seen attached screenshot. Problem happens with both x11 and Wayland sessions. More: opening this bug I have the messages: corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland socket ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 12:05:27 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 611)' InstallationDate: Installed on 2021-04-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/1922548/+subscriptions -- Mailing list: https://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 1937914] [NEW] Laptop Monitor Turns off During Startup
Public bug reported: While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...). It seems clear that this problem is caused by a bug that was introduced in one of the more recent updates (...5.8.0-59..., maybe?). I am not at all sure that the problem is in xorg; the package identification webpage just suggested that, if the monitor is blank when I would expect to see the Ubuntu logo during startup, then I should say that the relevant package is xorg. I am more than happy to run additional diagnostics that you would recommend if that would help you diagnose and fix the problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 14:28:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542] InstallationDate: Installed on 2021-07-06 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD9308H3X dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5YH15UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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 focal third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1937914 Title: Laptop Monitor Turns off During Startup Status in xorg package in Ubuntu: New Bug description: While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48...,
[Desktop-packages] [Bug 1937871] Re: [Galaxy Buds Live (F88A), Volume lower than it should be
** Tags added: hw-specific kernel-bug -- 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/1937871 Title: [Galaxy Buds Live (F88A), Volume lower than it should be Status in alsa-driver package in Ubuntu: New Bug description: Galaxy Buds Live sound volume is lower than in other devices using non-linux operating systems. This however doesn't happen with the zen linux kernel where the volume is more acceptable. If I try to mitigate this with volumes level above 100 percent in pulse audio, the sound is distorted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-1009.10-oem 5.13.0 Uname: Linux 5.13.0-1009-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gregassagraf 5248 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 16:09:14 2021 InstallationDate: Installed on 2021-07-19 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Galaxy Buds Live (F88A) Symptom_Type: None of the above Title: [Galaxy Buds Live (F88A), playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07N10G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/01/2021:br1.6:svnDellInc.:pnInspiron5402:pvr:sku0A01:rvnDellInc.:rn07N10G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5402 dmi.product.sku: 0A01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1937871/+subscriptions -- Mailing list: https://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 1937903] [NEW] After upgrading to 20.04 my live tex distribution could not find style files and fonts so I used apt-get purge as a prelude to reinstalling. The purge failed wit
Public bug reported: After upgrading to 20.04 my live tex distribution could not find style files and fonts so I used apt-get purge as a prelude to reinstalling. The purge failed with system errors: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 24 09:17:16 2021 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-04 (932 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-05-22 (62 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1937903 Title: After upgrading to 20.04 my live tex distribution could not find style files and fonts so I used apt-get purge as a prelude to reinstalling. The purge failed with system errors: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: After upgrading to 20.04 my live tex distribution could not find style files and fonts so I used apt-get purge as a prelude to reinstalling. The purge failed with system errors: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 24 09:17:16 2021 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-04 (932 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-05-22 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1937903/+subscriptions -- Mailing list: https://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 1937900] [NEW] Nautilus stuck during search, could not establish a connection to tracker
Public bug reported: When starting Nautilus I am performing a search and get no response, the app is stuck/unresponsive and the search does not work. When i start it in debug mode i see: ``` $ G_MESSAGES_DEBUG=all nautilus (nautilus:1258): Gtk-DEBUG: 13:43:03.508: Connecting to session manager (nautilus:1258): GLib-GObject-WARNING **: 13:43:03.573: Two different plugins tried to register 'NautilusDiscBurn'. (nautilus:1258): GLib-GObject-CRITICAL **: 13:43:03.573: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed (nautilus:1258): GLib-GObject-CRITICAL **: 13:43:03.573: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed Initializing nautilus-dropbox 2020.03.04 ** (nautilus:1258): DEBUG: 13:43:04.910: starting file info in 0x55c57dbc2460 ** (nautilus:1258): DEBUG: 13:43:04.941: stopping file info in 0x55c57dbc2460 (nautilus:1258): Tracker-DEBUG: 13:43:23.014: Using backend = 'AUTO' (nautilus:1258): Tracker-DEBUG: 13:43:23.014: Waiting for service to become available... ``` And when i kill tracker with `tracker reset -etracker reset -e` then the search suddenly works I am not a dev but in this case I would timeout tracker for being unresponsive and just get on with the search without it. # My platform $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 # Nautilus $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.5 Candidate: 1:3.26.4-0~ubuntu18.04.5 Version table: *** 1:3.26.4-0~ubuntu18.04.5 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages # Tracker $ apt-cache policy tracker tracker: Installed: 2.0.3-1ubuntu4 Candidate: 2.0.3-1ubuntu4 Version table: *** 2.0.3-1ubuntu4 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1937900 Title: Nautilus stuck during search, could not establish a connection to tracker Status in nautilus package in Ubuntu: New Bug description: When starting Nautilus I am performing a search and get no response, the app is stuck/unresponsive and the search does not work. When i start it in debug mode i see: ``` $ G_MESSAGES_DEBUG=all nautilus (nautilus:1258): Gtk-DEBUG: 13:43:03.508: Connecting to session manager (nautilus:1258): GLib-GObject-WARNING **: 13:43:03.573: Two different plugins tried to register 'NautilusDiscBurn'. (nautilus:1258): GLib-GObject-CRITICAL **: 13:43:03.573: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed (nautilus:1258): GLib-GObject-CRITICAL **: 13:43:03.573: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed Initializing nautilus-dropbox 2020.03.04 ** (nautilus:1258): DEBUG: 13:43:04.910: starting file info in 0x55c57dbc2460 ** (nautilus:1258): DEBUG: 13:43:04.941: stopping file info in 0x55c57dbc2460 (nautilus:1258): Tracker-DEBUG: 13:43:23.014: Using backend = 'AUTO' (nautilus:1258): Tracker-DEBUG: 13:43:23.014: Waiting for service to become available... ``` And when i kill tracker with `tracker reset -etracker reset -e` then the search suddenly works I am not a dev but in this case I would timeout tracker for being unresponsive and just get on with the search without it. # My platform $ lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 # Nautilus $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.5 Candidate: 1:3.26.4-0~ubuntu18.04.5 Version table: *** 1:3.26.4-0~ubuntu18.04.5 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages # Tracker $ apt-cache policy tracker tracker: Installed: 2.0.3-1ubuntu4 Candidate: 2.0.3-1ubuntu4 Version table: *** 2.0.3-1ubuntu4 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1937900/+subscriptions -- Mailing list: https://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 1937899] Re: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while
** Bug watch added: Red Hat Bugzilla #1981602 https://bugzilla.redhat.com/show_bug.cgi?id=1981602 ** Also affects: alsa-driver (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1981602 Importance: Unknown Status: Unknown ** Also affects: alsa-driver (openSUSE) Importance: Undecided Status: New -- 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/1937899 Title: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while Status in alsa-driver package in Ubuntu: New Status in alsa-driver package in Fedora: Unknown Status in alsa-driver package in openSUSE: New Bug description: Description of problem:when using the youtube videos in web browser after pausing the video the audio is not audible if audio level in the system is set than less than 30 percent in order to listen to audio the slider need to be changed to more than 35 percent in the desktop screen this issue is happening in both Firefox browser and chrome browser also. the volume in the speakers is already set to maximum level. Version-Release number of selected component (if applicable): Description: Ubuntu 21.04 Release: 21.04 How reproducible: all the times this issue is occurring Steps to Reproduce: 1.open any web browser and open any video website like youtube 2. set the volume in the system to less 30 percent or so then the audio is not able to listen even with slightest volume 3.in order the hear the audio again the volume need to be adjusted in the sound bar. Actual results:after playing the video pause it and again try to play the video the audio is not audible some times, again i have to adjust the slider to listen the audio. Expected results: the audio should be audible slightly even after setting the audio level set to 30 percent. Additional Information: Facing this issue in latest version of Fedora 34 also with the latest updated kernel 5.13.4-200.fc34.x86_64 and in red hat enterprise linux 8.4 too. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: swamych1002 F pulseaudio /dev/snd/pcmC0D0p: swamych1002 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 17:57:41 2021 InstallationDate: Installed on 2021-07-24 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2018 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 00 dmi.board.vendor: Dell Inc. dmi.board.version: 000 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:br1.1:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn00:rvr000:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1937899/+subscriptions -- Mailing list: https://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 1937899] [NEW] [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while
Public bug reported: Description of problem:when using the youtube videos in web browser after pausing the video the audio is not audible if audio level in the system is set than less than 30 percent in order to listen to audio the slider need to be changed to more than 35 percent in the desktop screen this issue is happening in both Firefox browser and chrome browser also. the volume in the speakers is already set to maximum level. Version-Release number of selected component (if applicable): Description:Ubuntu 21.04 Release:21.04 How reproducible: all the times this issue is occurring Steps to Reproduce: 1.open any web browser and open any video website like youtube 2. set the volume in the system to less 30 percent or so then the audio is not able to listen even with slightest volume 3.in order the hear the audio again the volume need to be adjusted in the sound bar. Actual results:after playing the video pause it and again try to play the video the audio is not audible some times, again i have to adjust the slider to listen the audio. Expected results: the audio should be audible slightly even after setting the audio level set to 30 percent. Additional Information: Facing this issue in latest version of Fedora 34 also with the latest updated kernel 5.13.4-200.fc34.x86_64 and in red hat enterprise linux 8.4 too. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: swamych1002 F pulseaudio /dev/snd/pcmC0D0p: swamych1002 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 17:57:41 2021 InstallationDate: Installed on 2021-07-24 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2018 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 00 dmi.board.vendor: Dell Inc. dmi.board.version: 000 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:br1.1:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn00:rvr000:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1937899 Title: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Description of problem:when using the youtube videos in web browser after pausing the video the audio is not audible if audio level in the system is set than less than 30 percent in order to listen to audio the slider need to be changed to more than 35 percent in the desktop screen this issue is happening in both Firefox browser and chrome browser also. the volume in the speakers is already set to maximum level. Version-Release number of selected component (if applicable): Description: Ubuntu 21.04 Release: 21.04 How reproducible: all the times this issue is occurring Steps to Reproduce: 1.open any web browser and open any video website like youtube 2. set the volume in the system to less 30 percent or so then the audio is not able to listen even with slightest volume 3.in order the hear the audio again the volume need to be adjusted in the sound bar. Actual results:after playing the video pause it and again try to play the video the audio is not audible some times, again i have to adjust the slider to listen the audio. Expected results: the audio should be audible slightly even after setting the audio level set to 30 percent. Additional Information: Facing this issue in latest version of Fedora 34 also with the latest updated kernel 5.13.4-200.fc34.x86_64 and in red hat enterprise linux 8.4 too. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature:
[Desktop-packages] [Bug 1937893] [NEW] Touchscreen Misbehaving After Upgrading to Ubuntu 21.04
Public bug reported: I just upgraded from Ubuntu 20.10 to 21.04. After the upgrade, the touchscreen of my laptop has started registering random touch events when no touch input is actually being given by the user. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 12:54:15 2021 DistUpgraded: 2021-07-07 09:51:26,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81a9] InstallationDate: Installed on 2020-10-10 (286 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=58c17d38-5a4a-455c-a288-fffc3bd115a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-07 (17 days ago) dmi.bios.date: 06/25/2018 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.53 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 57.53 dmi.modalias: dmi:bvnInsyde:bvrF.35:bd06/25/2018:br15.35:efr57.53:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.53:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion x360 Convertible dmi.product.sku: Z4Q51PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1937893 Title: Touchscreen Misbehaving After Upgrading to Ubuntu 21.04 Status in xorg package in Ubuntu: New Bug description: I just upgraded from Ubuntu 20.10 to 21.04. After the upgrade, the touchscreen of my laptop has started registering random touch events when no touch input is actually being given by the user. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 12:54:15 2021 DistUpgraded: 2021-07-07 09:51:26,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81a9] InstallationDate: Installed on 2020-10-10 (286 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=58c17d38-5a4a-455c-a288-fffc3bd115a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-07 (17 days ago) dmi.bios.date: 06/25/2018 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.53 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 57.53 dmi.modalias:
[Desktop-packages] [Bug 1855770] Re: Unable to disable ssh component of gnome-keyring
** Also affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-session-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1855770 Title: Unable to disable ssh component of gnome-keyring Status in Ubuntu MATE: New Status in gnome-keyring package in Ubuntu: New Status in mate-session-manager package in Ubuntu: New Bug description: Under previous versions of Ubuntu MATE (18.04 in particular), it was possible to disable the ssh component of gnome-keyring-daemon either by a) unchecking a box in Startup Applications, or b) editing ~/.config/autostart/gnome-keyring-ssh.desktop to include "X-MATE- Autostart-enabled=false". However, in 19.10 (and possibly before), disabling this component seems to be a no-op. This means that I can't easily use a gpg smartcard for ssh keys. To replicate: * Disable gnome-keyring-ssh, either by unchecking the box in Startup Applications or by editing the .desktop file directly. * Log out and in again. * At a command prompt, run "echo $SSH_AUTH_SOCK". Expected behavior: get ssh-agent or gnupg-agent socket info. Actual behavior: get "/run/user/1000/keyring/ssh" I can see from `ps aux` that gnome-keyring-daemon is not having its components started separately, but rather just launched with `/usr/bin/gnome-keyring-daemon --daemonize --login`. I see on the release notes "Fixed a gnome-keyring timeout in mate- session-manager" -- is it possible that now gnome-keyring-daemon is being started incorrectly? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1855770/+subscriptions -- Mailing list: https://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 1937350] Re: USB HDD not properly spin down after safely remove
** Also affects: caja (Ubuntu) Importance: Undecided Status: New ** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** No longer affects: caja (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1937350 Title: USB HDD not properly spin down after safely remove Status in Linux: New Status in Ubuntu MATE: New Status in linux package in Ubuntu: New Status in udisks2 package in Ubuntu: New Bug description: I do not know which package I should file the bug for. I am using Ubuntu MATE 20.04 LTS and Microsoft Windows 10. On Microsoft Windows 10, no issue with safely remove any USB external HDD. When using Microsoft Windows 10, after safely remove my external HDD, the HDD will spin down. But, on Ubuntu MATE 20.04 LTS, some issues occur after I try to safely remove my external HDD. Tried different hard drive, different enclosures, and also some external hard drive that came bundled with enclosure. All having same or different issues after safely remove them in Ubuntu MATE. Problems will also occur on those branded external HDD that came bundled with enclosure, for example, those Seagate Backup Plus drives ( https://www.seagate.com/as/en/consumer/backup/backup-plus/ ). Here are the common problems after safely remove (in Ubuntu MATE): 1. The external HDD will spin down and then spin up again, and then being automatically remounted again. The "dmesg" command shows errors. 2. The external HDD will spin down and then spin up again, no remount. The LED on the enclosure keep flashing. The "dmesg" command shows errors. After you unplug the HDD, you can connect another HDD. 3. The external HDD will spin down and then spin up again, no remount. The LED on the enclosure keep flashing. The "dmesg" command shows errors. BUT, after you unplug the HDD, when you connect another HDD, the computer will not detect it and will not mount it until you reboot the computer. But, before reboot connecting another device (e.g. keyboard, mouse, etc) to the same USB port, the device works perfectly. 4. The external HDD will spin down and then spin up again, no remount. But, after a few seconds, it spin down again. But, still, the "dmesg" command shows errors. Different HDD, different enclosure, show different symptoms or problems. Some HDD enclosures, number 1 above will occur. Some HDD enclosures, either number 2 or 3 above will occur. Sometimes, problem number 2 above will occur. Sometimes, problem number 3 will occur. Some enclosure, problem number 4 will occur. Here, I will use the following enclosure as example in this bug report: Product link: https://www.ugreen.com/products/usb-c-2-5-sata-iii-hard- drive-enclosure Purchase link in my country: https://shopee.com.my/UGREEN-USB-3.1-To- SATA-III-External-Hard-Drive- Enclosure-(2.5-)-i.64923440.1583255569?position=1 Here are the steps to reproduce (for the enclosure above): 1. Connect the external HDD to any available USB 3.0 port. The HDD will be mounted. Caja (Ubuntu MATE default file manager) will launch. 2. Close the Caja window. Do not do anything on the HDD. 3. Use left or right hand, touch the HDD enclosure to feel the spinning. Do not let your hand leave the enclosure, so that you can continue feel the spinning. 4. Use your another hand to operate your computer. 5. Go to desktop. 6. Right click on the external HDD icon. 7. Click "Safely Remove Drive". The HDD unmounted. Assume that one of your hands still touching the enclosure of the HDD, you will feel that the HDD will spin down and then spin up again. No remount. The LED indicator on the enclosure will keep flashing. These are described in problem number 2 and 3 above. Sometimes, after you unplug the drive and try to connect another drive, it will not be detected until you reboot your computer. Almost all external HDDs I tested will cause "dmesg" command to shows "Buffer I/O error" and "Synchronize Cache() failed" error after "Safely Remove Drive". In Microsoft Windows 10, all above mentioned problems WILL NOT occur. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cshong 1059 F pulseaudio /dev/snd/controlC0: cshong 1059 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-23 (242 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic
