[Desktop-packages] [Bug 1721401] Re: eog fails to open png: Failed to register: Timeout was reached
I have this problem as well, and it just started tonight (2021-05-25) on my xubuntu 20.04 system. I have another xubuntu 20.04 machine on which the problem does not occur. So, this may be transient, or mostly unrelated to eog. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1721401 Title: eog fails to open png: Failed to register: Timeout was reached Status in eog package in Ubuntu: Confirmed Bug description: eog fails to open PNG file. After about 25 seconds, it gives up and says: Failed to register: Timeout was reached You can find the relevant image at: https://www.dropbox.com/s/psrm3wj1n480ocx/FIDUCEO_FCDR_L1C_HIRS2_noaa14_2101144729_2101162929_easy_v0.7_fv0.4.png?dl=0 Ubuntu 16.04.2 LTS, GNOME Image Viewer 3.18.2. I expect it to display the image. Instead it fails with the above message. Image Magicks "display" utility shows the image fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1721401/+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 1921963] Re: SRU 3.36.9
It looks like the answer is because yaru-theme-gnome-shell implements some of what upstream implements in gnome-shell (data/theme/gnome-shell- sass/widgets/_calendar.scss). An upstream fix in 'gnome-shell' sometimes needs to be downstreamed to Ubuntu in the 'yaru-theme' package. -- 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/1921963 Title: SRU 3.36.9 Status in gnome-shell package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in yaru-theme source package in Focal: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Login a11y changed and so the usage of icons for notifications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
Hi Daniel,
SRU template filled, thanks!
** Description changed:
[Impact]
+ In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
+
+ In this case, the rear Mic will present on input devices of "Sound
+ Settings" even if attaching nothing to rear mic jack.
[Fix]
+ For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
+ ```
+ control.18 {
+ iface CARD
+ name 'Rear Mic Jack'
+ value true
+ comment {
+ access read
+ type BOOLEAN
+ count 1
+ }
+ }
+ ```
+ After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
+
+ For pulseaudio, if there is no any audio devices attached, then
+ attaching an input device on rear mic jack. The port will not be
+ selected automatically because the profiles is off. It needs patch
+ pulseaudio to check off profiles (for dual codec case).
[Test]
+ After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
+ This change only apply the bonus on below cases:
+ ```
+ if ((has_input_port && found_available_input_port && !has_output_port) ||
+ (has_output_port && found_available_output_port && !has_input_port) ||
+ (has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
+ ```
+ and these cases have been tested.
+ If there are some complex codec design then it might cause problem but so far
we didn't see that.
** Changed in: oem-priority
Status: In Progress => Triaged
--
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/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Triaged
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Incomplete
Status in alsa-ucm-conf source package in Focal:
New
Status in pulseaudio source package in Focal:
New
Status in alsa-ucm-conf source package in Groovy:
New
Status in pulseaudio source package in Groovy:
New
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
New
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 952922] Re: grab handles on certain windows do not work
[Expired for metacity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: metacity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/952922 Title: grab handles on certain windows do not work Status in metacity package in Ubuntu: Expired Bug description: When I open evince or nautilus, it is impossible to move up and down on the screen by grabbing the "handle" on the side. I have just tried with evince and nautilus, am assuming the problem is universal and caused by metacity. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-18.26-lowlatency-pae 3.2.9 Uname: Linux 3.2.0-18-lowlatency-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 12 07:50:55 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-03 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/952922/+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 597227] Re: Should Metacity really show up as a program in Software Center instead of a system package?
[Expired for software-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/597227 Title: Should Metacity really show up as a program in Software Center instead of a system package? Status in metacity package in Ubuntu: Invalid Status in software-center package in Ubuntu: Expired Bug description: software-center 2.0.5, Ubuntu 10.04 software-center 4.0.4, Ubuntu 11.04 1. Navigate to "Installed Software". 2. Scroll down to M. What happens: Metacity shows up by default. Any user can be looking through the installed software and think, "Metacity? GTK window manager? What's that? I don't need that!" and remove it, which I'm sure would cause some serious problems if that user decided to turn off visual effects or never had them on in the first place. Also, Metacity seems more like a system package than a program. What should happen: Metacity should be hidden by default, not appearing unless you choose "Show technical items". This can be implemented by removing Metacity's desktop file. [This bug report also previously mentioned capitalization of "Get Software" and "Installed Software", which is mostly obviated by the 5.0 redesign.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/597227/+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 1448429] Re: GNOME Flashback (Metacity): Compose Key not working as expected
[Expired for metacity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: metacity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1448429 Title: GNOME Flashback (Metacity): Compose Key not working as expected Status in metacity package in Ubuntu: Expired Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 15.04 Release: 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center xorg: Installed: 1:7.7+7ubuntu4 Candidate: 1:7.7+7ubuntu4 3) What you expected to happen The key combination AltGr + [ a produces ä (latin small letter a with diaresis) Works in GNOME Flashback (Compiz). 4) What happened instead The key combination AltGr + [ a produces ¨a Does not work in GNOME Flashback (Metacity). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Sat Apr 25 13:05:09 2015 DistUpgraded: 2015-04-23 21:17:34,692 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-10-28 (543 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4291NA7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-04-23 (1 days ago) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291NA7 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.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn4291NA7:pvrThinkPadX220:rvnLENOVO:rn4291NA7:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291NA7 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Apr 25 13:04:39 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4204 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1448429/+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 1459128] Re: metacity no longer honors keybindings without modmask?
[Expired for metacity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: metacity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1459128 Title: metacity no longer honors keybindings without modmask? Status in metacity package in Ubuntu: Expired Bug description: I'm extremely attached to the following two keybindings: $ dconf read /org/gnome/desktop/wm/keybindings/raise ['F1'] $ dconf read /org/gnome/desktop/wm/keybindings/lower ['F2'] But they stopped working for me in metacity 2.34.13. (That is, I hit F1/F2 expecting the window under the mouse cursor to be raised/lowered respectively, and it doesn't happen.) When I run `METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace` and install my keybindings: $ dconf write /org/gnome/desktop/wm/keybindings/raise "['F1']" $ dconf write /org/gnome/desktop/wm/keybindings/lower "['F2']" I notice the following appears in the log file: KEYBINDINGS: Will not grab keybinding F1 without modmask. KEYBINDINGS: Will not grab keybinding F2 without modmask. If I then try installing similar bindings with a modmask: $ dconf write /org/gnome/desktop/wm/keybindings/raise "['F1']" $ dconf write /org/gnome/desktop/wm/keybindings/lower "['F2']" no such log message occurs, and the modified keybindings work! When I searched for that log message on the web, it led to this recent commit and bug reference: https://mail.gnome.org/archives/commits-list/2015-April/msg01612.html https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1440570 Note however that this bug seems to refer to VNC, which I am not using. So is it the case that F1/F2, unmodified, can no longer be keyboard shortcuts? This would make me very sad, since I've used them several thousand times per day for the last 25 years or so, and I'm not sure I can rewire my fingers at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1459128/+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 1780468] Re: Blurry titlebar font when window is not maximized
[Expired for metacity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: metacity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized Status in metacity package in Ubuntu: Expired Bug description: What happens I've configured Compiz window manager to use gtk-window-decorator so that it may apply my Metacity theme for the titlebars. With this decorator, I've noticed that Compiz renders slightly blurry titlebar fonts when a window is not maximized. Once the window is maximized, sharp fonts are rendered. When a window is not maximized, the font seems to lack sub-pixel hinting or anti-aliasing, hence the slightly blurry appearance. I zoomed in on the font when the window was maximized and observed bluish lines around the characters. When a window was not maximized, the zoomed-in characters didn't have the bluish lines. I've tested and seen that the Marco window manager and the Emerald decorator (used with Compiz) both render sharp titlebar fonts regardless of whether a window is maximized or not. The image in the below link shows the slight difference in font rendering when Compiz is used with gtk-window-decorator. Firefox's window was maximized, with sharp text, while VLC's window was not maximized, with slightly blurry text. https://i.stack.imgur.com/5BalZ.png Upon switching to Marco window manager, both texts are sharp. https://i.stack.imgur.com/9Gzli.png When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue lines around the maximized Firefox window titlebar text are visible (it looks like sub-pixel rendering to me). The blue lines are completely lacking in the un-maximized VLC window titlebar text. https://i.stack.imgur.com/XDSAU.png What I expect to happen --- The titlebar font rendering should be sharp for both maximized and un-maximized windows. The cause (clip_to_rounded_corners) --- Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the libmetacity library. The clip_to_rounded_corners() function in "meta-theme-metacity.c" is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering. I rebuilt the libmetacity library with the clip_to_rounded_corners() call commented out and achieved sharp fonts for un-maximized windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: metacity 1:3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jul 6 19:52:03 2018 InstallationDate: Installed on 2018-05-06 (61 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+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 1922729] Re: SRU the current 3.36.2 stable update
Hello Sebastien, or anyone else affected, Accepted yelp into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/yelp/3.36.2-0ubuntu1 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: yelp (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1922729 Title: SRU the current 3.36.2 stable update Status in yelp package in Ubuntu: Fix Released Status in yelp source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some translation updates and bugfixes https://gitlab.gnome.org/GNOME/yelp/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that browsing documentation from different GNOME softwares still work correctly, including the desktop user guide * Regression potential The update has changes around the handling of local document, make sure to test those and try editing to see that the browser is handling it correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1922729/+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 1920986] Re: i have a high cpu use whene i open firefox
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1920986 Title: i have a high cpu use whene i open firefox Status in firefox package in Ubuntu: Expired Bug description: hello i have a high cpu use whene i open firefox in the terminal i type top and have 130 % webcon+ and 135 % firefox thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 23 19:40:52 2021 InstallationDate: Installed on 2021-03-22 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1920986/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Also affects: pulseaudio (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: New Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1921963] Re: SRU 3.36.9
Why is there a yaru-theme task on this bug? The upload in the unapproved queue has a changelog entry claiming to fix a specific bug, and doesn't seem associated with the 3.36.9 stable update at all? The upload itself looks fine, but please associate it with a bug that mentions the actual change it makes - that way the bug can point to changes in the calendar layout, and mention that the calendar widget should be checked for regressions. -- 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/1921963 Title: SRU 3.36.9 Status in gnome-shell package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in yaru-theme source package in Focal: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Login a11y changed and so the usage of icons for notifications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+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 1921963] Proposed package upload rejected
An upload of yaru-theme to focal-proposed has been rejected from the upload queue for the following reason: "Please re-upload pointing to a bug that is not the gnome-shell 3.36.9 tracking bug.". -- 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/1921963 Title: SRU 3.36.9 Status in gnome-shell package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in yaru-theme source package in Focal: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Login a11y changed and so the usage of icons for notifications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+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 1869086] Re: Firmware upgrade always notifies to reboot the device even on immediate failure
** Tags added: fwupd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869086 Title: Firmware upgrade always notifies to reboot the device even on immediate failure Status in snap-store-desktop: Triaged Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Focal: Triaged Bug description: If the firmware update request fails because of a network error or because the AC power is not plugged, or any other problem, gnome- software shows an error in an in-app notification, while sends a resident notification to gnome-shell that requests the user to restart the system, even if this is not really required. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+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 1869086] Re: Firmware upgrade always notifies to reboot the device even on immediate failure
I can't reproduce this. fwupd deb 1.3.11-1~focal1 snap-store, Version: 3.38.0-59-g494f078, Rev: 518 (latest/stable) Attached is the UI when AC is not plugged. ** Attachment added: "fwupd-test-no-ac-passed.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+attachment/5500346/+files/fwupd-test-no-ac-passed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869086 Title: Firmware upgrade always notifies to reboot the device even on immediate failure Status in snap-store-desktop: Triaged Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Focal: Triaged Bug description: If the firmware update request fails because of a network error or because the AC power is not plugged, or any other problem, gnome- software shows an error in an in-app notification, while sends a resident notification to gnome-shell that requests the user to restart the system, even if this is not really required. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929572] Re: Xorg freeze
Thanks for the bug report. Next time a freeze happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Open a Terminal and run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Check the system for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => xorg-server (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/1929572 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: A screen freezing had occurred when I was watching video whose location is on my connected phone(Redmi9 with global miui12). While its appearing, there's completely no response to every input, also, there's no mouse on the screen. That's what I can describe. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 25 22:29:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi Device [1d72:2003] Subsystem: Xiaomi GP107M [GeForce MX350] [1d72:2003] InstallationDate: Installed on 2021-05-03 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: TIMI RedmiBook 16 ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=18c673bc-d09d-4a44-814f-b4f048aa888a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 1.8 dmi.bios.vendor: TIMI dmi.bios.version: RMAIC6B0P0808 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: TM2003 dmi.board.vendor: TIMI dmi.board.version: V34F2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnTIMI:bvrRMAIC6B0P0808:bd12/02/2020:br1.8:efr1.8:svnTIMI:pnRedmiBook16:pvr:rvnTIMI:rnTM2003:rvrV34F2:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 16 dmi.product.sku: TM2003-28977 dmi.sys.vendor: TIMI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1929572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929557] Re: Ubuntu 21.04 No notification when battery under 10%
xgamma and xrandr control the 'Xorg' process. There is no Xorg process in a Wayland session so xgamma and xrandr will not work. That's not a bug. If you need them then you should log into 'Ubuntu on Xorg' instead. ** Summary changed: - Ubuntu 21.04 No alarm when Battery under 10% + Ubuntu 21.04 No notification when battery under 10% -- 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/1929557 Title: Ubuntu 21.04 No notification when battery under 10% Status in gnome-shell package in Ubuntu: New Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929572] [NEW] Xorg freeze
You have been subscribed to a public bug: A screen freezing had occurred when I was watching video whose location is on my connected phone(Redmi9 with global miui12). While its appearing, there's completely no response to every input, also, there's no mouse on the screen. That's what I can describe. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 25 22:29:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi Device [1d72:2003] Subsystem: Xiaomi GP107M [GeForce MX350] [1d72:2003] InstallationDate: Installed on 2021-05-03 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: TIMI RedmiBook 16 ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=18c673bc-d09d-4a44-814f-b4f048aa888a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 1.8 dmi.bios.vendor: TIMI dmi.bios.version: RMAIC6B0P0808 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: TM2003 dmi.board.vendor: TIMI dmi.board.version: V34F2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnTIMI:bvrRMAIC6B0P0808:bd12/02/2020:br1.8:efr1.8:svnTIMI:pnRedmiBook16:pvr:rvnTIMI:rnTM2003:rvrV34F2:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 16 dmi.product.sku: TM2003-28977 dmi.sys.vendor: TIMI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal freeze ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1929572 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server 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 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
For Ubuntu 20.04, the most common cause of syslog floods is bug 1880405 so we should probably wait for that fix to be released in gnome-shell 3.36.9. While waiting, everyone please check your Extensions app and ensure there are only the three built-in extensions listed. We need to exclude extensions as a first step because they cause so many bugs. -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+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 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
Hi everyone, I have the same problem. The solution to avoid the log flooding the entire disk is to place this line in the root cron (sudo crontab -e): */1 * * * * [[ $(tail /mnt/data/system/var/log/syslog | grep -vi "cron" | grep "The offending callback was SourceFunc().") ]] && kill -HUP $(pidof gnome-shell) This greps the last lines of the log every minute and triggers a restart of gnome-shell if the offending callback is found. None of the current applications are killed (except gnome-shell) which is convenient. If you are limited in space, I would recommend to run the command every 30s or less. Source of this is available here: https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/1868#note_1050922 Hope this helps. EDIT: By the way, here are information related to my system: - Ubuntu 20.04.2 - 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux - GNOME Shell 3.36.7 -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+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 1925730] Re: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation
*** This bug is a duplicate of bug 1921632 *** https://bugs.launchpad.net/bugs/1921632 We already handled it in another bug: https://bugs.launchpad.net/bugs/1921632 ** This bug has been marked a duplicate of bug 1921632 build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later -- 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/1925730 Title: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation Status in alsa-driver package in Ubuntu: New Bug description: New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu 21.04 sound does not work at all. System settings only show one audio output - "Dummy output". Audio input does not have even that, just an empty drop-down list. Issue can be fixed if we load a custom sound driver as described here: https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio- working-on-linux/ That poses a security risk however and according to the author of the article is not necessary since mainline Kernel release 5.11 now has required device headers included. ... lspci output: user@MYPC:~$ lspci -v | grep -i -A 10 audio 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS Subsystem: Dell Comet Lake PCH cAVS Flags: bus master, fast devsel, latency 64, IRQ 229, IOMMU group 16 Memory at 609b218000 (64-bit, non-prefetchable) [size=16K] Memory at 609b10 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci -- 01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) Subsystem: Dell TU106 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 1 Memory at 7300 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Looked around for soundwire drivers, found this: user@MYPC:~$ lsmod | grep soundwire soundwire_intel40960 2 snd_sof_intel_hda_common,snd_intel_dspcfg soundwire_generic_allocation16384 1 soundwire_intel soundwire_cadence 32768 1 soundwire_intel soundwire_bus 77824 7 regmap_sdw,soundwire_intel,snd_soc_rt715,soundwire_generic_allocation,soundwire_cadence,snd_soc_rt711,snd_soc_rt1308_sdw snd_soc_core 294912 8 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_rt715,snd_soc_hdac_hda,snd_soc_rt711,snd_soc_dmic,snd_soc_rt1308_sdw snd_pcm 118784 14 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_ipc,snd_soc_rt715,snd_compress,snd_soc_core,snd_soc_rt711,snd_soc_rt1308_sdw,snd_hda_core,snd_pcm_dmaengine Maybe using the soundwire_intel driver would fix the problem? Need to keep digging. Will post an update if I have any progress. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 00:18:15 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) 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_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: TU106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0YK6XT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0YK6XT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925730/+subscriptions -- Mailing
[Desktop-packages] [Bug 1929557] Re: Ubuntu 21.04 No alarm when Battery under 10%
Thanks for the additional info. Hopefully some GNOME developer will look at it. On 2021-05-25 18:27, ROCHE wrote: > Another point: ... The "xgamma" thing sounds as something completely unrelated to the power indicator. If it is, you'd better submit a separate bug report about that. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1929557 Title: Ubuntu 21.04 No alarm when Battery under 10% Status in gnome-shell package in Ubuntu: New Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+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 1925730] Re: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation
Hi, For about at least two months now, I have found the reason, and also how to solve it. And that is no other than compiling the kernel by yourself, while applying a change in the configuration. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976791 These settings need to be enabled before build (the first one makes the second one visible): CONFIG_SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES=y CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m Here follows is how to do it whith the NCurses interface that you get with the kernel source for Ubuntu: Device Drivers ---> Sound card support ---> Advanced Linux Sound Architecture ---> ALSA for SoC audio support ---> -*- Intel Machine drivers ---> [*] Use more user friendly long card names SoundWire generic machine driver For now I won't go into more detail, but this is wat needs to be done and what Canonical/Ubuntu should have done by themselves! Ubuntu is the only distro which I know that has this setting still disabled. SoundWire works out of the box with Arch Linux, with Fedora, with Debian, but not with Ubuntu (why doing these things different from Debian?). So please Canonical/Ubuntu correct it! Thanks! ** Bug watch added: Debian Bug tracker #976791 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976791 -- 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/1925730 Title: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation Status in alsa-driver package in Ubuntu: New Bug description: New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu 21.04 sound does not work at all. System settings only show one audio output - "Dummy output". Audio input does not have even that, just an empty drop-down list. Issue can be fixed if we load a custom sound driver as described here: https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio- working-on-linux/ That poses a security risk however and according to the author of the article is not necessary since mainline Kernel release 5.11 now has required device headers included. ... lspci output: user@MYPC:~$ lspci -v | grep -i -A 10 audio 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS Subsystem: Dell Comet Lake PCH cAVS Flags: bus master, fast devsel, latency 64, IRQ 229, IOMMU group 16 Memory at 609b218000 (64-bit, non-prefetchable) [size=16K] Memory at 609b10 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci -- 01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) Subsystem: Dell TU106 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 1 Memory at 7300 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Looked around for soundwire drivers, found this: user@MYPC:~$ lsmod | grep soundwire soundwire_intel40960 2 snd_sof_intel_hda_common,snd_intel_dspcfg soundwire_generic_allocation16384 1 soundwire_intel soundwire_cadence 32768 1 soundwire_intel soundwire_bus 77824 7 regmap_sdw,soundwire_intel,snd_soc_rt715,soundwire_generic_allocation,soundwire_cadence,snd_soc_rt711,snd_soc_rt1308_sdw snd_soc_core 294912 8 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_rt715,snd_soc_hdac_hda,snd_soc_rt711,snd_soc_dmic,snd_soc_rt1308_sdw snd_pcm 118784 14 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_ipc,snd_soc_rt715,snd_compress,snd_soc_core,snd_soc_rt711,snd_soc_rt1308_sdw,snd_hda_core,snd_pcm_dmaengine Maybe using the soundwire_intel driver would fix the problem? Need to keep digging. Will post an update if I have any progress. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 00:18:15 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
** Package changed: fuse (Debian) => fuse -- 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in FUSE: Fix Released Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Fix Released Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/fuse/+bug/254171/+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 1927970] Re: Maximised gnome-terminal not returning to normal size
Looks like there is a matching upstream https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/359 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #359 https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/359 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1927970 Title: Maximised gnome-terminal not returning to normal size Status in gnome-terminal package in Ubuntu: New Bug description: The default terminal size is 80x24 If the terminal is maximised then returned to normal by double clicking on the title bar the terminal ends up being 79x23 the first time, 78x22 the second time and so on. it can be reset by clicking on the burger menu -> advanced -> 80x24 I expect it to return to the same size it started at (80x24) lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 14:37:05 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-09-23 (228 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1927970/+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 1919143] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1919143 Title: SRU mutter to 3.36.9 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been relevant changes on DND, monitors handling and wayland windows configurations --- This is a request to update mutter to version >= 3.36.8 to fix various issues that have been fixed upstream. See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700#note_1058654 for the original mutter issue report that will be fixed by 3.36.8. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: libmutter-6-0 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 10:40:58 2021SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1919143/+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 1905825] Re: [SRU] Disable CRTCs when system becomes headless
This bug was fixed in the package mutter - 3.36.9-0ubuntu0.20.04.1 --- mutter (3.36.9-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1919143) - Do not ping unmanaging windows - Improve freezes when switching workspace - Fix drag cancel animation when using geometry scaling - Fix stuck icon in DND operation between X11 and wayland - Fix restoring focus to windows using globally active input - Fix _NET_WM_FRAME_DRAWN timestamps - Fix unwanted position changes on window resize - Fix device configuration not being picked up on X11 - Fix size hints with CSD - Disable CRTCs if there is no monitor (LP: #1905825) - Fixed crashes - Plugged memory leaks -- Marco Trevisan (Treviño) Wed, 31 Mar 2021 02:15:27 +0200 ** Changed in: mutter (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905825 Title: [SRU] Disable CRTCs when system becomes headless Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Committed Status in mutter source package in Hirsute: Fix Released Bug description: [Impact] On new Intel SoCs, after all connectors are unplugged and the system becomes headless, it cannot detect monitor hotplug event from type-c port. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561 Based on "drm/i915 Intel GFX Driver, Hotplug" [1]: "Finally, the userspace is responsible for triggering a modeset upon receiving the hotplug uevent, disabling or enabling the crtc as needed." [Test] Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor back, monitor is blank. With the fix applied, the system can detect monitor again. [Where problems could occur] This fix disables CRTCs when there's no monitor, if driver has trouble dealing with it, we may see something break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905825/+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 1905825] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905825 Title: [SRU] Disable CRTCs when system becomes headless Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Committed Status in mutter source package in Hirsute: Fix Released Bug description: [Impact] On new Intel SoCs, after all connectors are unplugged and the system becomes headless, it cannot detect monitor hotplug event from type-c port. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561 Based on "drm/i915 Intel GFX Driver, Hotplug" [1]: "Finally, the userspace is responsible for triggering a modeset upon receiving the hotplug uevent, disabling or enabling the crtc as needed." [Test] Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor back, monitor is blank. With the fix applied, the system can detect monitor again. [Where problems could occur] This fix disables CRTCs when there's no monitor, if driver has trouble dealing with it, we may see something break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905825/+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 1919143] Re: SRU mutter to 3.36.9
This bug was fixed in the package mutter - 3.36.9-0ubuntu0.20.04.1 --- mutter (3.36.9-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1919143) - Do not ping unmanaging windows - Improve freezes when switching workspace - Fix drag cancel animation when using geometry scaling - Fix stuck icon in DND operation between X11 and wayland - Fix restoring focus to windows using globally active input - Fix _NET_WM_FRAME_DRAWN timestamps - Fix unwanted position changes on window resize - Fix device configuration not being picked up on X11 - Fix size hints with CSD - Disable CRTCs if there is no monitor (LP: #1905825) - Fixed crashes - Plugged memory leaks -- Marco Trevisan (Treviño) Wed, 31 Mar 2021 02:15:27 +0200 ** Changed in: mutter (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1919143 Title: SRU mutter to 3.36.9 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been relevant changes on DND, monitors handling and wayland windows configurations --- This is a request to update mutter to version >= 3.36.8 to fix various issues that have been fixed upstream. See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700#note_1058654 for the original mutter issue report that will be fixed by 3.36.8. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: libmutter-6-0 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 10:40:58 2021SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1919143/+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 254171] Re: Nautilus can't properly unmount FUSE file systems
** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released -- 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Fix Released Status in fuse package in Debian: Fix Released Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+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 1929598] Re: Firefox rfuses to start YouTube display
** Attachment added: "Screenshot from 2021-05-25 14-24-40.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1929598/+attachment/5500303/+files/Screenshot%20from%202021-05-25%2014-24-40.png -- 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/1929598 Title: Firefox rfuses to start YouTube display Status in firefox package in Ubuntu: New Bug description: Firefox starts to build the buffer, but is does not display anything. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 88.0.1+build1-0ubuntu0.21.04.2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bertadmin 4040 F pulseaudio /dev/snd/pcmC1D0p: bertadmin 4040 F...m pulseaudio /dev/snd/controlC0: bertadmin 4040 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue May 25 14:25:12 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 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2019-11-30 (542 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev enp7s0 proto dhcp metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 192.168.1.0/24 dev enp7s0 proto kernel scope link src 192.168.1.106 metric 100 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=88.0.1/20210504152106 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-03-24 (61 days ago) dmi.bios.date: 07/18/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.10 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.10:bd07/18/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1929598/+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 1929598] [NEW] Firefox rfuses to start YouTube display
Public bug reported: Firefox starts to build the buffer, but is does not display anything. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 88.0.1+build1-0ubuntu0.21.04.2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bertadmin 4040 F pulseaudio /dev/snd/pcmC1D0p: bertadmin 4040 F...m pulseaudio /dev/snd/controlC0: bertadmin 4040 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue May 25 14:25:12 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 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2019-11-30 (542 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev enp7s0 proto dhcp metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 192.168.1.0/24 dev enp7s0 proto kernel scope link src 192.168.1.106 metric 100 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=88.0.1/20210504152106 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-03-24 (61 days ago) dmi.bios.date: 07/18/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.10 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.10:bd07/18/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1929598 Title: Firefox rfuses to start YouTube display Status in firefox package in Ubuntu: New Bug description: Firefox starts to build the buffer, but is does not display anything. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 88.0.1+build1-0ubuntu0.21.04.2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bertadmin 4040 F pulseaudio /dev/snd/pcmC1D0p: bertadmin 4040 F...m pulseaudio /dev/snd/controlC0: bertadmin 4040 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue May 25 14:25:12 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 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2019-11-30 (542 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev enp7s0 proto dhcp metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 192.168.1.0/24 dev enp7s0 proto kernel scope link src 192.168.1.106 metric 100
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
According to https://github.com/karelzak/util-linux/pull/705, this issue seems to have been fixed natively in mount/libmount1 from util-linux (since version 2.34). So it should work with Ubuntu 20.04 LTS (focal fossal) and newer. -- 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in fuse package in Debian: Fix Released Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
On Tue, May 25, 2021 at 05:51:12PM -, Francisco Pombal wrote: > Thanks for seeing this through, but let me raise some important points. This isn't the right place to be raising this. Only people subscribed to the bug will see the conversation here, and that cuts out most of the relevant people from the conversation. Try https://discourse.ubuntu.com/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Committed Status in jsunit source package in Bionic: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+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 1929011] Re: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot
Thanks for responding. Why is it then that the occurrences are identical with openSUSE please? rsvp & thx again. Peter On Tuesday, May 25, 2021, 12:50:37 PM EDT, Adolfo Jayme <1929...@bugs.launchpad.net> wrote: AFAIK, Ubuntu disables some of these emergency keys by default ** Package changed: gnome-screensaver (Ubuntu) => ubuntu-settings (Ubuntu) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1929011 Title: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot Status in ubuntu-settings package in Ubuntu: New Bug description: Left-Alt is always operational & Right-Alt is not at any time & not specific to this report's subject category. True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso. It is natural to use Right-Alt due to a closer distance to the SysRq key. This might help explain why some say REISUB does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 00:27:12 2021 InstallationDate: Installed on 2020-07-14 (309 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1929011/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1929011 Title: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot Status in ubuntu-settings package in Ubuntu: New Bug description: Left-Alt is always operational & Right-Alt is not at any time & not specific to this report's subject category. True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso. It is natural to use Right-Alt due to a closer distance to the SysRq key. This might help explain why some say REISUB does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 00:27:12 2021 InstallationDate: Installed on 2020-07-14 (309 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1929011/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Thanks for seeing this through, but let me raise some important points. Why is Thunderbird not covered by the same update policy as Firefox? Sure it's not a web browser, but it's one of the most important and widely used GUI email clients. Also, it is a close cousin of Firefox. These updates took way too long to come out for LTS releases, and they are/were already obsolete once they did roll out. For example, the 78.9.x and 78.10.x releases are more than a month old at this point, and both contain fixes for "high" severity vulnerabilities: https://www.mozilla.org/en-US/security/advisories/mfsa2021-12/ https://www.mozilla.org/en-US/security/advisories/mfsa2021-14/ I think Ubuntu should make a greater effort to keep up with Thunderbird upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Committed Status in jsunit source package in Bionic: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+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 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1929011] Re: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot
AFAIK, Ubuntu disables some of these emergency keys by default ** Package changed: gnome-screensaver (Ubuntu) => ubuntu-settings (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1929011 Title: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot Status in ubuntu-settings package in Ubuntu: New Bug description: Left-Alt is always operational & Right-Alt is not at any time & not specific to this report's subject category. True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso. It is natural to use Right-Alt due to a closer distance to the SysRq key. This might help explain why some say REISUB does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 00:27:12 2021 InstallationDate: Installed on 2020-07-14 (309 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1929011/+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 1929583] [NEW] libpci is not declared as a runtime dependency
Public bug reported: In snapcraft.yaml: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from-source/tree/snapcraft.yaml?h=stable You can see that libpciaccess0 is declared under stage-packages for intel-media-driver. However, this is missing from chromium. This is causing issues in Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=1068560#c22 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1929583 Title: libpci is not declared as a runtime dependency Status in chromium-browser package in Ubuntu: New Bug description: In snapcraft.yaml: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from-source/tree/snapcraft.yaml?h=stable You can see that libpciaccess0 is declared under stage-packages for intel-media-driver. However, this is missing from chromium. This is causing issues in Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=1068560#c22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1929583/+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 1929557] Re: Ubuntu 21.04 No alarm when Battery under 10%
Hello, In fact, I think that in the "parameters", "energy" section, the management for standby, ??? Are time based ... It would be a good idea to add the "alert" function when the power level (or battery voltage) drops below 10% or 15%. Another point: Under Wayland, the "xgamma" setting does not work. and gives an image of your bland ... And impossible to put a scan at 120 Hz. Bien cordialement -- 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/1929557 Title: Ubuntu 21.04 No alarm when Battery under 10% Status in gnome-shell package in Ubuntu: Incomplete Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+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 254171] Re: Nautilus can't properly unmount FUSE file systems
** Changed in: fuse (Debian) Status: Unknown => Fix Released -- 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in fuse package in Debian: Fix Released Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+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 1895643] Please test proposed package
Hello Timo, or anyone else affected, Accepted enigmail into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/enigmail/2:2.2.4-0ubuntu0.18.04.1 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: thunderbird (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Committed Status in jsunit source package in Bionic: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Hello Timo, or anyone else affected, Accepted jsunit into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/jsunit/0.2.2-1~ubuntu0.18.04.2 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: jsunit (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: enigmail (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Committed Status in jsunit source package in Bionic: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+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 1866059] Re: firefox-locale-* packages do not enable localization => post-install localization is not complete
Hello Paride, or anyone else affected, Accepted thunderbird into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thunderbird/1:78.8.1+build1-0ubuntu0.18.04.1 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: thunderbird (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1866059 Title: firefox-locale-* packages do not enable localization => post-install localization is not complete Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Fix Committed Bug description: On 2020-03-03 I installed a Focal system from the latest ISO image and chose the Italian localization at install time. The localization setting worked as expected, but not for Firefox: its interface is still in English. No "Italian" option shows up in the 'Preferences -> Language' menu (the menu is empty). The firefox-locale-it package is correctly installed. I tried installing firefox-locale-fr and restart Firefox, but I still got no French option in the Language menu. On the other hand letting Firefox download the language pack itself *does* work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866059/+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 1878292] Re: firefox FTBFS on s390x
Hello Olivier, or anyone else affected, Accepted thunderbird into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thunderbird/1:78.8.1+build1-0ubuntu0.18.04.1 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: thunderbird (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1878292 Title: firefox FTBFS on s390x Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Fix Committed Bug description: Builds hang when trying to compile the third-party sqlite3 copy, during 7+ hours, before being killed. See e.g. https://launchpad.net/ubuntu/+source/firefox/76.0.1+build1-0ubuntu1/+build/19276095: 436:55.58 make[6]: *** [/<>/firefox-76.0.1+build1/config/rules.mk:673: sqlite3.o] Killed 436:55.59 make[6]: Leaving directory '/<>/firefox-76.0.1+build1/obj-s390x-linux-gnu/third_party/sqlite3/src' 436:55.59 make[5]: *** [/<>/firefox-76.0.1+build1/config/recurse.mk:74: third_party/sqlite3/src/target-objects] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1878292/+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 1895643] Please test proposed package
Hello Timo, or anyone else affected, Accepted thunderbird into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thunderbird/1:78.8.1+build1-0ubuntu0.18.04.1 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Committed Status in jsunit source package in Bionic: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For focal ** Patch added: "pulseaudio_13.99.1-1ubuntu3.11.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500253/+files/pulseaudio_13.99.1-1ubuntu3.11.debdiff -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1923505] Re: thunderbird 78.9.0 FTBFS on ppc64el
FWIW, this happens in Debian as well; cf: https://ci.debian.net/packages/t/thunderbird/unstable/ppc64el/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1923505 Title: thunderbird 78.9.0 FTBFS on ppc64el Status in thunderbird package in Ubuntu: Triaged Bug description: The build hangs forever when compiling the webrender rust crate (see https://launchpad.net/ubuntu/+source/thunderbird/1:78.9.0+build2-0ubuntu3/+build/21368163). I'm attaching the full build log for future reference. This happens when building with rustc 1.50.0+dfsg1+llvm-0ubuntu4 and 1.50.0+dfsg1+llvm-0ubuntu5 (the latter is the version currently in the hirsute release pocket). The build completes when building with rustc 1.50.0+dfsg1+llvm-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1923505/+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 1929557] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1929557/+attachment/5500248/+files/GsettingsChanges.txt -- 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/1929557 Title: Ubuntu 21.04 No alarm when Battery under 10% Status in gnome-shell package in Ubuntu: Incomplete Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+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 1929557] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1929557/+attachment/5500250/+files/ShellJournal.txt -- 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/1929557 Title: Ubuntu 21.04 No alarm when Battery under 10% Status in gnome-shell package in Ubuntu: Incomplete Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+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 1929557] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1929557/+attachment/5500251/+files/monitors.xml.txt -- 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/1929557 Title: Ubuntu 21.04 No alarm when Battery under 10% Status in gnome-shell package in Ubuntu: Incomplete Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+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 1929557] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1929557/+attachment/5500249/+files/ProcCpuinfoMinimal.txt -- 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/1929557 Title: Ubuntu 21.04 No alarm when Battery under 10% Status in gnome-shell package in Ubuntu: Incomplete Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+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 1929557] Re: Ubuntu 21.04 No alarm when Battery under 10%
apport information ** Tags added: apport-collected hirsute ** Description changed: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 21.04 + Package: gnome-shell 3.38.4-1ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 + RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 + Tags: hirsute + Uname: Linux 5.11.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1929557/+attachment/5500247/+files/Dependencies.txt -- 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/1929557 Title: Ubuntu 21.04 No alarm when Battery under 10% Status in gnome-shell package in Ubuntu: Incomplete Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+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 1923505] Re: thunderbird 78.9.0 FTBFS on ppc64el
** Tags added: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1923505 Title: thunderbird 78.9.0 FTBFS on ppc64el Status in thunderbird package in Ubuntu: Triaged Bug description: The build hangs forever when compiling the webrender rust crate (see https://launchpad.net/ubuntu/+source/thunderbird/1:78.9.0+build2-0ubuntu3/+build/21368163). I'm attaching the full build log for future reference. This happens when building with rustc 1.50.0+dfsg1+llvm-0ubuntu4 and 1.50.0+dfsg1+llvm-0ubuntu5 (the latter is the version currently in the hirsute release pocket). The build completes when building with rustc 1.50.0+dfsg1+llvm-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1923505/+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 254171] Re: Nautilus can't properly unmount FUSE file systems
** Bug watch added: github.com/libfuse/libfuse/issues #246 https://github.com/libfuse/libfuse/issues/246 ** Also affects: fuse (Debian) via https://github.com/libfuse/libfuse/issues/246 Importance: Unknown Status: Unknown -- 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in fuse package in Debian: Unknown Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+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 254171] Re: Nautilus can't properly unmount FUSE file systems
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #133 https://gitlab.gnome.org/GNOME/gvfs/-/issues/133 ** Changed in: nautilus Importance: Medium => Unknown ** Changed in: nautilus Status: Confirmed => Unknown ** Changed in: nautilus Remote watch: GNOME Bug Tracker #607706 => gitlab.gnome.org/GNOME/gvfs/-/issues #133 -- 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Unknown Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929572] [NEW] Xorg freeze
Public bug reported: A screen freezing had occurred when I was watching video whose location is on my connected phone(Redmi9 with global miui12). While its appearing, there's completely no response to every input, also, there's no mouse on the screen. That's what I can describe. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 25 22:29:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi Device [1d72:2003] Subsystem: Xiaomi GP107M [GeForce MX350] [1d72:2003] InstallationDate: Installed on 2021-05-03 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: TIMI RedmiBook 16 ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=18c673bc-d09d-4a44-814f-b4f048aa888a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 1.8 dmi.bios.vendor: TIMI dmi.bios.version: RMAIC6B0P0808 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: TM2003 dmi.board.vendor: TIMI dmi.board.version: V34F2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnTIMI:bvrRMAIC6B0P0808:bd12/02/2020:br1.8:efr1.8:svnTIMI:pnRedmiBook16:pvr:rvnTIMI:rnTM2003:rvrV34F2:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 16 dmi.product.sku: TM2003-28977 dmi.sys.vendor: TIMI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1929572 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: A screen freezing had occurred when I was watching video whose location is on my connected phone(Redmi9 with global miui12). While its appearing, there's completely no response to every input, also, there's no mouse on the screen. That's what I can describe. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 25 22:29:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi Device [1d72:2003] Subsystem: Xiaomi GP107M [GeForce MX350] [1d72:2003] InstallationDate: Installed on 2021-05-03 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: TIMI RedmiBook 16 ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=18c673bc-d09d-4a44-814f-b4f048aa888a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 1.8 dmi.bios.vendor: TIMI dmi.bios.version: RMAIC6B0P0808 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: TM2003 dmi.board.vendor: TIMI dmi.board.version: V34F2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TIMI
[Desktop-packages] [Bug 1886161] Re: Unattended upgrades should work on roaming laptops
@Robin You should be able to just run `systemctl start apt-daily.service apt-daily-upgrade.service` from the hook. This will start those two services - which run update / upgrade - in the same transaction, and hence ordering will work correctly. The timer will still run again, so it's not _optimal_, but oh well. An optimal solution would just make the timer "catch up" when the conditions apply. We'll be able to simulate that I guess by moving away from ConditionACPower=true to checking battery state ourself, then exiting with a special error code and retrying on that. systemd at least was fixed to allow retrying oneshot units a while ago, but we've not had the chance to rework the apt integration to do retries. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1929557] Re: Ubuntu 21.04 No alarm when Battery under 10%
Thanks for your report. The issue does not seem to be about the docs, though. Can you please provide some info about your system by running this command: apport-collect 1929557 ** Package changed: ubuntu-docs (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1929557 Title: Ubuntu 21.04 No alarm when Battery under 10% Status in gnome-shell package in Ubuntu: Incomplete Bug description: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929557/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For groovy ** Patch added: "pulseaudio_13.99.2-1ubuntu2.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500217/+files/pulseaudio_13.99.2-1ubuntu2.4.debdiff -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929557] [NEW] Ubuntu 21.04 No alarm when Battery under 10%
You have been subscribed to a public bug: Update 20.10 to 21.04... OK All are corrects ,thanks ! Except No visual or auditory alarm when the battery voltage or power drops below 10% It happened to me several times to fall to 0 and the net stop of the pc. Under 20.04, I was using Cairo dock with the energy monitoring function. Which no longer works under Wailance ... Likewise, I switched to 21.04 .org because the xgamma, Scanning frequency 120 Hz settings do not work under Wailance. ASUS GL753VD PC, core I7 7700, 8 gios Ram, NVIDIA GEX Force GTX 1050 Video Cordialement ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete -- Ubuntu 21.04 No alarm when Battery under 10% https://bugs.launchpad.net/bugs/1929557 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886161] Re: Unattended upgrades should work on roaming laptops
** Changed in: apt (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1527817] Re: unhelpful error message "Parsing filters is unsupported."
** Changed in: file-roller (Ubuntu) Importance: Low => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1527817 Title: unhelpful error message "Parsing filters is unsupported." Status in file-roller package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. download http://www.speedlink.com/support/bin/sl-8861-b-cd-content-02-26-10.zip 2. try to extract the `.iso` file into `/tmp/` The error message `Parsing filters is unsupported.` doesn't provide any information and doesn't explain if something and what is wrong and thus needs to be replaced by a message which does that. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: file-roller 3.16.4-1ubuntu3 Uname: Linux 4.3.0-040300-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 19 02:11:40 2015 InstallationDate: Installed on 2015-12-12 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1527817/+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 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
I'm having this problem on a machine that uses google chrome, the gnome calculator and a corporate software. It's vanilla Ubuntu 20.04. Syslog reaches 50g and the machine stops working (disk full). Exact same message as reported. Any way to stop the log until the problem is resolved? gnome-shell: 3.36.7-0ubuntu0.20.04.1 google-chrome-stable: 90.0.4430.93-1 -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For hirsute ** Patch added: "pulseaudio_14.2-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500206/+files/pulseaudio_14.2-1ubuntu2.debdiff -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For impish ** Patch added: "pulseaudio_14.2-2ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500205/+files/pulseaudio_14.2-2ubuntu2.debdiff -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
The attachment "0001-test-c930-and-c940-dual-speaker.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) 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_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
The attachment "alsa-ucm-conf_1.2.2-1ubuntu0.8.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
alsa-ucm-conf/h/i already contains this patch https://github.com/alsa- project/alsa-ucm-conf/commit/368f10bdc3dbfd4f83ab348b54b8455f08fd1a9e. Thus, skip. -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For groovy ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu5.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500204/+files/alsa-ucm-conf_1.2.2-1ubuntu5.3.debdiff -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
For focal ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1929371/+attachment/5500202/+files/alsa-ucm-conf_1.2.2-1ubuntu0.8.debdiff -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1925320] Re: Backport packages for 20.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.1-2~20.04.1 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: mesa (Ubuntu Focal) Status: New => Fix Committed -- 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/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Also affects: alsa-ucm-conf (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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1925320] Re: Backport packages for 20.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-12 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-12/1:12.0.0-3ubuntu1~20.04.1 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: llvm-toolchain-12 (Ubuntu Focal) Status: New => Fix Committed -- 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/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in xorg-server source package in Focal: New Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@ivandrs, Since it is not ubuntu linux on your machine, I don't know how to build kernel for your distro. Please apply this patch to the kernel source, build and install the testing kernel. boot with "snd_hda_intel.dmic_detect=0", after booting up, please run alsamixer, please make sure master, DAC1 and DAC2 are all at maximum volume, then test speakers. And upload the alsa-info.txt with testing kernel. ** Patch added: "0001-test-c930-and-c940-dual-speaker.patch" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5500190/+files/0001-test-c930-and-c940-dual-speaker.patch -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) 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_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1929536] Re: [SRU] GDM background configurable with gsettings
** Description changed: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. - [Rationale] - Corporate customers use LTS releases and ultimately this will be released for 20.04. - This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. + [Test Case] + 1. Boot a desktop session + 2. Verify that the default aubergine background is displayed in the greeter. + 3. Login as the administrator of the machine + 4. Install systemd-container + 5. Switch to the GDM user: + $ sudo machinectl shell gdm@ /bin/bash + 6. Apply a different background with the command: + $ gsettings set com.ubuntu.login-screen background-picture-uri 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + 7. Logout + 8. Verify that the image 'warty-final-ubuntu.png' is displayed as the background of the greeter. + [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 ** Description changed: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Test Case] - 1. Boot a desktop session + 1. Boot a desktop session 2. Verify that the default aubergine background is displayed in the greeter. 3. Login as the administrator of the machine 4. Install systemd-container 5. Switch to the GDM user: - $ sudo machinectl shell gdm@ /bin/bash + $ sudo machinectl shell gdm@ /bin/bash 6. Apply a different background with the command: - $ gsettings set com.ubuntu.login-screen background-picture-uri 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + $ gsettings set com.ubuntu.login-screen background-picture-uri 'file:///usr/share/backgrounds/warty-final-ubuntu.png' 7. Logout 8. Verify that the image 'warty-final-ubuntu.png' is displayed as the background of the greeter. - - [Risks] - The changeset is minimal, isolated and can be easily reverted. + [Risks / Impact] + The changeset is minimal, isolated (Only the code of the greeter is impacted by the change.) and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 -- 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/1929536 Title: [SRU] GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Test Case] 1. Boot a desktop session 2. Verify that the default aubergine background is displayed in the greeter. 3. Login as the administrator of the machine 4. Install systemd-container 5. Switch to the GDM user: $ sudo machinectl shell gdm@ /bin/bash 6. Apply a different background with the command: $ gsettings set com.ubuntu.login-screen
[Desktop-packages] [Bug 1929536] [NEW] [SRU] GDM background configurable with gsettings
Public bug reported: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases and ultimately this will be released for 20.04. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 ** Affects: gnome-shell (Ubuntu) Importance: Medium Status: Fix Released ** Affects: gnome-shell (Ubuntu Focal) Importance: Medium Status: New ** Also affects: gnome-shell (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Focal) Milestone: None => ubuntu-20.04.3 -- 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/1929536 Title: [SRU] GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases and ultimately this will be released for 20.04. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929536/+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 1929530] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
Public bug reported: Not able to hear the sounds even on testing and any sound within the system. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu UBUNTU 16.04 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen I expect to sound within the system 4) What happened instead There is no sound ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niharika 2011 F pulseaudio CurrentDesktop: Unity Date: Sun May 23 18:36:38 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2021-04-25 (27 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niharika 2011 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.name: 0N5RYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd04/19/2018:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0N5RYC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1929530 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Not able to hear the sounds even on testing and any sound within the system. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu UBUNTU 16.04 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen I expect to sound within the system 4) What happened instead There is no sound ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niharika 2011 F pulseaudio CurrentDesktop: Unity Date: Sun May 23 18:36:38 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2021-04-25 (27 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niharika 2011 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.name: 0N5RYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd04/19/2018:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0N5RYC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1929530/+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 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
** Summary changed: - Overview sometimes fails to appear or disappear in gnome-shell 3.38.4 + Overview sometimes fails to appear or disappear in gnome-shell 3.38 -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Hirsute: Confirmed Status in gnome-shell source package in Impish: In Progress Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+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 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38.4
Verified https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/1794 does fix this properly. The "nan" error messages made me think this was related to recent gjs changes when it's not. -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38.4 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Hirsute: Confirmed Status in gnome-shell source package in Impish: In Progress Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
@Seb, I'll work on these two patches comment#3 mentioned in the other bug. https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929371 Let's leave this ticket to track https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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
