[Desktop-packages] [Bug 1913439] Re: "Alert Sound" change has no effect at all
** Changed in: gnome-control-center (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913439 Title: "Alert Sound" change has no effect at all Status in gnome-control-center package in Ubuntu: New Bug description: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.38.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Tags: third-party-packages groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913439/+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 1921766] Re: Output device not remembered after connecting/disconnecting another
Thanks for the bug report. First please try editing /etc/pulse/default.pa and comment out: load-module module-switch-on-port-available load-module module-switch-on-connect and then reboot. If that hasn't fixed the problem then please subscribe to: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/44 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #44 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/44 ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/44 Importance: Unknown Status: Unknown -- 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/1921766 Title: Output device not remembered after connecting/disconnecting another Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for development work. I run it on a Lenovo X1 Carbon 8th Generation connected to dual monitors via a Lenovo dock. Both monitors are capable of outputting sound via HDMI. I use bluetooth headphones frequently with my Ubuntu 20.10 system, but I don't leave them on -- I turn them on and off as needed for Zoom calls. When I'm not on a call, however, I prefer to use my laptop's speakers for audio -- not my monitor speakers. Turning the bluetooth headphones on works fine, they connect and pulseaudio correctly identifies the new connection and switches to the headphones as the audio device. However, when I turn the headphones off, pulseaudio always selects an HDMI audio device as the sound device to use, not the internal speaker device that I was using prior to turning on the headphones. I must manually open Sound Settings and select the speaker device every time I turn my headphones off. My expectation is that the device I was using prior to connecting the headphones is remembered and switched back to by default after I disconnect my bluetooth headphones. I've tried using the pavucontrol app to disable the HDMI audio devices, but the hardware device disable settings are not granular enough to let me target the HDMI devices independently of the speaker device. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1921766/+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 1921764] Re: Bug affichage.
** Tags added: radeon ** Summary changed: - Bug affichage. + [radeon] Bug affichage. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu) ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Incomplete -- 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/1921764 Title: [radeon] Bug affichage. Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 29 17:55:52 2021 DistUpgraded: 2021-03-27 13:26:19,628 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:e147] InstallationDate: Installed on 2021-03-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. P35-DS4 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=040b03c4-747a-4dce-8e7a-5cbea40e1985 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2021-03-27 (2 days ago) dmi.bios.date: 05/11/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: P35-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/11/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Mar 29 17:47:30 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech M315/M235 MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1921764/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Another user affected on 20.04. Happened to me after resuming from sleep. Alt+F2: R made it go away for me as well. -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1916301] Re: I can't play live videos on YouTube (problem with live transmission) - Ubuntu 18.04.5
@madbiologist, I have problems with this video from the link and I can
confirm that this is MP4 video:
"video/mp4; codecs=\"avc1.4d4020\"","bitrate":3481000,
I don't have installed libavcodec57 yet but I would like to know if it is
normal that Mozilla can run these kind videos (mp4) by default?
--
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/1916301
Title:
I can't play live videos on YouTube (problem with live transmission) -
Ubuntu 18.04.5
Status in firefox package in Ubuntu:
Incomplete
Bug description:
Dear Launchpad Team,
I can't play live videos from Youtube. I have problem only with live
transmission. Normal videos works fine. I noticed that I also have
this same problem on Focal (now I checked this on Bionic - Ubuntu
18.04.5). On Lubuntu 18.04.5 on other machine I don't have this
problem. I can play on Lubuntu all Youtube videos. What is a problem?
Do you know? I think that by default Ubuntu have not necessary package
to play live videos on Youtube. Have I right or this is a bug? On
Answers section on launchpad anyone can't tell me if it is a bug so
this is why I report this bug now. If it is not a bug I am very sorry
and you can delete this report now.
Example I have problem with this video:
https://www.youtube.com/watch?v=21X5lGlDOfg
I used debugger by youtube and this is output of this:
"debug_error": {
"errorCode": "html5.unsupportedlive",
"errorMessage": "Ten format wideo nie jest obsługiwany.",
"Nx": "HTML5_NO_AVAILABLE_FORMATS_FALLBACK",
"cj": "","
If it is a bug can you fix it?
UPDATE: Today I updated my firefox to the newest version 86.0. This
bug still exists.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916301/+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 1916301] Re: I can't play live videos on YouTube (problem with live transmission) - Ubuntu 18.04.5
*of course I mean that Mozilla can't run these kind of videos. I wrote
that can run but this is not true. Firefox can't run in my PC mp4 video.
--
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/1916301
Title:
I can't play live videos on YouTube (problem with live transmission) -
Ubuntu 18.04.5
Status in firefox package in Ubuntu:
Incomplete
Bug description:
Dear Launchpad Team,
I can't play live videos from Youtube. I have problem only with live
transmission. Normal videos works fine. I noticed that I also have
this same problem on Focal (now I checked this on Bionic - Ubuntu
18.04.5). On Lubuntu 18.04.5 on other machine I don't have this
problem. I can play on Lubuntu all Youtube videos. What is a problem?
Do you know? I think that by default Ubuntu have not necessary package
to play live videos on Youtube. Have I right or this is a bug? On
Answers section on launchpad anyone can't tell me if it is a bug so
this is why I report this bug now. If it is not a bug I am very sorry
and you can delete this report now.
Example I have problem with this video:
https://www.youtube.com/watch?v=21X5lGlDOfg
I used debugger by youtube and this is output of this:
"debug_error": {
"errorCode": "html5.unsupportedlive",
"errorMessage": "Ten format wideo nie jest obsługiwany.",
"Nx": "HTML5_NO_AVAILABLE_FORMATS_FALLBACK",
"cj": "","
If it is a bug can you fix it?
UPDATE: Today I updated my firefox to the newest version 86.0. This
bug still exists.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916301/+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 1891270] Re: Iranian calendar shows in Azerbaijani language
The screen shot of the Language Support's problem in the last daily build of Xubuntu about this bug. As you can see Azerbaijani is the default. Also Persian isn't exist. ** Attachment added: "Bug in Xubuntu" https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+attachment/5482240/+files/az.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Correction to #81, I meant to say on the A2DP I've got no microphone (as I understand it this is expected as A2DP is unidirectional) and on the HSP/HFP profile I have access to the microphone, but the audio quality is very poor and unusable. -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1921766] Re: Output device not remembered after connecting/disconnecting another
** Tags added: groovy ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1921766 Title: Output device not remembered after connecting/disconnecting another Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for development work. I run it on a Lenovo X1 Carbon 8th Generation connected to dual monitors via a Lenovo dock. Both monitors are capable of outputting sound via HDMI. I use bluetooth headphones frequently with my Ubuntu 20.10 system, but I don't leave them on -- I turn them on and off as needed for Zoom calls. When I'm not on a call, however, I prefer to use my laptop's speakers for audio -- not my monitor speakers. Turning the bluetooth headphones on works fine, they connect and pulseaudio correctly identifies the new connection and switches to the headphones as the audio device. However, when I turn the headphones off, pulseaudio always selects an HDMI audio device as the sound device to use, not the internal speaker device that I was using prior to turning on the headphones. I must manually open Sound Settings and select the speaker device every time I turn my headphones off. My expectation is that the device I was using prior to connecting the headphones is remembered and switched back to by default after I disconnect my bluetooth headphones. I've tried using the pavucontrol app to disable the HDMI audio devices, but the hardware device disable settings are not granular enough to let me target the HDMI devices independently of the speaker device. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1921766/+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 1921794] [NEW] connection to scanner very slow
Public bug reported: When starting simple scan it does "search for scanners" for about 30 seconds, until "ready to scan". Previously (forgot when that was, but same hardware) it was almost immediate. Seems to be some software bug. --- The printer/scanner and driver are: Description:HP LaserJet MFP M426fdn Location: Local Printer Driver: HP LaserJet Pro MFP M426-M427 Postscript via CUPS. --- Running hp-check -i gives this output: Missing Required Dependencies error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies error: 'python3-dbus.mainloop.qt' package is missing/incompatible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 30 00:59:36 2021 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2018-06-15 (1018 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libjpeg-x86_64.so.9.2.0 MachineType: Dell Inc. OptiPlex 7040 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=63e54e9f-567c-498f-883a-5216d348a80f ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to focal on 2020-08-20 (221 days ago) dmi.bios.date: 07/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.5 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.5:bd07/19/2019:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal local-libs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1921794 Title: connection to scanner very slow Status in simple-scan package in Ubuntu: New Bug description: When starting simple scan it does "search for scanners" for about 30 seconds, until "ready to scan". Previously (forgot when that was, but same hardware) it was almost immediate. Seems to be some software bug. --- The printer/scanner and driver are: Description: HP LaserJet MFP M426fdn Location: Local Printer Driver: HP LaserJet Pro MFP M426-M427 Postscript via CUPS. --- Running hp-check -i gives this output: Missing Required Dependencies error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies error: 'python3-dbus.mainloop.qt' package is missing/incompatible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 30 00:59:36 2021 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2018-06-15 (1018 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libjpeg-x86_64.so.9.2.0 MachineType: Dell Inc. OptiPlex 7040 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=63e54e9f-567c-498f-883a-5216d348a80f ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to focal on 2020-08-20 (221 days ago) dmi.bios.date: 07/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.5 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.5:bd07/19/2019:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1916301] Re: I can't play live videos on YouTube (problem with live transmission) - Ubuntu 18.04.5
I will try this soon. I can see that this libavcodec57 is from universe
repositories. Is it safe program? Why Ubuntu don't have installed this
by default? Is it licence problem? Second question is to updates for
libavcodec57 after April 2021 year. This is from Universe repositories
so this package will be not get updates in the future? This is very
important for me because I want to have bionic and I want to not migrate
to focal.
--
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/1916301
Title:
I can't play live videos on YouTube (problem with live transmission) -
Ubuntu 18.04.5
Status in firefox package in Ubuntu:
Incomplete
Bug description:
Dear Launchpad Team,
I can't play live videos from Youtube. I have problem only with live
transmission. Normal videos works fine. I noticed that I also have
this same problem on Focal (now I checked this on Bionic - Ubuntu
18.04.5). On Lubuntu 18.04.5 on other machine I don't have this
problem. I can play on Lubuntu all Youtube videos. What is a problem?
Do you know? I think that by default Ubuntu have not necessary package
to play live videos on Youtube. Have I right or this is a bug? On
Answers section on launchpad anyone can't tell me if it is a bug so
this is why I report this bug now. If it is not a bug I am very sorry
and you can delete this report now.
Example I have problem with this video:
https://www.youtube.com/watch?v=21X5lGlDOfg
I used debugger by youtube and this is output of this:
"debug_error": {
"errorCode": "html5.unsupportedlive",
"errorMessage": "Ten format wideo nie jest obsługiwany.",
"Nx": "HTML5_NO_AVAILABLE_FORMATS_FALLBACK",
"cj": "","
If it is a bug can you fix it?
UPDATE: Today I updated my firefox to the newest version 86.0. This
bug still exists.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916301/+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 1891270] Re: Iranian calendar shows in Azerbaijani language
I have this problem too! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1921595] Re: Screen flickers in Ubuntu Mate 21.04 and Ubuntu Unity 21.04
*** This bug is a duplicate of bug 1867668 *** https://bugs.launchpad.net/bugs/1867668 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1867668, so it 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. Feel free to continue to report any other bugs you may find. ** Tags added: groovy hirsute ** This bug has been marked a duplicate of bug 1867668 Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver -- 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/1921595 Title: Screen flickers in Ubuntu Mate 21.04 and Ubuntu Unity 21.04 Status in xorg package in Ubuntu: New Bug description: On upgrading from Ubuntu Mate 20.10 to 21.04 I observed screen flickering. I observed the same on clean install of Ubuntu Unity. I eventually fixed this by following this advice: https://askubuntu.com/questions/1231441/ubuntu-screen- flickering/1231443#1231443 Create file /etc/X11/xorg.conf.d/20-intel.conf : Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" EndSection My graphics card is Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1921595/+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 1518411] Re: "Maximum number of clients reached", new in Ubuntu 15.10
** Changed in: xorg-server (Ubuntu) Status: Fix Released => Confirmed ** Changed in: compiz Status: Fix Released => Confirmed ** Changed in: compiz (Ubuntu) Status: Fix Released => Triaged -- 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/1518411 Title: "Maximum number of clients reached", new in Ubuntu 15.10 Status in Compiz: Confirmed Status in compiz package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: In my newly upgraded (from 15.04) Ubuntu 15.10 system, after I've been logged in for a while I can no longer open new windows and instead get a "Maximum number of clients reached" error. This did not happen in 15.04. I ran "lsof" on the X server and did not see an excessive number of open file descriptors. I ran it again on a newly restarted X server and the number of open file descriptors looked about the same. I also ran "xlsclients" when the X server was reporting "Maximum number of clients reached" and the list of clients looked correct and reasonable (and there were less than 30 of them). I am happy to collect any additional logs or debugging information to help track this down. I don't know where to look further. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 20 13:00:09 2015 DistUpgraded: 2015-11-17 11:59:09,835 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.4, 3.19.0-33-generic, x86_64: installed virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:7410] MachineType: System76, Inc. Galago UltraPro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=821f94aa-97e2-4384-8494-9f510a75877b ro i915.disable_power_well=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-11-17 (3 days ago) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Nov 20 12:51:23 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1518411/+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 1920682] Re: Lenovo x1 Yoga freeze after stylus touches the display
*** This bug is a duplicate of bug 1920632 *** https://bugs.launchpad.net/bugs/1920632 I confirm this bug on Thinkpad Yoga X11 gen.3 Laptop freezes completely and it cannot even be rebooted. The only solution was to let it drain the battery before charging to reboot. This is a very ugly bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1920682 Title: Lenovo x1 Yoga freeze after stylus touches the display Status in libwacom package in Ubuntu: Confirmed Bug description: Had no problem with stylus. Since one of the last updates the stylus freezes the notebook. No reaction to nothing. Only power off by holding hardware button works. Is also mentionned in https://askubuntu.com/questions/1324000/thinkpad-yoga-x1-gen-2 -freezes-completely-when-stylus-is-used-ubuntu-20-04-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1920682/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
** Changed in: network-manager (Ubuntu) Status: Fix Released => Invalid ** Changed in: network-manager (Ubuntu Precise) Status: Fix Released => Invalid ** Changed in: dnsmasq (Ubuntu) Status: Fix Released => Triaged ** Changed in: dnsmasq (Ubuntu Precise) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Triaged Status in network-manager source package in Precise: Invalid Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1401488] Re: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption
** Changed in: glib2.0 (Ubuntu) Status: Fix Released => Triaged -- 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/1401488 Title: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption Status in GLib: Expired Status in Mir: Fix Released Status in Mir 0.9 series: Won't Fix Status in glib2.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Bug description: This happens randomly when using the phone ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.0.5+15.04.20141204-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf AssertionMessage: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** CrashCounter: 1 Date: Wed Dec 10 19:28:35 2014 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1417733344 GraphicsCard: InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141211-020204) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 9 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_message (do_abort=, fmt=0xb68e3628 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (action=1, str=0xb68e366c "corrupted double-linked list", ptr=) at malloc.c:4996 malloc_consolidate (av=av@entry=0xaa800010) at malloc.c:4165 _int_malloc (av=av@entry=0xaa800010, bytes=bytes@entry=1264) at malloc.c:3423 __GI___libc_malloc (bytes=1264) at malloc.c:2891 Title: unity-system-compositor assert failure: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.58-2 version.lightdm: lightdm 1.13.0-0ubuntu2 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1401488/+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 1891270] Re: Iranian calendar shows in Azerbaijani language
I also have this bug in the last daily build on all flavors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
@Daniel van Vugt - Thank you for suggesting the change in post #60. It didn't work for me though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: In Progress Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1401488] Re: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption
** Changed in: glib2.0 (Ubuntu) Status: Triaged => Fix Released -- 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/1401488 Title: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption Status in GLib: Expired Status in Mir: Fix Released Status in Mir 0.9 series: Won't Fix Status in glib2.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Bug description: This happens randomly when using the phone ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.0.5+15.04.20141204-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf AssertionMessage: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** CrashCounter: 1 Date: Wed Dec 10 19:28:35 2014 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1417733344 GraphicsCard: InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141211-020204) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 9 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_message (do_abort=, fmt=0xb68e3628 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (action=1, str=0xb68e366c "corrupted double-linked list", ptr=) at malloc.c:4996 malloc_consolidate (av=av@entry=0xaa800010) at malloc.c:4165 _int_malloc (av=av@entry=0xaa800010, bytes=bytes@entry=1264) at malloc.c:3423 __GI___libc_malloc (bytes=1264) at malloc.c:2891 Title: unity-system-compositor assert failure: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.58-2 version.lightdm: lightdm 1.13.0-0ubuntu2 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1401488/+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 1915605] Re: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5
Bug still exists in Mozilla Firefox 87.0. Ubuntu 20.04.2.0 don't have this issue. Problem only in Bionic system. When you will fix this issue? -- 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/1915605 Title: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5 Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I have problem with Firefox on Ubuntu 18.04.5 system. When I run firefox this loading too long (circle spinning - animation of my cursor). I noticed this bug also on Xubuntu 18.04.4 on another computer. On Lubuntu 18.04.5 system on another computer I don't have these kind of bug so it is problem with Ubuntu and Xubuntu system. On Ubuntu 20.04 and Ubuntu 20.04.1 I don't have these bug. Of course I have updated system. I noticed also that if I will run firefox for the first time after booting my system this bug is not exist. I have this bug for the second run of the firefox and next. I have this problem also booting my computer with live USB with clear system image with Ubuntu 18.04.5. Like I earlier said this is problem with the system. When I use Ubuntu 20.04 I don't have this problem. My system is clean this is fresh install. I don't know what is problem but I am sure that everyone with Ubuntu 18.04.5 have this problem. Firefox is the newest 85.0.1 version. On older vesion I also had this problem in Ubuntu 18.04.5. Firefox start with no errors. No errors is a shown in terminal. Problem is with spinning with the cursor. When I run firefox cursor is spinning but firefox normally works. This cursor spinning only when I move this cursor on GNOME environment (top of the screen I don't know what is the name of this. This is graphic bar? When I run firefox in this "graphic bar" are shown name of the program (in my case firefox). On Ubuntu 20.04 my cursor doesn't spinning. Like I said this is problem only with Ubuntu 18.04.5 and Xubuntu 18.04.4 system. So this is the problem with bionic family but on Lubuntu 18.04.4 and 18.04.5 and doesn't have this problem too. I tried reinstall firefox but this doesn't help. I also deleted files for firex in /home but this also doesn't help. I think that this problem is more complicated. Can you fix it? I am sure that everyone have this problem. Some output from terminal: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 UPDATE: Today I updated to the newest version of the firefox - 86.0 and bug still exists. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1915605/+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 1921802] [NEW] Realtek ALC294 Recording problem, all sound output piped through input
Public bug reported: I have encountered an issue with Ubuntu 21.04 where any audio output is piped to the mic in incorrectly. This is happening by default when using the 3.5 aux in & out ports. This would be great if I wanted a loopback but I don't. This fundamentally breaks my workflow and would like to find a resolution, but no idea what else to try. This seems to happens on both the default pulseaudio server & force switching to pipewire Microphone is a vmoda boom pro PC is a lenovo thinkcentre m910q tiny which has: - 1x mic jack - 1x combo headphone/mic jack - running on the realtek alc294 I have tested this by recording with parec with the physical microphone switch off and on, with a youtube video playing in the background. I have also done the same test with microphone detached from headphones and it still is piped through. All audio is recorded, which to me seems to confirm there is an issue/bug somewhere in the audio stack. I have only found one other example of this happening, where that was on a different distro (manjaro) & reporter said to use usb, where I am using aux/ 3.5mm plugs. However, that thread just stopped with no resolution: https://forum.manjaro.org/t/all-the-sound-is-going-through- my-microphone/41760/10 I have attempted the tests in that thread, and I can confirm that there is some sort of software cross talk happening here. I have also attempted both recommendation for hdajackretask, and setting custom quirks in alsa-base.conf in this thread: https://superuser.com/questions/1312970/headset-microphone-not-detected- by-pulse-und-alsa hdajackretask was tried to get the combo headphone/mic jack to work, but did not find any setting to get that to work. Using two separate plugs, headphones & microphone do work, so not an issue with the pin setup. I tried the specific quirk for this codec, alc294-lenovo-mic, but that did not work either. Have tried: options snd-hda-intel model=alc294-lenovo-mic options snd-hda-intel model=headset-mic options snd-hda-intel model=dell-headset-multi In all variations, but this does not solve the issue of all of my audio is getting sent through the input for no good reason. I am not sure how else to debug at this point and looking for any insight possible. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 5.11.0-051100rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 29 20:41:36 2021 InstallationDate: Installed on 2021-02-05 (52 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) 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:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Pink Mic, Front Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [10MV000MUS, Realtek ALC294, Pink Mic, Front] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2018 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: M1AKT3BA dmi.board.name: 310B dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305150443148 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrM1AKT3BA:bd09/18/2018:br1.41:efr1.18:svnLENOVO:pn10MV000MUS:pvrThinkCentreM910q:rvnLENOVO:rn310B:rvrSDK0J40697WIN3305150443148:cvnLENOVO:ct35:cvrNone: dmi.product.family: ThinkCentre M910q dmi.product.name: 10MV000MUS dmi.product.sku: LENOVO_MT_10MV_BU_Think_FM_ThinkCentre M910q dmi.product.version: ThinkCentre M910q dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-29T17:12:38.893779 ** 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/1921802 Title: Realtek ALC294 Recording problem, all sound output piped through input Status in alsa-driver package in Ubuntu: New Bug description: I have encountered an issue with Ubuntu 21.04 where any audio output is piped to the mic in incorrectly. This is happening by default when using the 3.5 aux in & out ports. This would be great if I wanted a loopback but I don't. This fundamentally breaks my workflow and would like to find a resolution, but no idea what else to try. This seems to happens on both the default pulseaudio server & force switching to pipewire Microphone is a vmoda boom pro PC is a lenovo thinkcentre m910q tiny which has: - 1x mic jack -
[Desktop-packages] [Bug 1921764] Re: Bug affichage.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thank you! -- 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/1921764 Title: Bug affichage. Status in xorg package in Ubuntu: New Bug description: Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 29 17:55:52 2021 DistUpgraded: 2021-03-27 13:26:19,628 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:e147] InstallationDate: Installed on 2021-03-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. P35-DS4 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=040b03c4-747a-4dce-8e7a-5cbea40e1985 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2021-03-27 (2 days ago) dmi.bios.date: 05/11/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: P35-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/11/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Mar 29 17:47:30 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech M315/M235 MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1921764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I guess this bug has been solved. As stated in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 by @rmeissn, from gnome-settings, when the headset is connected, you can switch from HSP/HFP to A2DP. Once changed this setting my headsed sounds perfectly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~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 1765363] Re: prime-select intel is not powering off the nvidia card
On-demand mode does not have this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1920682] Re: Lenovo x1 Yoga freeze after stylus touches the display
*** This bug is a duplicate of bug 1920632 *** https://bugs.launchpad.net/bugs/1920632 @RazTaz : you can force shutdown of the Thinkpad Yoga X11 by pressing the power button during more than 5 seconds. By the way, there is a fix of this bug (see https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-5.8/+bug/1920632) with a patch on the kernel (5.8.45) that can be installed via proposed channel (see https://wiki.ubuntu.com/Testing/EnableProposed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1920682 Title: Lenovo x1 Yoga freeze after stylus touches the display Status in libwacom package in Ubuntu: Confirmed Bug description: Had no problem with stylus. Since one of the last updates the stylus freezes the notebook. No reaction to nothing. Only power off by holding hardware button works. Is also mentionned in https://askubuntu.com/questions/1324000/thinkpad-yoga-x1-gen-2 -freezes-completely-when-stylus-is-used-ubuntu-20-04-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1920682/+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 1921583] Re: Can't run System Monitor in Ubuntu Unity 21.04
@seb128, the crash in my opinion is not related to the theme, but rather the same as reported upstream https://gitlab.gnome.org/GNOME/gnome- system-monitor/-/issues/182, coming from the migration to LibHandy, on non-GNOME environments. The issue was fixed upstream with commit https://gitlab.gnome.org/GNOME/gnome-system- monitor/-/commit/69224a7b27a85e7485fb47f9e9f14ce674798c28 on master and with commit https://gitlab.gnome.org/GNOME/gnome-system- monitor/-/commit/ba93af5b3e429db5a9c4dd7e2d06b800735a9071 on the gnome-40 stable branch, and will be available with the next stable release. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues #182 https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/182 ** Also affects: libgtop via https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/182 Importance: Unknown Status: Unknown ** No longer affects: libgtop ** Also affects: gnome-system-monitor via https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/182 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1921583 Title: Can't run System Monitor in Ubuntu Unity 21.04 Status in Gnome System Monitor: Unknown Status in gnome-system-monitor package in Ubuntu: Incomplete Bug description: I can't run System Monitor in Ubuntu Unity 21.04. I reported a bug on Ubuntu Unity's tracker, but I've been told to report it here. https://gitlab.com/ubuntu-unity/ubuntu-unity- issues/-/issues/82#note_539356065 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-system-monitor 40.0-1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 27 15:32:16 2021 InstallationDate: Installed on 2021-03-27 (0 days ago) InstallationMedia: Ubuntu Unity 21.04 SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1921583/+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 1886092] Re: libreoffice doesn't list gpg private key for a digital signature due to apparmor
This bug was fixed in the package libreoffice - 1:7.1.2~rc2-0ubuntu1
---
libreoffice (1:7.1.2~rc2-0ubuntu1) hirsute; urgency=medium
[ Rico Tzschichholz ]
* New upstream release candidate
* Bump yaru source to "2021-03-14" and add yaru-mate styles
* Fix signing documents with enforced apparmor (LP: #1886092)
* Disable lto due to insufficient disc space on amd64 builder
[ Matthias Klose ]
* Fix lto build, avoiding to pass lto flags to the skia build.
-- Rico Tzschichholz Sat, 27 Mar 2021 16:01:35
+0100
** Changed in: libreoffice (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
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/1886092
Title:
libreoffice doesn't list gpg private key for a digital signature due
to apparmor
Status in libreoffice package in Ubuntu:
Fix Released
Status in libreoffice source package in Focal:
Confirmed
Status in libreoffice source package in Groovy:
New
Status in libreoffice source package in Hirsute:
Fix Released
Bug description:
LibreOffice should be able to digitally sign a document with a GPG
private key in the GPG key chain. However, the key is not listed in
the list of certificates shown following the menu File - Digital
Signatures - Digital Signatures... - Sign Document..., after, e.g.,
creating and saving a document on LibreOffice Writer.
This seems to be because apparmor doesn't allow LibreOffice to
communicate with GPG agent. /var/log/syslog shows lines like:
Jul 1 15:15:14 misoan kernel: [20238.265212] audit: type=1400
audit(1593652514.311:333): apparmor="DENIED" operation="connect"
profile="libreoffice-soffice//gpg" name="/run/user/1001/gnupg/S.gpg-
agent" pid=23725 comm="gpg" requested_mask="wr" denied_mask="wr"
fsuid=1001 ouid=1001
Locally, I could make LibreOffice show the GPG private key with the
following change against
/etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin
--- apparmor.d.20200702/usr.lib.libreoffice.program.soffice.bin
2019-10-03 10:31:21.0 -1000
+++ apparmor.d/usr.lib.libreoffice.program.soffice.bin2020-07-02
08:59:44.516754728 -1000
@@ -223,6 +223,7 @@
owner @{HOME}/.gnupg/* r,
owner @{HOME}/.gnupg/random_seed rk,
+owner /{,var/}run/user/*/** rw,
}
# probably should become a subprofile like gpg above, but then it doesn't
Tested with the following packages on Xfce4
$ lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
$ apt-cache policy libreoffice-common | grep Installed
Installed: 1:6.4.3-0ubuntu0.20.04.1
$ apt-cache policy gpg gpg-agent | grep -B1 Installed
gpg:
Installed: 2.2.19-3ubuntu2
--
gpg-agent:
Installed: 2.2.19-3ubuntu2
$ apt-cache policy apparmor | grep Installed
Installed: 2.13.3-7ubuntu5.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886092/+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 1872377] Re: No menus in Unity after upgrading to 20.04
*** This bug is a duplicate of bug 1890049 ***
https://bugs.launchpad.net/bugs/1890049
** This bug has been marked a duplicate of bug 1890049
global menu bar no longer supported after 20.04 upgrade
--
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/1872377
Title:
No menus in Unity after upgrading to 20.04
Status in firefox package in Ubuntu:
Won't Fix
Bug description:
In Ubuntu 19.10, the Firefox menus appeared as normal. After upgrading
to Ubuntu 20.04 beta, with Firefox 75.0+build3-0ubuntu1, the Firefox
menus no longer appear either on the window or the title bar. This
happens both when the window is maximised and when it isn't.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 75.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alistair 2490 F pulseaudio
BuildID: 20200403170909
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Apr 13 09:55:56 2020
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
dns-search integrics.com
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2017-08-16 (970 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
default via 10.12.0.1 dev enp0s31f6 proto dhcp metric 100
10.12.0.0/21 dev enp0s31f6 proto kernel scope link src 10.12.3.219 metric
100
169.254.0.0/16 dev enp0s31f6 scope link metric 1000
MostRecentCrashID: bp-3d145359-2f62-4b35-a046-86be50191125
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:733
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=75.0/20200403170909 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-04-12 (0 days ago)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET57W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN1WET57W(1.36):bd11/29/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872377/+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 1859123] Re: No global menus (panel-appmenu / dbus) in Firefox 72.0.1
*** This bug is a duplicate of bug 1890049 *** https://bugs.launchpad.net/bugs/1890049 ** This bug has been marked a duplicate of bug 1890049 global menu bar no longer supported after 20.04 upgrade -- 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/1859123 Title: No global menus (panel-appmenu / dbus) in Firefox 72.0.1 Status in firefox package in Ubuntu: Won't Fix Bug description: No global menus are displayed in latest Firefox 72.0.1 (possibly in a slightly earlier version). This issue was observed on three different systems all running Ubuntu MATE 20.04 Focal (development), and I first noticed it on each system upon updating to 72.0.1 today. The symptoms are identical to https://bugs.launchpad.net/ubuntu- mate/+bug/1743687 , but running `env UBUNTU_MENUPROXY=0 firefox` does not resolve the issue. `env UBUNTU_MENUPROXY=1 firefox` does not resolve the issue either. My first guess is that the issue is a change in Firefox, due to how the previous solution with the environment variable no longer works. (Perhaps a change to the Unity menu patch?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859123/+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 1921588] Re: Firefox doesn't support HUD
*** This bug is a duplicate of bug 1890049 *** https://bugs.launchpad.net/bugs/1890049 This is bug #1890049, and it's indeed marked "Won't Fix", see rationale in that other bug report. ** This bug has been marked a duplicate of bug 1890049 global menu bar no longer supported after 20.04 upgrade -- 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/1921588 Title: Firefox doesn't support HUD Status in firefox package in Ubuntu: New Status in mate-hud package in Ubuntu: New Bug description: Currently, Firefox doesn't support HUD ( `mate-hud`, I assume Unity's HUD is also affected as per https://ubuntuunity.org/2020/06/05/hud- globalmenu-firefox/ ), as Martin Wimpress said in his Wimpy's World Discord server 27/03/2021 15:12 UTC 'Some apps are removing support for ModelMenu. That used to be a patch that Canonical contributed to Firefox, which is long since dropped.' Filing this bug as maybe a community member would want to re-introduce this patch. But if this is a Won't Fix please mark it as such, just wanted to get the issue logged as I can't find it elsewhere on Launchpad. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 8178 F pulseaudio /dev/snd/pcmC0D0p: adam 8178 F...m pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: MATE Date: Sat Mar 27 15:41:07 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2019-10-11 (532 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) IpRoute: default via 192.168.43.1 dev wlp3s0 proto dhcp metric 600 10.88.254.0/24 dev lxdbr0 proto kernel scope link src 10.88.254.1 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.43.0/24 dev wlp3s0 proto kernel scope link src 192.168.43.188 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=69.0.3/20191010103742 (Out of date) Profile0 - LastVersion=87.0/20210318103112 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2009 dmi.bios.release: 8.0 dmi.bios.vendor: AMI dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MCP73T-AD dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAMI:bvrP01-A3:bd06/06/2009:br8.0:svnPackardBell:pnimediaS1710:pvr:rvnPackardBell:rnMCP73T-AD:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: imedia S1710 dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1921588/+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 1921687] [NEW] gnome-calendar doesn't import ics files correctly
Public bug reported: gnome-calendar doesn't import ics files correctly. 1. I downloaded public ics files like https://www.calendarlabs.com/ical- calendar/ics/76/US_Holidays.ics Their entries were shown in gnome- calendar, but not in gnome's date & time. In gnome-calendar they had an end date before the start date. The ics files from calendarlabs don't implement the standard from https://tools.ietf.org/html/rfc5545#section-3.6.1 for VEVENTs correctly. While the DATE from DTSTART is inclusive, the DATE from DTEND isn't. For a one day event DTEND's DATE has therefore to be one day after DTSTART's date. Some programs correct this by simply increasing DTEND by one day in these cases and gnome-calendar should do that too. As no event can end before it starts, gnome-calendar's behavior of setting the end date before the start date doesn't make sense. 2. If a VEVENT has a DTSTART property with a DATE but no DURATION and no DTEND property, according to https://tools.ietf.org/html/rfc5545#section-3.6.1 "the event's duration is taken to be one day." I therefore deleted the DTEND property in for instance US_Holidays.ics and expected that now gnome-calendar would import the ics file's VEVENTS correctly. But even in this case of standard conforming ics files gnome-calendar imported them with an end date before the start date. This time without the need to correct an error, but simply the need to implement a standard correctly. In both cases gnome-calendar shouldn't produce events with a end date before the start date. I used apport but again: I have ubuntu 20.04.2 LTS and an up to date gnome-calendar 3.36.2-0ubuntu1. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 29 02:46:12 2021 InstallationDate: Installed on 2018-08-10 (961 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (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-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1921687 Title: gnome-calendar doesn't import ics files correctly Status in gnome-calendar package in Ubuntu: New Bug description: gnome-calendar doesn't import ics files correctly. 1. I downloaded public ics files like https://www.calendarlabs.com /ical-calendar/ics/76/US_Holidays.ics Their entries were shown in gnome-calendar, but not in gnome's date & time. In gnome-calendar they had an end date before the start date. The ics files from calendarlabs don't implement the standard from https://tools.ietf.org/html/rfc5545#section-3.6.1 for VEVENTs correctly. While the DATE from DTSTART is inclusive, the DATE from DTEND isn't. For a one day event DTEND's DATE has therefore to be one day after DTSTART's date. Some programs correct this by simply increasing DTEND by one day in these cases and gnome-calendar should do that too. As no event can end before it starts, gnome-calendar's behavior of setting the end date before the start date doesn't make sense. 2. If a VEVENT has a DTSTART property with a DATE but no DURATION and no DTEND property, according to https://tools.ietf.org/html/rfc5545#section-3.6.1 "the event's duration is taken to be one day." I therefore deleted the DTEND property in for instance US_Holidays.ics and expected that now gnome- calendar would import the ics file's VEVENTS correctly. But even in this case of standard conforming ics files gnome-calendar imported them with an end date before the start date. This time without the need to correct an error, but simply the need to implement a standard correctly. In both cases gnome-calendar shouldn't produce events with a end date before the start date. I used apport but again: I have ubuntu 20.04.2 LTS and an up to date gnome-calendar 3.36.2-0ubuntu1. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 29 02:46:12 2021 InstallationDate: Installed on 2018-08-10 (961 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar
[Desktop-packages] [Bug 1890049] Re: global menu bar no longer supported after 20.04 upgrade
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1890049 ** Tags added: iso-testing -- 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/1890049 Title: global menu bar no longer supported after 20.04 upgrade Status in firefox package in Ubuntu: Won't Fix Bug description: 1) version: 79.0+build1-0ubuntu0.20.04.1 500 2) Ubuntu Release : Ubuntu 20.04.1 LTS 3) What I expected to happen: In Unity DE. menu bars are integrated with title bar or top panel when maximized 4) What happened instead: Menu bar doesn't integrate. Takes too much vertical space. Problematic because I have made a jump to wide screens around 2012. I guess decision makers at ubuntu still enjoy 4:3 screens and thus don't see the value in DEs that optimize vertical space. But it would be really nice to have a hand here. The current workaround is to disable the menu bar, which leaves me at the mercy of the hamburger menu. The hamburger menu is an implant from old Mobile App Design. But nowadays even Mobile App UX designers decry the Hamburger menu and in a desktop it makes little sense. Firefox is a good example because the menu bar has sections like History which are a lot richer than what's available to be accessed from the hamburger menu. It's really just not possible to have as many menu options and categories as a menu bar in a hamburger menu. And access is less efficient -> more mouse movement -> more mouse clicks. So I have to choose between wasting space unnecessarily with a menu bar that does not integrate with the top panel OR losing a lot of access to options and settings by removing the menu bar and using the hamburger menu instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1890049/+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 1825983] Re: chromium-browser ignores system proxy settings
UPD: I have installed Google Chrome 89.0.4389.90 (Official Build), it works properly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1825983 Title: chromium-browser ignores system proxy settings Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.2 chromium-browser 73.0.3683.86 Network proxy is configured via Settings GUI dialog. chromium-browser is started with verbose output: [9810:9810:0423/134338.510775:VERBOSE1:proxy_config_service_linux.cc(484)] All gsettings tests OK. Will get proxy config from gsettings. [9810:9810:0423/134338.510926:VERBOSE1:proxy_config_service_linux.cc(1243)] Obtained proxy settings from annotation hash code 11258689 [9810:9810:0423/134338.510949:VERBOSE1:pref_proxy_config_tracker_impl.cc(184)] 0x55e7b2944b00: set chrome proxy config service to 0x55e7b27e3f10 Listing all gsettings with proxy: ~$ gsettings list-recursively | grep proxy will return: org.gnome.system.proxy.http host 'gse.auk.cvclab.lan' org.gnome.system.proxy.http port 9191 org.gnome.system.proxy.http use-authentication false org.gnome.system.proxy.http authentication-password '' org.gnome.system.proxy.http authentication-user '' org.gnome.system.proxy.http enabled false org.gnome.evolution.shell.network-config proxy-type 0 org.gnome.evolution.shell.network-config use-http-proxy false org.gnome.system.proxy.https host '' org.gnome.system.proxy.https port 0 org.gnome.system.proxy.socks host '' org.gnome.system.proxy.socks port 0 org.gnome.system.proxy.ftp host '' org.gnome.system.proxy.ftp port 0 org.gnome.system.proxy use-same-proxy true org.gnome.system.proxy mode 'manual' org.gnome.system.proxy autoconfig-url '' org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8', '::1'] org.gnome.settings-daemon.plugins.screensaver-proxy active true org.gnome.settings-daemon.plugins.screensaver-proxy priority 0 chromium-browsers fails to connect to the internet with the error message: ERR_CONNECTION_TIMED_OUT Starting chromium-browser with the proxy command line parameter: ~$ chromium-browser --proxy-server="gse.auk.cvclab.lan:9191" This starts the browser and the internet connection works fine. With Firefox there are no issues, it works with the configured system proxy settings. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1825983/+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 1825983] Re: chromium-browser ignores system proxy settings
I experience the same issue on Ubuntu 20.04. Neither manual proxy settings, nor PAC file helps. Additionally, I've exported http_proxy and https_proxy environment variables wherever I could (.bashrc, .zshrc, /etc/environment) I suppose, the fact that my PC is in the domain or that it has multiple admin users may play a role... but how? I tried that hack with changing .desktop file https://askubuntu.com/questions/513840/google-chrome-proxy-settings But I found my executable in /snap/chromium/1528/bin/chromium.desktop and did not succeed to find the way to edit it (read-only file system). Moreover, this file will be rewritten during package update. I am totally dissatisfied with the fact that I should run chromium via terminal or create some desktop shortcuts. Is there any hope that the issue will be fixed? What can I do for that? P.S. I've tried Chromium 89.0.4389.90 - 91.0.4455.2, no one works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1825983 Title: chromium-browser ignores system proxy settings Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.2 chromium-browser 73.0.3683.86 Network proxy is configured via Settings GUI dialog. chromium-browser is started with verbose output: [9810:9810:0423/134338.510775:VERBOSE1:proxy_config_service_linux.cc(484)] All gsettings tests OK. Will get proxy config from gsettings. [9810:9810:0423/134338.510926:VERBOSE1:proxy_config_service_linux.cc(1243)] Obtained proxy settings from annotation hash code 11258689 [9810:9810:0423/134338.510949:VERBOSE1:pref_proxy_config_tracker_impl.cc(184)] 0x55e7b2944b00: set chrome proxy config service to 0x55e7b27e3f10 Listing all gsettings with proxy: ~$ gsettings list-recursively | grep proxy will return: org.gnome.system.proxy.http host 'gse.auk.cvclab.lan' org.gnome.system.proxy.http port 9191 org.gnome.system.proxy.http use-authentication false org.gnome.system.proxy.http authentication-password '' org.gnome.system.proxy.http authentication-user '' org.gnome.system.proxy.http enabled false org.gnome.evolution.shell.network-config proxy-type 0 org.gnome.evolution.shell.network-config use-http-proxy false org.gnome.system.proxy.https host '' org.gnome.system.proxy.https port 0 org.gnome.system.proxy.socks host '' org.gnome.system.proxy.socks port 0 org.gnome.system.proxy.ftp host '' org.gnome.system.proxy.ftp port 0 org.gnome.system.proxy use-same-proxy true org.gnome.system.proxy mode 'manual' org.gnome.system.proxy autoconfig-url '' org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8', '::1'] org.gnome.settings-daemon.plugins.screensaver-proxy active true org.gnome.settings-daemon.plugins.screensaver-proxy priority 0 chromium-browsers fails to connect to the internet with the error message: ERR_CONNECTION_TIMED_OUT Starting chromium-browser with the proxy command line parameter: ~$ chromium-browser --proxy-server="gse.auk.cvclab.lan:9191" This starts the browser and the internet connection works fine. With Firefox there are no issues, it works with the configured system proxy settings. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1825983/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Description changed: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. + Cases where the crash can be triggered: + + - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE + - Start the ISO on real hardware in 'safe graphics mode' + + Cases where the crash is not encountered: + - Start the ISO on real intel (HD graphics) hardware with full acceleration. + + NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to + the previous 20.3.4 in hirsute. + Try/Install crash: - Screen fails to start, or starts then crashes on any user action. The + Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021
[Desktop-packages] [Bug 1921707] [NEW] CTRL-TAB word completion does not work
Public bug reported: My system is Kubuntu 20.04 with Ubuntu Studio installed on an HP ZBook 15 G3. In Libreoffice Writer, the cycling through word completion suggestions with CTRL-TAB doesn't work - instead it inserts a tab stop as if I only hit the TAB key. Other keyboard shortcuts involving the CTRL key, like CTRL-S, CTRL-V, CTRL-Z, etc works as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-70.78-lowlatency 5.4.94 Uname: Linux 5.4.0-70-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Mar 29 09:31:41 2021 InstallationDate: Installed on 2021-02-07 (49 days ago) InstallationMedia: Kubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1921707 Title: CTRL-TAB word completion does not work Status in libreoffice package in Ubuntu: New Bug description: My system is Kubuntu 20.04 with Ubuntu Studio installed on an HP ZBook 15 G3. In Libreoffice Writer, the cycling through word completion suggestions with CTRL-TAB doesn't work - instead it inserts a tab stop as if I only hit the TAB key. Other keyboard shortcuts involving the CTRL key, like CTRL-S, CTRL-V, CTRL-Z, etc works as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-70.78-lowlatency 5.4.94 Uname: Linux 5.4.0-70-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Mar 29 09:31:41 2021 InstallationDate: Installed on 2021-02-07 (49 days ago) InstallationMedia: Kubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1921707/+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 1883370] Re: system-config-printer hangs when trying to change driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1883370 Title: system-config-printer hangs when trying to change driver Status in System Config Printer: Fix Released Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Confirmed Status in system-config-printer source package in Groovy: Confirmed Bug description: gnome-control-center is able to find and install my network printer (Samsung M287x) automatically. When I attempt to change the printer driver (default printer driver doesn't support duplex printing) via system-config-printer, system-config-printer will hang. Please see attached log captured via system-config-printer --debug. I am running stock Ubuntu 20.04. Changing the driver worked fine in ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 13 10:34:15 2020 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2020-05-17 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for M267x-287x: socket://192.168.1.166 MachineType: LENOVO 20KHCTO1WW PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M267x-287x.ppd'] failed with exit code 2: grep: /etc/cups/ppd/M267x-287x.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d86e16c0-e48c-492e-9cf8-05a068340cd7 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1883370/+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 1915887] Re: systemd spams the syslog about lack of native systemd unit file
Hello Rolf, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native
[Desktop-packages] [Bug 1883370] Re: system-config-printer hangs when trying to change driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1883370 Title: system-config-printer hangs when trying to change driver Status in System Config Printer: Fix Released Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Confirmed Status in system-config-printer source package in Groovy: Confirmed Bug description: gnome-control-center is able to find and install my network printer (Samsung M287x) automatically. When I attempt to change the printer driver (default printer driver doesn't support duplex printing) via system-config-printer, system-config-printer will hang. Please see attached log captured via system-config-printer --debug. I am running stock Ubuntu 20.04. Changing the driver worked fine in ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 13 10:34:15 2020 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2020-05-17 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for M267x-287x: socket://192.168.1.166 MachineType: LENOVO 20KHCTO1WW PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M267x-287x.ppd'] failed with exit code 2: grep: /etc/cups/ppd/M267x-287x.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d86e16c0-e48c-492e-9cf8-05a068340cd7 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1883370/+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 1921618] Re: Black wallpaper instead than set image
** Package changed: xorg (Ubuntu) => nautilus (Ubuntu) ** Also affects: compiz (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/1921618 Title: Black wallpaper instead than set image Status in compiz package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: The image set as wallpaper appears for one second and then is replaced by a black screen. This occurs after a hard reset. After a suspension: nothing worked and I had to do a hard reset by switching the machine off. At restart I'm in the mentioned situation and the usual methods to reset the wall paper do not fix the problem. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 28 13:23:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a7] InstallationDate: Installed on 2017-06-16 (1381 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 005: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=0db16900-e9f1-49a7-b5db-508d231aac23 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0NDFXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0NDFXD:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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/compiz/+bug/1921618/+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 1915887] Re: systemd spams the syslog about lack of native systemd unit file
Hello Rolf, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service
[Desktop-packages] [Bug 1921532] Re: scanning multiple pages from flatbed results in error message but scan works
Could you please build the latest version of Simple-scan and check if this issue is still existing. The instruction is here: https://gitlab.gnome.org/GNOME/simple-scan/-/blob/master/README.md#building-manually-from-source It will greatly speedup the resolving time. ** Changed in: simple-scan (Ubuntu) Status: New => Confirmed ** Changed in: simple-scan (Ubuntu) Assignee: (unassigned) => Bartosz Kosiorek (gang65) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1921532 Title: scanning multiple pages from flatbed results in error message but scan works Status in simple-scan package in Ubuntu: Confirmed Bug description: when I select "Multiple Pages From Flatbed" it results in an error message after every page (screenshot attached) - Failed to scan - Unable to start scan [close] but it works well. so.. probably cosmetic. by the way: This application is dope - 100 times more accessible than xsane ^ ^ simple-scan 3.36.3 andreas@moya:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 What I expect: "Load next page and press 'scan'" What happened instead: Error message "unable to scan" - yet it scanned fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Mar 26 17:28:52 2021 InstallationDate: Installed on 2021-03-13 (13 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=c7c6bc8a-f29f-47f0-b26e-5e9a56b11128 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2018 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: JBET71WW (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET71WW(1.35):bd09/14/2018:br1.35:efr1.4:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921532/+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 1913439] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1913439/+attachment/5481901/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913439 Title: "Alert Sound" change has no effect at all Status in gnome-control-center package in Ubuntu: Expired Bug description: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.38.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Tags: third-party-packages groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913439/+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 1913439] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1913439/+attachment/5481902/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913439 Title: "Alert Sound" change has no effect at all Status in gnome-control-center package in Ubuntu: Expired Bug description: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.38.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Tags: third-party-packages groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913439/+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 1913439] Re: "Alert Sound" change has no effect at all
apport information ** Tags added: apport-collected third-party-packages ** Description changed: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-control-center 1:3.38.3-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 + Tags: third-party-packages groovy + Uname: Linux 5.8.0-48-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1913439/+attachment/5481900/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913439 Title: "Alert Sound" change has no effect at all Status in gnome-control-center package in Ubuntu: Expired Bug description: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.38.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Tags: third-party-packages groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913439/+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 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly
Minor progress: desktop-icons-ng emulates a traditional Xorg desktop window so is able to convince gnome-shell to fade the icons in/out properly. But only in Xorg sessions. -- 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/1847712 Title: Desktop icons vanishing when in Activities Overview is jarring and looks ugly Status in gnome-shell package in Ubuntu: In Progress Bug description: Desktop icons vanishing and reappearing when in Activities Overview is jarring and looks ugly. Suggestions: * Don't hide them in AO, because they will be well shaded anyway; or * Fade them out and in smoothly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 11 14:24:42 2019 InstallationDate: Installed on 2019-05-02 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847712/+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 1701243] Re: GDM does not work if gnome-session is not installed
** Changed in: gdm3 (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1701243 Title: GDM does not work if gnome-session is not installed Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 package in Debian: Fix Released Bug description: Test Case = Install Ubuntu 17.10 from a recent daily image. After install log in. sudo apt install gdm3 Choose gdm3 when prompted. Restart your computer. The bug is that gdm refuses to start Workaround == Install gnome-session More Info = For smoother upgrades and to allow the option of a more vanilla GNOME experience, it was decided to try to continue to use an ubuntu-session package by default containing an "ubuntu" session that identifies as "Ubuntu" and runs GNOME. We don't want or need the GNOME sessions in the default install. This is more fallout from https://git.gnome.org/browse/gdm/commit/?id=f66cdfcb so let's try reverting that change. See also LP: #1686257 and https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=850291 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1701243/+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 1921766] [NEW] Output device not remembered after connecting/disconnecting another
Public bug reported: Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for development work. I run it on a Lenovo X1 Carbon 8th Generation connected to dual monitors via a Lenovo dock. Both monitors are capable of outputting sound via HDMI. I use bluetooth headphones frequently with my Ubuntu 20.10 system, but I don't leave them on -- I turn them on and off as needed for Zoom calls. When I'm not on a call, however, I prefer to use my laptop's speakers for audio -- not my monitor speakers. Turning the bluetooth headphones on works fine, they connect and pulseaudio correctly identifies the new connection and switches to the headphones as the audio device. However, when I turn the headphones off, pulseaudio always selects an HDMI audio device as the sound device to use, not the internal speaker device that I was using prior to turning on the headphones. I must manually open Sound Settings and select the speaker device every time I turn my headphones off. My expectation is that the device I was using prior to connecting the headphones is remembered and switched back to by default after I disconnect my bluetooth headphones. I've tried using the pavucontrol app to disable the HDMI audio devices, but the hardware device disable settings are not granular enough to let me target the HDMI devices independently of the speaker device. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1921766 Title: Output device not remembered after connecting/disconnecting another Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for development work. I run it on a Lenovo X1 Carbon 8th Generation connected to dual monitors via a Lenovo dock. Both monitors are capable of outputting sound via HDMI. I use bluetooth headphones frequently with my Ubuntu 20.10 system, but I don't leave them on -- I turn them on and off as needed for Zoom calls. When I'm not on a call, however, I prefer to use my laptop's speakers for audio -- not my monitor speakers. Turning the bluetooth headphones on works fine, they connect and pulseaudio correctly identifies the new connection and switches to the headphones as the audio device. However, when I turn the headphones off, pulseaudio always selects an HDMI audio device as the sound device to use, not the internal speaker device that I was using prior to turning on the headphones. I must manually open Sound Settings and select the speaker device every time I turn my headphones off. My expectation is that the device I was using prior to connecting the headphones is remembered and switched back to by default after I disconnect my bluetooth headphones. I've tried using the pavucontrol app to disable the HDMI audio devices, but the hardware device disable settings are not granular enough to let me target the HDMI devices independently of the speaker device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1921766/+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 1921595] [NEW] Screen flickers in Ubuntu Mate 21.04 and Ubuntu Unity 21.04
You have been subscribed to a public bug: On upgrading from Ubuntu Mate 20.10 to 21.04 I observed screen flickering. I observed the same on clean install of Ubuntu Unity. I eventually fixed this by following this advice: https://askubuntu.com/questions/1231441/ubuntu-screen- flickering/1231443#1231443 Create file /etc/X11/xorg.conf.d/20-intel.conf : Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" EndSection My graphics card is Intel. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Screen flickers in Ubuntu Mate 21.04 and Ubuntu Unity 21.04 https://bugs.launchpad.net/bugs/1921595 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1921595] Re: Screen flickers in Ubuntu Mate 21.04 and Ubuntu Unity 21.04
** Package changed: ubuntu => xorg (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/1921595 Title: Screen flickers in Ubuntu Mate 21.04 and Ubuntu Unity 21.04 Status in xorg package in Ubuntu: New Bug description: On upgrading from Ubuntu Mate 20.10 to 21.04 I observed screen flickering. I observed the same on clean install of Ubuntu Unity. I eventually fixed this by following this advice: https://askubuntu.com/questions/1231441/ubuntu-screen- flickering/1231443#1231443 Create file /etc/X11/xorg.conf.d/20-intel.conf : Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" EndSection My graphics card is Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1921595/+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 1921764] [NEW] Bug affichage.
Public bug reported: Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 29 17:55:52 2021 DistUpgraded: 2021-03-27 13:26:19,628 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:e147] InstallationDate: Installed on 2021-03-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. P35-DS4 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=040b03c4-747a-4dce-8e7a-5cbea40e1985 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2021-03-27 (2 days ago) dmi.bios.date: 05/11/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: P35-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/11/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Mar 29 17:47:30 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech M315/M235 MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic compiz-0.9 i386 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/1921764 Title: Bug affichage. Status in xorg package in Ubuntu: New Bug description: Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 29 17:55:52 2021 DistUpgraded: 2021-03-27 13:26:19,628 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:e147] InstallationDate: Installed on 2021-03-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. P35-DS4 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=040b03c4-747a-4dce-8e7a-5cbea40e1985 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2021-03-27 (2 days ago) dmi.bios.date: 05/11/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: P35-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/11/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
[Desktop-packages] [Bug 1920121] Re: Unable to do anything after pressing the Super key
*** This bug is a duplicate of bug 1871262 *** https://bugs.launchpad.net/bugs/1871262 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1920121 Title: Unable to do anything after pressing the Super key Status in gnome-shell package in Ubuntu: Confirmed Bug description: I press super key, the various application windows appear on desktop but i'm unable to do anything: i can just click on the red 'X' top right of the window to close it but if i click on the window i can't get focus on it. to exit this situation i can only reboot so I was unable to open the problem while it was active. I can just attach the journal relative to it. The problem seems random, trying to reproduce it I had the problem 3 times out of 6 attempts. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 19 08:49:44 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-28 (18 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228) RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920121/+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 1917300] Re: updated firefox 86.0 (64 bit)
The fact that the problem doesn't happen in safe mode suggests that it's hardware-accelerated rendering/compositing that is to blame. After restarting firefox in normal mode, you might want to try instructions at https://support.mozilla.org/en-US/kb/upgrade-graphics- drivers-use-hardware-acceleration#w_i-still-have-problems-with-my- graphics-card-in-firefox. -- 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/1917300 Title: updated firefox 86.0 (64 bit) Status in firefox package in Ubuntu: Incomplete Bug description: updated firefox 86.0 (64 bit) starts and colored pixels blinking all around the screen; cannot use it any more. Using a ThinkPad SL 510, 4 GB RAM Ubuntu 20.04 LTS --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe 878 F pulseaudio /dev/snd/controlC1: joe 878 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-11-08 (137 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 169.254.0.0/16 dev enp8s0 scope link metric 1000 192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 metric 100 Package: firefox 87.0+build3-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=87.0/20210318103112 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2011 dmi.bios.release: 1.73 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET91WW (1.49 ) dmi.board.name: 28476NG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad SL510 dmi.product.name: 28476NG dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917300/+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 1919955] Re: weird graphics artifacts in Firefox on Xorg after upgrade
Thanks for following up rue. The recent mesa update suggests the problem was with that package, rather than with firefox itself. I'm closing the bug now, glad to know that the problem is resolved for you. ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- 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/1919955 Title: weird graphics artifacts in Firefox on Xorg after upgrade Status in firefox package in Ubuntu: Invalid Bug description: Hi, just updated today and after restart I logged in under Xorg and when opening Firefox you get blue and black pixelated static across the screen. this only happens running Xorg, not under Wayland. A bit hard to explain the issue, so added a screenshot Also this could be an Xorg issue It only seems to affect Firefox. Thanks Rue ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 86.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rue5652 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 18 18:12:48 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-03-16 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) IpRoute: default via 192.168.1.254 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.70 metric 100 ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2010 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786H1 v01.05 dmi.board.name: 304Ah dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786H1v01.05:bd06/09/2010:br1.5:svnHewlett-Packard:pnHPCompaq8100EliteSFFPC:pvr:rvnHewlett-Packard:rn304Ah:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 8100 Elite SFF PC dmi.product.sku: LE093PA#ABG dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1919955/+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 1914458] Re: Crash after stylus touch on wacom tablet
*** This bug is a duplicate of bug 1920632 *** https://bugs.launchpad.net/bugs/1920632 This has been marked as a duplicate of bug #1920632 (which it may well be) - however I am experiencing these crashes on kernel 5.4.0-70-generic (i.e. the GA kernel for 20.04.2) - is it possible to get the fix from bug #1920632 backported into that kernel to fix this issue for everyone? Apologies if I've misunderstood the process. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1914458 Title: Crash after stylus touch on wacom tablet Status in xf86-input-wacom package in Ubuntu: New Bug description: A bug in the input-wacom module was causing intermittent crashes when the stylus first touched the tablet. This is documented here: https://github.com/linuxwacom/input-wacom/issues/234 Apparently input-wacom has been released with a fix, I was told that I need to raise a bug in launchpad to get this fix propagated into an update for 20.04 (apologies if that is not the case). According to the above link, the fix has been released and accepted into the main upstream kernels (I don't know which versions exactly) - I'm unclear as to what the process is for this to go into an LTS update.. after much searching all I've read is that one should raise a bug in launchpad(!) Many thanks.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1914458/+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 1611730] Re: libreoffice 5.2.0.4 ppa
** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- 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/1611730 Title: libreoffice 5.2.0.4 ppa Status in libreoffice package in Ubuntu: Fix Released Bug description: Running Ubuntu 14.04.4. Updating Libreoffice via http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ trusty/main. My Libreoffice installation upgraded to 5.2.0.4 yesterday, and now libreoffice-gtk no longer works with it. When I try to reinstall libreoffice-gtk, the following error report is given: The following packages have unmet dependencies. libreoffice-gtk : Depends: libreoffice-core (= 1:4.2.8-0ubuntu4) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Aptitude reports: The following packages have unmet dependencies: libreoffice-core : Breaks: libreoffice-gtk (< 1:5.2.0~rc4-0ubuntu1~trusty1) but 1:4.2.8-0ubuntu4 is to be installed. libreoffice-gtk : Depends: libreoffice-core (= 1:4.2.8-0ubuntu4) but 1:5.2.0~rc4-0ubuntu1~trusty1 is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1611730/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
apt-get -y install alsa-tools cat > /lib/firmware/hda-jack-retask.fw << 'EOFFW' [codec] 0x10ec0235 0x17aa3826 0 [pincfg] 0x17 0x90170111 [verb] 0x01 0x0716 0x04 0x01 0x0717 0x04 0x01 0x0715 0x04 EOFFW cat > /etc/modprobe.d/hda-jack-retask.conf << 'EOFCONF' options snd-hda-intel power_save=0 power_save_controller=N patch=hda-jack-retask.fw EOFCONF 29.03.2021 19:49:49 Diogo André Cardoso Pereira <1553...@bugs.launchpad.net>: > How do you guys modify the files ? Im new to linux so i dont have no idea > what to do, i just install sudo apt get install hdajackretask,so what to do > next? > Also i dont find the files mentioned anywhere, im probably making this all > wrong XD > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1553685 > > Title: > Lenovo Y700-17ISK subwoofer doesn't work > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M > 4GB) > Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, > kernel 4.4.0-10-generic, nvidia 361.28) > > Problem: Notebook subwoofer doesn't work. > > Judging from alsa-info.sh output, there is no pin declared for the bass > output by BIOS. > Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-10-generic 4.4.0-10.25 > ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 > Uname: Linux 4.4.0-10-generic x86_64 > ApportVersion: 2.20-0ubuntu3 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: aljosa 1776 F pulseaudio > CurrentDesktop: Unity > Date: Sun Mar 6 11:02:21 2016 > HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 > InstallationDate: Installed on 2016-03-05 (0 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) > MachineType: LENOVO 80Q0 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed > root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 > RelatedPackageVersions: > linux-restricted-modules-4.4.0-10-generic N/A > linux-backports-modules-4.4.0-10-generic N/A > linux-firmware 1.156 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/31/2016 > dmi.bios.vendor: LENOVO > dmi.bios.version: CDCN30WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: Allsparks 7A > dmi.board.vendor: LENOVO > dmi.board.version: NO DPK > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo ideapad Y700-17ISK > dmi.modalias: > dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: > dmi.product.name: 80Q0 > dmi.product.version: Lenovo ideapad Y700-17ISK > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware
[Desktop-packages] [Bug 1518411] Re: "Maximum number of clients reached", new in Ubuntu 15.10
** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Released ** Changed in: compiz (Ubuntu) Status: Triaged => Fix Released ** Changed in: compiz Status: Confirmed => Fix Released -- 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/1518411 Title: "Maximum number of clients reached", new in Ubuntu 15.10 Status in Compiz: Fix Released Status in compiz package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: In my newly upgraded (from 15.04) Ubuntu 15.10 system, after I've been logged in for a while I can no longer open new windows and instead get a "Maximum number of clients reached" error. This did not happen in 15.04. I ran "lsof" on the X server and did not see an excessive number of open file descriptors. I ran it again on a newly restarted X server and the number of open file descriptors looked about the same. I also ran "xlsclients" when the X server was reporting "Maximum number of clients reached" and the list of clients looked correct and reasonable (and there were less than 30 of them). I am happy to collect any additional logs or debugging information to help track this down. I don't know where to look further. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 20 13:00:09 2015 DistUpgraded: 2015-11-17 11:59:09,835 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.4, 3.19.0-33-generic, x86_64: installed virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:7410] MachineType: System76, Inc. Galago UltraPro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=821f94aa-97e2-4384-8494-9f510a75877b ro i915.disable_power_well=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-11-17 (3 days ago) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Nov 20 12:51:23 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1518411/+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 1921583] Re: Can't run System Monitor in Ubuntu Unity 21.04
So far it only affects Ubuntu Unity 21.04. Main Ubuntu 21.04 doesn't seem to have this issue and System monitor opens without any problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1921583 Title: Can't run System Monitor in Ubuntu Unity 21.04 Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: I can't run System Monitor in Ubuntu Unity 21.04. I reported a bug on Ubuntu Unity's tracker, but I've been told to report it here. https://gitlab.com/ubuntu-unity/ubuntu-unity- issues/-/issues/82#note_539356065 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-system-monitor 40.0-1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 27 15:32:16 2021 InstallationDate: Installed on 2021-03-27 (0 days ago) InstallationMedia: Ubuntu Unity 21.04 SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1921583/+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 1915887] Re: systemd spams the syslog about lack of native systemd unit file
Fixed in Hirsute in 247.3-2ubuntu1 . ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service
[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
How do you guys modify the files ? Im new to linux so i dont have no idea what to do, i just install sudo apt get install hdajackretask,so what to do next? Also i dont find the files mentioned anywhere, im probably making this all wrong XD -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1921583] Re: Can't run System Monitor in Ubuntu Unity 21.04
This is the error i get when trying to run the system monitor from a terminal: ubuntu@ubuntu:~$ gnome-system-monitor (gnome-system-monitor:5412): Gtk-WARNING **: 17:49:22.082: Theme parsing error: gtk.css:6083:16: Junk at end of value for color (gnome-system-monitor:5412): Gtk-CRITICAL **: 17:49:22.765: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed (gnome-system-monitor:5412): Handy-ERROR **: 17:49:22.941: gtk_window_set_titlebar() is not supported for HdyWindow Trace/breakpoint trap (core dumped) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1921583 Title: Can't run System Monitor in Ubuntu Unity 21.04 Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: I can't run System Monitor in Ubuntu Unity 21.04. I reported a bug on Ubuntu Unity's tracker, but I've been told to report it here. https://gitlab.com/ubuntu-unity/ubuntu-unity- issues/-/issues/82#note_539356065 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-system-monitor 40.0-1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 27 15:32:16 2021 InstallationDate: Installed on 2021-03-27 (0 days ago) InstallationMedia: Ubuntu Unity 21.04 SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1921583/+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 1921583] Re: Can't run System Monitor in Ubuntu Unity 21.04
Thank you for your bug report. The issue seems to be a theme one though, which one do you use? Is it provided in Ubuntu, in which case it should be reassigned to that component ** Changed in: gnome-system-monitor (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1921583 Title: Can't run System Monitor in Ubuntu Unity 21.04 Status in gnome-system-monitor package in Ubuntu: Incomplete Bug description: I can't run System Monitor in Ubuntu Unity 21.04. I reported a bug on Ubuntu Unity's tracker, but I've been told to report it here. https://gitlab.com/ubuntu-unity/ubuntu-unity- issues/-/issues/82#note_539356065 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-system-monitor 40.0-1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 27 15:32:16 2021 InstallationDate: Installed on 2021-03-27 (0 days ago) InstallationMedia: Ubuntu Unity 21.04 SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1921583/+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 1921583] Re: Can't run System Monitor in Ubuntu Unity 21.04
It doesn't say "Theme parsing error" when the theme is Adwaita or Ambiance. But still, it does not run. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1921583 Title: Can't run System Monitor in Ubuntu Unity 21.04 Status in gnome-system-monitor package in Ubuntu: Incomplete Bug description: I can't run System Monitor in Ubuntu Unity 21.04. I reported a bug on Ubuntu Unity's tracker, but I've been told to report it here. https://gitlab.com/ubuntu-unity/ubuntu-unity- issues/-/issues/82#note_539356065 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-system-monitor 40.0-1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 27 15:32:16 2021 InstallationDate: Installed on 2021-03-27 (0 days ago) InstallationMedia: Ubuntu Unity 21.04 SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1921583/+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 1921583] Re: Can't run System Monitor in Ubuntu Unity 21.04
Could you try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1921583 Title: Can't run System Monitor in Ubuntu Unity 21.04 Status in gnome-system-monitor package in Ubuntu: Incomplete Bug description: I can't run System Monitor in Ubuntu Unity 21.04. I reported a bug on Ubuntu Unity's tracker, but I've been told to report it here. https://gitlab.com/ubuntu-unity/ubuntu-unity- issues/-/issues/82#note_539356065 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-system-monitor 40.0-1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 27 15:32:16 2021 InstallationDate: Installed on 2021-03-27 (0 days ago) InstallationMedia: Ubuntu Unity 21.04 SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1921583/+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 1921781] [NEW] Build-depends on qt5-default which is obsolete and dropped in hirsute
Public bug reported: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. ** Affects: indicator-sound (Ubuntu) Importance: High Status: New ** Affects: libqofono (Ubuntu) Importance: High Status: New ** Affects: poppler-qml-plugin (Ubuntu) Importance: High Status: New ** Affects: qtpowerd (Ubuntu) Importance: High Status: New ** Affects: qtubuntu-cameraplugin-fake (Ubuntu) Importance: High Status: New ** Affects: signon-keyring-extension (Ubuntu) Importance: High Status: New ** Affects: signon-plugin-sasl (Ubuntu) Importance: High Status: New ** Affects: signon-ui (Ubuntu) Importance: High Status: New ** Affects: unity-api (Ubuntu) Importance: High Status: New ** Also affects: libqofono (Ubuntu) Importance: Undecided Status: New ** Also affects: poppler-qml-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: qtpowerd (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu-cameraplugin-fake (Ubuntu) Importance: Undecided Status: New ** Also affects: signon-keyring-extension (Ubuntu) Importance: Undecided Status: New ** Also affects: signon-plugin-sasl (Ubuntu) Importance: Undecided Status: New ** Also affects: signon-ui (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-api (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => High ** Changed in: libqofono (Ubuntu) Importance: Undecided => High ** Changed in: qtpowerd (Ubuntu) Importance: Undecided => High ** Changed in: poppler-qml-plugin (Ubuntu) Importance: Undecided => High ** Changed in: qtubuntu-cameraplugin-fake (Ubuntu) Importance: Undecided => High ** Changed in: signon-keyring-extension (Ubuntu) Importance: Undecided => High ** Changed in: signon-plugin-sasl (Ubuntu) Importance: Undecided => High ** Changed in: signon-ui (Ubuntu) Importance: Undecided => High ** Changed in: unity-api (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-keyring-extension in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: New Status in poppler-qml-plugin package in Ubuntu: New Status in qtpowerd package in Ubuntu: New Status in qtubuntu-cameraplugin-fake package in Ubuntu: New Status in signon-keyring-extension package in Ubuntu: New Status in signon-plugin-sasl package in Ubuntu: New Status in signon-ui package in Ubuntu: New Status in unity-api package in Ubuntu: New Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
** Changed in: network-manager (Ubuntu Precise) Status: Invalid => Fix Released ** Changed in: network-manager (Ubuntu) Status: Invalid => Fix Released ** Changed in: dnsmasq (Ubuntu Precise) Status: Triaged => Fix Released ** Changed in: dnsmasq (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in dnsmasq source package in Precise: Fix Released Status in network-manager source package in Precise: Fix Released Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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
